Both of your solutions are wrong. When proftpd starts in daemon mode,
upstart fails for some reason to get PID of the process. I tried both
"expect fork" and "expect daemon" - to no help. Yes, proftpd starts just
fine, but you'll fail to stop it. I tried proftpd in no-daemon mode "-n
-q" - fails to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: proftpd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/868885
Title:
Ubu
@Xebec
Woowh That's a long time after intial. message. But it does work out
well.
Note do not start in deamon mode, just use upstart.
Before using it with upstart first remove the start link's with update
rc.d .
If you wan't to stop proftpd just do it with sudo killall -9 proftpd.
The fact tha
Christophe, of course I removed all links from rc* before I wrote my
/etc/init/xebec-proftpd.conf. I know how to stop the process. The
problem is not in starting it (as it starts just fine with either of
your scripts) and stopping it at reboot (as it is killed naturally) or
by kill. The problem is
BTW. I have this problem in Precise - not Natty. Wrote here since it was
never marked as fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/868885
Title:
Ubuntu natty Proftpd start fails at boot t
I did not used it with precise. Main pc still running natty.
And my other pc with 12.04 does not needs masquerading, then it's
working fine without upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Turned out while testing some of the combinations, I was affected by a
shamefully long time unresolved upstart bug:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582745 . Here is correct (in
my opinion) version of my xebec-proftpd.conf:
# When to start the service
start on (local-filesystems
In the future, please use 'ubuntu-bug package-name' to report Ubuntu bugs.
https://help.ubuntu.com/community/ReportingBugs
You have reported a bug in a non-existent package in Ubuntu archives
since 2007. No developer will see this bug report because simply the
package does not exist any more.
**