the last node is deleted. Instead, resolve the Coverity warning
by returning (node *)1 when you delete the root node.
based an idea from millert@. ok otto@
and add an 'rtableid' keyword to ps.
Add rtable id, thread id, and socket splice info to struct kinfo_file2
and make fstat display socket splice information.
Remove old KVM_PROC2 and kinfo_proc2 interfaces; bump libkvm major
Socket splice info and corrections from bluhm@ "Lovely" deraadt@
configuration without service disruption which is not what -HUP does for
nsd(8).
Anyway, zone operations (...) should be done using nsdc(8) and not with
an rc script.
discussed with and ok sthen@
regular user, member of the operator group); rm(1) was waiting for
interactive input to remove the runfiles which made no sense, so just
use `-f'.
issue spotted by weerd@
ok weerd@ robert@
fail with errno set to ERANGE if not enough room is provided. Similar for
getlogin_r() so remove minbytes enforcement attribute.
ok kettenis@ guenther@ deraadt@ on getcwd, deraadt@ on getlogin_r.
Pretty terse for now but will eventually come with some more complex
examples when ratchov@ finishes some ongoing work on aucat(1).
ok ratchov@ jmc@ deraadt@
number of audio* nodes from 3 to 1 on vax, since none of the audio-capable
vax can receive another audio device as expansion (until we get TURBOchannel
support with DMA on VS4k/90).
ok deraadt@ todd@
server _must_ be running and accessible before ypldap is started).
Add a proper pexp in the ypldap rc script.
discussed with pyr@ robert@ deraadt@
ok deraadt@
reading it failed, ${pexp} ended up as the empty string and the script
would send SIGTERM to init(1), which was really inconvenient.
Fix that by never allowing pexp to become empty.
My patch considerably simplified by and ok ajacoutot@.
its _flags in rc.conf(8).
When the rc.d(8) system starts a daemon, it will record its pexp under
/var/run/rc.d/rcscriptname and use that to interact with it (errors in
creating /var/run/rc.d or missing pexp file are non fatal, the framework
will just fallback to what it currently does).
deraadt@ doesn't mind a long as it doesn't come in the way of people
manually managing their daemons.
discussed with and input from sthen@ halex@ robert@ schwarze@
ok sthen@ robert@