On Mon, 3 Dec 2007, Arvinn L?kkebakken wrote:
Michael Brennen wrote:
On Monday 03 December 2007, Arvinn L?kkebakken wrote:
I have set DAEMON=1 in the config.
I have some troubles with running policyd as a daemon though. Every time
after starting policyd in a ssh terminal I am not able to end the ssh
terminal when logging out afterwards. The ssh terminal lives forever
until I kill the policyd process that was started from within it, or
until I kill the sshd process itself.
I've not looked at the code, but this may happen if the forked policyd is not
closing one or more of stdin, stdout or stderr
Is there a way I'll be able to verify whether this is the case?
Arvinn
I'd just try something simple, that creates some output, including
something that creates errors, like the following, which you can also run
in background mode and with the sleep,see what it does if you log out from
the terminal session once you start it running:
#!/bin/sh
# test stdout/stderr redirection
# first, sleep a bit...
/bin/sleep 10
# first, get a listing of /tmp .. should generate a list and no errors
ls -l /tmp >./test.out 2>./test2.out
# try to copy a file that doesn't exist -- generate an error message
cp /tmp/nosuchfile /tmp/nosuchfile2 1>>./test.out 2>>./test2.out
# close stdout and stderr -- optional, works only for Bourne or Korn shell
&-
2>&-
exit
-------------------------------------------------------------------------
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
