Hello James, Thank you for taking the time to look in to this bug as well as get back to me. The explanation of the issue definitely makes the problem more clear. However, I am intrigued by the fact that something so important is assumed, and that Upstart errors when it encounters something different (such as there being no initramfs thus /dev/pts not being mounted). However, I'm not intimately familiar with the inner workings, but I would hope there's a way to fix it without having to implement the '--no-log' workaround.
The custom-compiled kernel that's being used to boot the system should have sufficient PTY support enabled: ---- ~# zgrep -i "pty" /proc/config.gz CONFIG_UNIX98_PTYS=y CONFIG_LEGACY_PTYS=y CONFIG_LEGACY_PTY_COUNT=256 ---- Thank you for the suggestion for the workaround. Sadly, I don't think that's something I can implement due to some restrictions with the environment that Ubuntu 12.04 LTS will be running in (at least in my case). But if this isn't something you guys are able to resolve in Upstart before release, alternative options may need to be looked at. I would also love to be able to have job logging enabled, as I feel it is an important addition to Upstart. Thank you again for your time, James. I look forward to seeing how this issue irons out. -Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/980917 Title: Failed to create pty - disabling logging for job To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
