Ok, I can reproduce the bug any time now: $ sudo apt-get install autofs5 ... Setting up autofs5 (5.0.6-0ubuntu4) ... start: Job failed to start invoke-rc.d: initscript autofs, action "start" failed. dpkg: error processing autofs5 (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: autofs5 E: Sub-process /usr/bin/dpkg returned an error code (1)
What happens---It seems---is that autofs fails to start via start utility: $ sudo start autofs start: Job failed to start $ cd ~fedorov bash: cd: /usr/users/fedorov: No such file or directory However, if I manually start automount, everything seems to work just fine: $ sudo automount $ cd ~fedorov /usr/users/fedorov$ So the bug seems to be not in autofs5 but rather in Upstart, no? Should I mention also that the root filesystem on this box is on a raid0? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/952340 Title: autofs5 fails to install: post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/952340/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
