Comment 6 for bug 980917
Revision history for this message
| Tim Heckman (theckman) wrote Re: Failed to create pty - disabling logging for job | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
James: It seems that this is a chicken and egg problem when someone doesn't have an initramfs. I'm quite alright with logging being disabled if "/dev/pts" isn't mounted. The problem I have is the large amount of unhelpful errors that are printed on the console. If this could be a concise error, that would be great:
"init: Failed to create pty - temporarily disabling job logging"
And that should be the only error, in my opinion. On the opposing side, I can see where having the specific job that wasn't logged noted. However, that doesn't happen now. And if it flooded the console, I don't think I'd be for it.
Again, without knowing how Upstart processes jobs (maybe I should fix that), I would probably be okay with something like:
"init: Failed to create pty - disabling job logging for the following:
Job1, Job2, Job3, etc."
Simply add a job to the end of the comma-separated list if it isn't logged.
-Tim