Hmmm. I don't think I saw a message to tell me there was an update to this bug, which is why I've not responded in ages. But I could be wrong...
I've just been bitten by this daft issue again, which prompted me to look at this bug for any responses. Using a micro-SD card with an ARM lucid installation, just logged in via the serial console to rescue the real system (installed on a SATA hard drive but broken due to kernel testing). Logging in as root, multiple seconds (maybe 20?) with no discernible activity. Then it eventually printed out the motd. I've just removed all of /etc/update-motd.d to save me the pain again on this machine. I'm guessing that the *huge* slowdown could well be due to network timeouts on this device, which is not on the network. Or maybe the very slow uSD is the problem. Going back to the report: If console logins are so rare, I don't see any value to update-motd anyway. Even on a system without the long delays I'm seeing, it looks like make-work. In my case, I'm only using the console to start with to try and fix a problem, so slowing down access to the console unnecessarily is very frustrating. In terms of the bad coding with no locking, I'm afraid you'll have to look elsewhere for fixes. My preferred solution to this would be to simply remove the update-motd misfeature altogether. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/684244 Title: Multiple issues with pam_motd update-motd code To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/684244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
