You could use ktrace(1) to trace all calls and then use kdump(1) to read them, and may help you to find what cause it to die, but it may be tricky for anyone except nfsd developer.. You can also try to find person who supports it by looking at last commits to: https://github.com/openbsd/src/blame/master/sbin/nfsd/nfsd.c and email this person, but I do not know if it will help, or talk to people on bugs@ list.
Or you can move to samba/smbd: SMB must have good support in Windows. On Wed, Apr 18, 2018 at 2:53 AM, Rupert Gallagher <r...@protonmail.com> wrote: > > Do you mean nfsd server dies? > > I mean the NFS service as delivered by nfsd, portmap and mountd. > > > Does it provide core dump? > > No! > > > You do not need to restart it > manually: just create script that checks for server existence (like > ``/etc/rc.d/nfsd check``) and run it if it is dead. > > I usually prepare my servers from source with custom patches and settings. > When a server dies on me, it makes a lot of noise in the logs, and it > happens rarely. In 30+ years of activity, I have never restarted a > production server because of clients using it! > > NFS is an exception. I am using the obsd default, and it dies on me under > load and without logs. It is unreliable. > >
