Here's a screen capture from the vmware ESXi console thing.
I'm not sure if there's could be a link but just in case. After I upgraded to 14.04 some of my own upstart jobs where starting, stopping and starting again in a loop (I guess upstart gave up after a number of iterations).
I had the error 'This account is currently not available.' in my upstart jobs' logs because I was using :
exec su -c './myscript' nobody
instead of setuid. I changed all my scripts to use setuid and everything seems to be fine now.
During boot.
Here's a screen capture from the vmware ESXi console thing.
I'm not sure if there's could be a link but just in case. After I upgraded to 14.04 some of my own upstart jobs where starting, stopping and starting again in a loop (I guess upstart gave up after a number of iterations).
I had the error 'This account is currently not available.' in my upstart jobs' logs because I was using :
exec su -c './myscript' nobody
instead of setuid. I changed all my scripts to use setuid and everything seems to be fine now.