autofs doesn't start on boottime and "ghost" option is being ingnored on HP machines

anybody PLEASE?

This problem still persists, and as far as i understand now after some research it might have to do with the "speedup" of the boot process that has been implemented in Jaunty?

It'd be really nice if someone could take notice pls, as said before i am willing to provide what ever information you guys require or to run some routines if you wish me to.

Thanks and greetings, firebug

Hi,

I was wondering if you were still having this problem?

Regards
chuck

Hi Chuck!

Yes, unfortunately nothing has changed so far, problem still persists...

Faithfully,
firebug

Thanks for the response, which versions of Ubuntu are these machines are using. Also are they using dhcp or static ips?

Thanks
chuck

Also there seems to be two bugs here. Can you open a second bug for the ghost issue?

Thanks
chuck

Hi Chuck!

All of these machines run Ubuntu Jaunty Jackalope 9.04 and are configured to use dhcp ips where the lease is configured to never expire and the machines also have a reserved ip, meaning always the same one.
So from a technical point of view it is dhcp but practically the ips are static...

@ghost option, basically yes, but you believe that the ghost problem won't go away when the autofs problem is fixed?

thanks and your's, firebug

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Lucid Lynx. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Dear Chuck!

As I am still interested in finding a solution to this I would very much like to help you in solving this, but unfortunately I cannot quite understand how I am supposed to reproduce he failure with a live cd as the malfunction occurs during startup and I seriously don't want to engineer a live cd in order to execute autofs and ldap commands during startup...
As described above there is no problem if you do it manually after startup...
Any suggestions on that?
Yours, Firebug

Dear Chuck!

Here's what i can do for you:
As mentioned above i put a line "/etc/init.d/autofs start" into /etc/rc.local but this did not work anymore since some updates last week, so I put a "echo 'ifconfig` >> /tmp/bla.txt infront of that line and i saw from that that the ethernet interface did not have an ip-address at that time, of course the ldap communication then does not work so good...
As I haven't concerned myself with upstart yet I cannot tell how to solve this properly, however I have a quick and dirty solution to this, I put the following line into /etc/rc.local;

(while [ ! -f /var/run/autofs/_home.pid ]; do /etc/init.d/autofs start; sleep 10; done) &

As you can see this while-loop tests if the pid-file for autofs exists and if not it keeps trying to start it in 10 seconds steps.
This does work but a proper solution would of course be preferable, so I hope you can get this upstart messup fixed somehow...:)
Your's, firebug