In fact I could find one possible reason of that problem (it might be other
one) : when the server failed to start (in my case because unable to connect
database), the pid file is written anyway... to the startup script is trying to
kill a pid that is not existing...
The nice way, where to rewrite the startup script to display an error when
trying to restart a server that is not running...
** Changed in: tinyerp-server (Ubuntu)
Status: New => Confirmed
--
tinyerp-server start-stop-daemon: warning: failed to kill : No such process
https://bugs.launchpad.net/bugs/220897
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
