> Message: 7 > Date: Mon, 03 Dec 2007 17:59:07 +0100 > From: Arvinn L?kkebakken <[EMAIL PROTECTED]> > Subject: Re: [policyd-users] not daemonizing correctly? > To: policyd-users@lists.sourceforge.net > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Tobias J. Kreidl wrote: > > Hello, Arvinn: > > No, I've never seen this, but this likely has nothing to do with > > policyd itself. A few quetsions:
...the effect you encounter might derieve from errors in your source code. I have already seen such behaviour when implementing an authentication mechanism. You can get this effect when you do not fork off your processes correctly. When compiling this, you get a program that must return somtime. Because it doesn't, your system waits for the program to terminate. So your ssh-terminal waits also. See the "Linux Daemon Writing HOWTO from Devin Watson" for code details. > > 1) Do you experience this with any other programs? > Nope. Not that I've tested that many. On the other hand I have tested it > on 8 different systems. Same behavior. If you do work with a virtual hosts somewhere out there, you might have configuration problems in the vmware of your provider. Perhaps you aren't allowed forking off processes or encounter similar administrative restrictions ? If you didn't change the source code, you should check your environments rights or capabilities to handle your processes. Perhaps you tell us something about your machines ? > > 2) I'm assuming you are launching policyd as "root"? > As of now yes. I've planned to change it to an unprivileged user before > production setting though. > > 3) What shell are you using? (Also, make sure all the limit/ulimit > > settings have typical root priviledges after you log in or "su" > > to "root".) > Running bash as root. Running policyd -c policyd.conf (or > /etc/init.d/policyd start or restart) then exit -> ssh lives forever. > > 4) Does turning up the DEBUG level show anything revealing in the logs? > Nope :(. > > > > 5) Are you using the init script thatcomes with policy d (under > > contributed software, I believe): > > > [snip] > > > > I ask, because otherwise, you might have a stray lock file somewhere > > that's preventing policyd from running properly. > > > > Yes I use this init script. But whether I use it or not has no effect on > the behavior I described. Same thing happens when I try to leave the ssh > login shell. When I run the init script all looks good like every other > init scripts. And policyd works like a charm, or in other words; it does > exactly what it is supposed to do.. I've ran it with greylisting in > training mode on several nodes for some days and I have cumulated more > than 300k's of rows in the triplet table. Nothing suspicious at all; > Except the way it insists to keep my terminal. > > > Arvinn Did you compile the code yourself using a clean environment ? Perhaps you did have a compilation problem and have a malfunctional bunch of mnemonics now. Thomas ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ policyd-users mailing list policyd-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/policyd-users
