Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 18 Jul 2008 15:32:42 +0200
From:      =?EUC-KR?Q?Eirik_=A8=AAverby?= <ltning@anduin.net>
To:        "gavin@FreeBSD.org" <gavin@FreeBSD.org>
Cc:        "freebsd-bugs@FreeBSD.org" <freebsd-bugs@FreeBSD.org>, "gavin@FreeBSD.org" <gavin@FreeBSD.org>
Subject:   Re: bin/118248: newsyslog(8) does not obey -s (nosignal) flag
Message-ID:  <626FCB21-D237-47E0-9809-4397936EEA5D@anduin.net>
In-Reply-To: <200807181307.m6ID7qAd057121@freefall.freebsd.org>
References:  <200807181307.m6ID7qAd057121@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
I haven't actually verified that as such. The main gripe I had at the  
time wasn't the signalling as such but that it was complaining when  
the process wasn't running. Skipping the signalling doesn't help much  
if it still complains and returns with an error code - though I guess  
it's subject to some debate how exactly it *should* behave with the -f  
flag.

Thanks for giving this issue attention at all :)

/Eirik

On 18. juli. 2008, at 13.07, gavin@FreeBSD.org wrote:

> Synopsis: newsyslog(8) does not obey -s (nosignal) flag
>
> State-Changed-From-To: open->feedback
> State-Changed-By: gavin
> State-Changed-When: Fri Jul 18 13:05:43 UTC 2008
> State-Changed-Why:
> To submitter: are you sure the signal is actually being sent to the
> process?  From looking at the code, I cannot see a way that the
> signal could be sent if -s is specified, although if run with verbose
> logging newsyslog will say that it is sending signals even though it
> doesn't actually go through with it.
>
>
> Responsible-Changed-From-To: freebsd-bugs->gavin
> Responsible-Changed-By: gavin
> Responsible-Changed-When: Fri Jul 18 13:05:43 UTC 2008
> Responsible-Changed-Why:
> Track
>
> http://www.freebsd.org/cgi/query-pr.cgi?pr=118248
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?626FCB21-D237-47E0-9809-4397936EEA5D>