Re: [Dnrd-user] Porting issue: a stray file in /usr/local/etc/dnrd

[Natanael C. <nc...@us...>]

On Mon, 2005-01-10 at 00:41 -0800, David Arnstein wrote:
> I have ported dnrd to Cygwin, which is (roughly speaking) a Linux/Unix 
> emulation layer that runs on Microsoft Window.  Cygwin is developed by 
> Red Hat, by the way.  When my port is as polished as I can make it, I 
> will ask the dnrd maintainers to consider merging in my changes.

Funny, I was thinking of cywin today actually. :) I would gladly merge
your changes to the CVS.

> In the mean time, here is a slight problem.  When dnrd fails (it is my 
> fault, and ...) it writes a file called dnrd.exe.stackdump in 
> /usr/local/etc/dnrd.  This file is the Cygwin analog to a "core" file.
> 
> The next time dnrd starts, it will abort itself because the file 
> dnrd.exe.stackdump has loose file permissions, and dnrd considers this 
> to be a security risk.
> 
> My question to the dnrd experts is thus: does dnrd presently have a 
> problem with core files?  

I don't know really. I don't see core files very often. If dnrd crashes
I try to fix it immediatly. When thinking of it, dnrd runs as non root
user and the /usr/local/etc/dnrd *has* to be owned by root. That means
that dnrd has no rights to write any core dumps anywhere.

> If dnrd were to write a core file, would it go 
> into /usr/local/etc/dnrd?

It would *have* to do that since it chroots to this dir.

>   Would this cause subsequent launches of dnrd 
> to abort?

Obviously it does.

> If the dnrd maintainers have a strategy in place to deal with the 
> possibility of core files, I'd like to understand it.  I would try to 
> faithfully emulate it in my port.

Honestly, I haven't thought much of core files. If you have any
suggestion I'd like to hear.

> Thanks for listening!

Thanks for porting :)

BTW I have done some changes in CVS today and are working on a 2.18
release. You might want to use the CVS version.

--
Natanael Copa