Hi Graham, Am 18.06.2010 23:34, schrieb Graham T: > Sure - I will give that a try. > > But how will that be any different to the section in /etc/init.d/proftpd > that checks for the existence of /var/run/proftpd and creates it if it > is not present? >
I suspect a race between the upstart jobs and the traditional init scripts. Unfortunately proftpd is a traditional init script. I'm not 100% sure, but I believe upstart scripts are executed partly in parallel with traditional init scripts, so I suspect that sometimes /var/run is not yet mounted as tmpfs when the check you mentioned: > # /var/run could be on a tmpfs > [ ! -d /var/run/proftpd ] && mkdir /var/run/proftpd > is performed. Probably /var/run/proftpd exists at this point (on the root filesystem.) Then, before proftpd is executed later in this script /var/run is mounted by the upstart script and suddenly /var/run/proftpd does not exists anymore (because this is a new filesystem now). However, this is all just speculation. There would be only a short timeframe were this failure can occur, but on the other hand this is in line with your report that the behaviour seems somewhat random. > > And if I stop the proftpd service, manually delete /var/run/proftpd then > start the proftpd service again the /var/run/proftpd directory is > correctly created and the service starts. > > I am just asking out of curiosity as I have no idea what > /etc/init/mounted-varrun is used for! > Its executed immediately after /var/run is mounted as tmpfs. > I will add that line in now and let you know how it goes. > Of course this is not the real bug fix, but would point in the right direction... Best regards, Arnd -- proftpd will not start with kernel 2.6.32-22-generic https://bugs.launchpad.net/bugs/591865 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
