hi,
one may have noticed this "problem" before: zabbix-agent (aswell
as zabbix-server, though) do leave some Standard file Descriptors
(after a short look i guess stderr) open, which one can reproduce
by logging into a system using ssh, start the agent/server and
then logout:
kida:/home/abi# /etc/init.d/zabbix-agent start
Starting Zabbix agent: zabbix_agentd
kida:/home/abi# exit
logout
[logout hangs here for.ever
]
the only way to force ssh to drop the connection is by using
~. Yes, thats not a big problem, but its best practise, when
programming unix daemons to close the std I/O descriptors
inherited from the parent and then redirect the childs std I/O
to, for example /dev/null. See
(point 6)
one may have noticed this "problem" before: zabbix-agent (aswell
as zabbix-server, though) do leave some Standard file Descriptors
(after a short look i guess stderr) open, which one can reproduce
by logging into a system using ssh, start the agent/server and
then logout:
kida:/home/abi# /etc/init.d/zabbix-agent start
Starting Zabbix agent: zabbix_agentd
kida:/home/abi# exit
logout
[logout hangs here for.ever
]the only way to force ssh to drop the connection is by using
~. Yes, thats not a big problem, but its best practise, when
programming unix daemons to close the std I/O descriptors
inherited from the parent and then redirect the childs std I/O
to, for example /dev/null. See
(point 6)
Comment