[radvd-devel-l] radvd not starting with different logmethod than default

Reuben Hawkins reubenhwk at gmail.com
Sat Jan 7 11:25:53 EST 2012

On Tue, Jan 3, 2012 at 6:32 AM, Reuben Hawkins <reubenhwk at gmail.com> wrote:
> On Mon, Jan 2, 2012 at 10:45 PM, Pekka Savola <pekkas at netcore.fi> wrote:
>> On Mon, 2 Jan 2012, Reuben Hawkins wrote:
>>> I'm not sure about the code I removed to make it work.  I removed code
>>> which was closing and reopening the log.  This was somehow breaking
>>> privsep.
>>> Does anybody know why the close/reopen was in there?
>> The first part was before my time (AFAIR) but a part of it was due to stderr
>> syslogging with forking:
>> https://github.com/reubenhwk/radvd/commit/61bb845a319cd0a23ef2edb762712779604eff22
>> So I think this had something to do with logging working correctly with a)
>> forking and/or b) privilege dropping and c) different logmethods.
>> Pekka
>> --
>> radvd-devel-l mailing list  :  radvd-devel-l at litech.org
>> http://lists.litech.org/listinfo/radvd-devel-l
> hmmmmm.... I'm not sure how to fix the problem then...  I have two
> ideas (both may be wrong)...
> * remove all logging from the privsep fork
> * remove stderr_syslog log method
> Any insights?

Hi All,

I've pushed up some changes to the master branch regarding privsep.
It all seems to be working well so if I don't hear anything in the
next week or so I'm going to release 1.8.4.  If you have some time,
please do some testing.

The only thing I know of which can be worked out is Ctrl+C doesn't
always end radvd the same way...  Sometime it seems to kill radvd
immediately.  Sometimes it seems to exit gracefully.  Nonetheless, it
doesn't seem like a big deal now, plus the latest changes didn't
introduce the problem.  I'm going to proceed assuming this isn't a bug
and is only just annoying.

Thanks in advance,

More information about the radvd-devel-l mailing list