On Thursday, February 02, 2012 8:03:12 pm Doug Barton wrote:
> On 02/01/2012 04:42, John Baldwin wrote:
> > On Tuesday, January 31, 2012 9:23:12 pm Doug Barton wrote:
> >> On 01/31/2012 08:49, John Baldwin wrote:
> >>> A co-worker ran into a race between updating a cron tab via crontab(8)
> >>> an
On Thu, 2012-02-02 at 17:03 -0800, Doug Barton wrote:
> On 02/01/2012 04:42, John Baldwin wrote:
> > On Tuesday, January 31, 2012 9:23:12 pm Doug Barton wrote:
> >> On 01/31/2012 08:49, John Baldwin wrote:
> >>> A co-worker ran into a race between updating a cron tab via crontab(8)
> >>> and
> >>
On 02/01/2012 04:42, John Baldwin wrote:
> On Tuesday, January 31, 2012 9:23:12 pm Doug Barton wrote:
>> On 01/31/2012 08:49, John Baldwin wrote:
>>> A co-worker ran into a race between updating a cron tab via crontab(8) and
>>> cron(8) yesterday. Specifically, cron(8) failed to notice that a cro
On Tuesday, January 31, 2012 9:23:12 pm Doug Barton wrote:
> On 01/31/2012 08:49, John Baldwin wrote:
> > A co-worker ran into a race between updating a cron tab via crontab(8) and
> > cron(8) yesterday. Specifically, cron(8) failed to notice that a crontab
> > was
> > updated. The problem is
On 01/31/2012 08:49, John Baldwin wrote:
> A co-worker ran into a race between updating a cron tab via crontab(8) and
> cron(8) yesterday. Specifically, cron(8) failed to notice that a crontab was
> updated. The problem is that 1) by default our filesystems only use second
> granularity for ti
On Tuesday, January 31, 2012 3:13:34 pm Ian Lepore wrote:
> On Tue, 2012-01-31 at 13:30 -0500, John Baldwin wrote:
> > On Tuesday, January 31, 2012 12:57:50 pm Ian Lepore wrote:
> > > On Tue, 2012-01-31 at 11:49 -0500, John Baldwin wrote:
> > > > A co-worker ran into a race between updating a cron
On Tue, 2012-01-31 at 13:30 -0500, John Baldwin wrote:
> On Tuesday, January 31, 2012 12:57:50 pm Ian Lepore wrote:
> > On Tue, 2012-01-31 at 11:49 -0500, John Baldwin wrote:
> > > A co-worker ran into a race between updating a cron tab via crontab(8)
> > > and
> > > cron(8) yesterday. Specifica
On Tuesday, January 31, 2012 12:57:50 pm Ian Lepore wrote:
> On Tue, 2012-01-31 at 11:49 -0500, John Baldwin wrote:
> > A co-worker ran into a race between updating a cron tab via crontab(8) and
> > cron(8) yesterday. Specifically, cron(8) failed to notice that a crontab
> > was
> > updated. T
On Tue, 2012-01-31 at 11:49 -0500, John Baldwin wrote:
> A co-worker ran into a race between updating a cron tab via crontab(8) and
> cron(8) yesterday. Specifically, cron(8) failed to notice that a crontab was
> updated. The problem is that 1) by default our filesystems only use second
> gran
