Re: bin/46219: crontab changes do not take effect on the following minute

[Matthew Mondor <mm_lists%pulsar-zone.net@localhost>]

The following reply was made to PR bin/46219; it has been noted by GNATS.

From: Matthew Mondor <mm_lists%pulsar-zone.net@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: bin/46219: crontab changes do not take effect on the following
 minute
Date: Sun, 18 Mar 2012 03:59:04 -0400

 On Sun, 18 Mar 2012 06:00:01 +0000 (UTC)
 mayuresh%acm.org@localhost wrote:
 
 > >Fix:
 > Don't know.
 
 Hmm after quickly checking the cron code, it seems that if we wanted
 cron(8) to immediately act upon a user change event, crontab(1) would
 have to kill the daemon with SIGHUP (I'm not sure poke_daemon() now
 does anything useful; since crontab(1) is setuid root, it probably
 could do this), or the daemon would have to use kevent polling with
 file modification notification.  What's interesting is that
 poke_daemon() seems to assume that this is what cron(8) should do,
 because what that function does is update the file time stamp...
 -- 
 Matt