Hello, Arvinn:
No, I've never seen this, but this likely has nothing to do with policyd itself. A few quetsions:
1) Do you experience this with any other programs?
2) I'm assuming you are launching policyd as "root"?
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".)
4) Does turning up the DEBUG level show anything revealing in the logs?
5) Are you using the init script thatcomes with policy d (under contributed software, I believe):

#!/bin/bash
#
# Init file for Policy Daemon
#
# chkconfig: 2345 55 25
# description: Postfix Policy Daemon
#
# processname: policyd

# source function library
. /etc/rc.d/init.d/functions

RETVAL=0
PROG="/usr/local/policyd/policyd"
CONF="/usr/local/policyd/policyd.conf"

start()
{
        echo -n $"Starting $PROG:"
        #initlog -c "$PROG -c $CONF" && success || failure
        daemon "$PROG -c $CONF"
        RETVAL=$?
        [ "$RETVAL" = 0 ] && touch /var/lock/subsys/policyd
        echo
}

stop()
{
        echo -n $"Stopping $PROG:"
        killproc policyd
        RETVAL=$?
        [ "$RETVAL" = 0 ] && rm -f /var/lock/subsys/policyd
        echo
}

restart()
{
        stop
        start
}

case "$1" in
        start)
                start
                ;;
        stop)
                stop
                ;;
        restart)
                restart
                ;;
        *)
                echo $"Usage: $0 {start|stop|restart}"
                RETVAL=1
esac
exit $RETVAL


I ask, because otherwise, you might have a stray lock file somewhere that's preventing policyd from running properly.


Regards,
--Tobias

On Mon, 3 Dec 2007, Arvinn L?kkebakken wrote:

Hi. Thanks for a fine product.

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.
Does anybody else experience the same problem?

OS:. CentOS 5
Policyd 1.82.

Regards,
Arvinn

-------------------------------------------------------------------------
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
-------------------------------------------------------------------------
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

Reply via email to