On Sat, Jan 21, 2012 at 09:39:30AM +0100, Otto Moerbeek wrote:
> On Fri, Jan 20, 2012 at 10:48:54AM +0100, Otto Moerbeek wrote:
>
> > On Fri, Jan 20, 2012 at 10:38:35AM +0100, Michael Meskes wrote:
> >
> > > On Thu, Jan 19, 2012 at 09:41:08PM +0100, Otto Moerbeek wrote:
> > > > > With a hint fro
On Fri, Jan 20, 2012 at 10:48:54AM +0100, Otto Moerbeek wrote:
> On Fri, Jan 20, 2012 at 10:38:35AM +0100, Michael Meskes wrote:
>
> > On Thu, Jan 19, 2012 at 09:41:08PM +0100, Otto Moerbeek wrote:
> > > > With a hint from Paul Jantzen I did test this a bit further. There's
> > >
> > > That is,
On Fri, Jan 20, 2012 at 10:38:35AM +0100, Michael Meskes wrote:
> On Thu, Jan 19, 2012 at 09:41:08PM +0100, Otto Moerbeek wrote:
> > > With a hint from Paul Jantzen I did test this a bit further. There's
> >
> > That is, Paul Janzen, sorry about that.
> >
> > > code to avoid having a child runi
On Thu, Jan 19, 2012 at 09:41:08PM +0100, Otto Moerbeek wrote:
> > With a hint from Paul Jantzen I did test this a bit further. There's
>
> That is, Paul Janzen, sorry about that.
>
> > code to avoid having a child runing too long. If you have 20s
> > patience, you'll see this:
> >
> > calendar
On Fri, Jan 20, 2012 at 10:30:01AM +0100, Michael Meskes wrote:
> On Thu, Jan 19, 2012 at 09:38:06PM +0100, Otto Moerbeek wrote:
> > With a hint from Paul Jantzen I did test this a bit further. There's
> > code to avoid having a child runing too long. If you have 20s
> > patience, you'll see this
On Thu, Jan 19, 2012 at 09:38:06PM +0100, Otto Moerbeek wrote:
> With a hint from Paul Jantzen I did test this a bit further. There's
> code to avoid having a child runing too long. If you have 20s
> patience, you'll see this:
>
> calendar: uid 1000 did not finish in time
Now that's interesting.
On Thu, Jan 19, 2012 at 05:46:48PM +0100, Otto Moerbeek wrote:
> Introducing a race is never the right solution, imo.
That I totally agree with.
> By the way, your fix does not catch an included file being a fifo
> either. So while introducing a race, it actually does not fix the
> problem.
Goo
On Thu, Jan 19, 2012 at 09:38:06PM +0100, Otto Moerbeek wrote:
> On Thu, Jan 19, 2012 at 05:46:48PM +0100, Otto Moerbeek wrote:
>
> > On Thu, Jan 19, 2012 at 05:09:25PM +0100, Michael Meskes wrote:
> >
> > > On Thu, Jan 19, 2012 at 12:30:15PM +0100, Otto Moerbeek wrote:
> > > > I looked through
On Thu, Jan 19, 2012 at 05:46:48PM +0100, Otto Moerbeek wrote:
> On Thu, Jan 19, 2012 at 05:09:25PM +0100, Michael Meskes wrote:
>
> > On Thu, Jan 19, 2012 at 12:30:15PM +0100, Otto Moerbeek wrote:
> > > I looked through some of the diffs and noted your are introducing a
> > > race in calendar_fi
On Thu, Jan 19, 2012 at 05:09:25PM +0100, Michael Meskes wrote:
> On Thu, Jan 19, 2012 at 12:30:15PM +0100, Otto Moerbeek wrote:
> > I looked through some of the diffs and noted your are introducing a
> > race in calendar_fifo.diff. Why are you changing this code?
>
> Because the old code blocks
On Thu, Jan 19, 2012 at 12:30:15PM +0100, Otto Moerbeek wrote:
> I looked through some of the diffs and noted your are introducing a
> race in calendar_fifo.diff. Why are you changing this code?
Because the old code blocks if a named pipe is used as a calendar file, a bug
report is here:
http://b
On Thu, Jan 19, 2012 at 10:40:13AM +0100, Michael Meskes wrote:
> Hi,
>
> I'm working on the Debian package bsdmainutils which includes calendar from
> OpenBSD.
>
> In an effort to fix bugs and improve the feature set we added several patches
> to calendar. Some are Linux specific, but the major
Hi,
I'm working on the Debian package bsdmainutils which includes calendar from
OpenBSD.
In an effort to fix bugs and improve the feature set we added several patches
to calendar. Some are Linux specific, but the majority would also be
applicable to OpenBSD. Maybe you're interested in adding thes
13 matches
Mail list logo
