On Sat, Jan 16, 2016 at 10:04:56AM -0700, Todd C. Miller wrote:
> On Sat, 16 Jan 2016 14:56:48 +0100, Landry Breuil wrote:
>
> > Good point - the other option would be to log_warn() ? Or just call
> > unlink() without checking the return code like its' done for csockpath ?
>
> I think (void)unlin
On Sat, 16 Jan 2016 14:56:48 +0100, Landry Breuil wrote:
> Good point - the other option would be to log_warn() ? Or just call
> unlink() without checking the return code like its' done for csockpath ?
I think (void)unlink(...) is fine for cleanup.
- todd
On Sat, Jan 16, 2016 at 11:15:30PM +1000, Jonathan Matthew wrote:
> On Sat, Jan 16, 2016 at 12:19:18PM +0100, Landry Breuil wrote:
> > On Sat, Jan 16, 2016 at 11:47:33AM +0100, Landry Breuil wrote:
> > > On Sat, Jan 16, 2016 at 11:40:35AM +0100, Landry Breuil wrote:
> > > > Hi,
> > > >
> > > > pla
On Sat, Jan 16, 2016 at 12:19:18PM +0100, Landry Breuil wrote:
> On Sat, Jan 16, 2016 at 11:47:33AM +0100, Landry Breuil wrote:
> > On Sat, Jan 16, 2016 at 11:40:35AM +0100, Landry Breuil wrote:
> > > Hi,
> > >
> > > playing with ldapd, i noticed that upon exit, the child process (ldape)
> > > is
On Sat, Jan 16, 2016 at 11:47:33AM +0100, Landry Breuil wrote:
> On Sat, Jan 16, 2016 at 11:40:35AM +0100, Landry Breuil wrote:
> > Hi,
> >
> > playing with ldapd, i noticed that upon exit, the child process (ldape)
> > is aborted by pledge:
> >
> > ldapd(10229): syscall 10 "cpath"
> >
> > and /