Your message dated Tue, 1 Jun 2010 01:05:39 +0200
with message-id <[email protected]>
and subject line Re: Bug#583921: qcontrol: qcontrol is killed just after start
has caused the Debian Bug report #583921,
regarding qcontrol: qcontrol is killed just after start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
583921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583921
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: qcontrol
Severity: normal
I think this is copy&paste problem in /etc/init.d/qcontrol script
(marked by *)
case "$1" in
start)
# Change status led to show green
device=$(grep "Hardware[[:space:]]*:" /proc/cpuinfo 2>/dev/null | \
head -n1 | sed "s/^[^:]*: //")
case $device in
"QNAP TS-109/TS-209" | "QNAP TS-119/TS-219")
test_event_dev || exit 0
if pid=$(qcontrol_start); then
log_action_msg "System boot completed"
# Returns 1 even on success
qcontrol statusled greenon || true
qcontrol powerled on || true
if [ "$SOUND_BUZZER" != no ]; then
qcontrol buzzer short || true
fi
* # Kill the control process
* kill -TERM $pid
* rm -f $SOCKET
fi
;;
--- End Message ---
--- Begin Message ---
On Monday 31 May 2010, Evgeny M. Zubok wrote:
> I think this is copy&paste problem in /etc/init.d/qcontrol script
No, this is on purpose. The man page and README.Debian file for the package
document that there is no proper daemon mode yet. For that reason the
control program is killed after commands have been executed.
Upstream has done some work on implementing a proper daemon mode, but that
is not yet complete.
Cheers,
FJP
--- End Message ---
