«press any key to exit» bug
Closed this issue · 3 comments
GoogleCodeExporter commented
I've created initscript to run udpt (daemonized) in such way:
start-stop-daemon --start --background --make-pidfile \
--pidfile ${PID_FILE} \
-1 ${LOG_FILE} -2 ${ERROR_LOG_FILE} \
--exec ${DAEMON} -- ${CONF_FILE}
I run script in one terminal window (start-stop-daemon has detached and I see
bash prompt) and watching for the output (tail -f ${LOG_FILE}) in other
terminal window. But when I press any key in first terminal, udpt is gracefully
terminated (I saw «Goodbye.» and «threads terminated» in second terminal).
Very funny :)
Original issue reported on code.google.com by beelzebu...@gmail.com on 13 Aug 2013 at 11:12
GoogleCodeExporter commented
There are plans to add a daemon/Windows Service into the tracker later.
The tracker doesn't currently run as a daemon/service.
In the meantime, this isn't an issue (it may be an issue later).
Original comment by naim...@gmail.com on 14 Aug 2013 at 12:07
- Changed state: Done
- Added labels: Type-Enhancement, Milestone-v1.0.0
- Removed labels: Type-Defect
GoogleCodeExporter commented
Daemon/service is very good, but at least in Linux no need to specially made
daemon application – start-stop-daemon can easily background non-daemon ones.
In case of udpt, I think that only stdin connection (waiting for any keys)
prevents this task to be done properly, resulting in need of something like
screen/tmux for remote use.
Is there any real need in this «anykey waiting»? Maybe I do not understand
its purpose?
Original comment by beelzebu...@gmail.com on 14 Aug 2013 at 3:21
GoogleCodeExporter commented
It may help now that the program only exits with signals instead of standard
input.
Original comment by naim...@gmail.com on 18 Aug 2013 at 7:33