Reviewing this I can only conclude that there is not an issue with
Deluge but with start-stop-daemon failing to start because the location
that you are using to store the config and log files is not available.
It suggests that the mount point is not available at the point that
deluge init script is being run and as expected start-stop-daemon will
quietly fail.
If there was any issue with deluged/deluge-web starting and not finding
a directory etc. then there would be error log output in
/media/raid5/deluge_config/deluged.log.
Just to add that in the OP init script details, for DAEMON2_ARGS the log
file name is the same as in DAEMON1_ARGS so will be clobbered.
** Changed in: deluge (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/599234
Title:
deluged and deluge-web violate home dir when they should not
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deluge/+bug/599234/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
