On 12/04/13 06:03, John Baldwin wrote: > On Tuesday, December 03, 2013 4:55:58 pm Colin Percival wrote: >> The rc system aggressively caches the contents of /etc/rc.conf in order to >> improve boot performance; this produces arguably astonishing (non-)results >> if /etc/rc.conf is modified during the boot process. >> >> Since performance considerations make it infeasible to automatically detect >> if the cached /etc/rc.conf parameters should be invalidated, provide a >> mechanism for explicitly requesting that /etc/rc.conf be reloaded: Catch >> SIGALRM and reload /etc/rc.conf if it is received. > > Might have been worth mentioning explicitly why you didn't use SIGHUP in the > log message (found it in the thread on rc@).
Yeah, I meant to include that but forgot when I actually sat down to write the commit message. > ALRM does seem like an odd choice compared to, say, USR1. SIGUSR1 / SIGUSR2 have always seemed more like "internal API" signals to me rather than something processes should send to each other. I have no idea why I feel this way, but that's why I avoided them. -- Colin Percival Security Officer Emeritus, FreeBSD | The power to serve Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
