Public bug reported: Ubuntu Hardy i386 upstart 0.3.9-2
Creating a new file in /etc/event.d does not seem to be re-read until the next boot up. As per http://upstart.ubuntu.com/faq.html#reload , upstart should automatically re-read its configuration using inotify. It is not related to LP#68904 as inotify is enabled in kernel $ grep INOTIFY /boot/config-2.6.24-16-generic CONFIG_INOTIFY=y CONFIG_INOTIFY_USER=y How to repro: - create a file /etc/event.d/ttyS0 with the following content: # ttyS0 - getty # # This service maintains a getty on ttyS0 from the point the system is # started until it is shut down again. start on stopped rc2 start on stopped rc3 start on stopped rc4 start on stopped rc5 stop on runlevel 0 stop on runlevel 1 stop on runlevel 6 respawn exec /sbin/getty -L 115200 ttyS0 vt102 expected behaviour: to have a serial console started on serial port 0. actual behaviour: until next boot up, the file will not be read ** Affects: upstart (Ubuntu) Importance: Undecided Status: New -- upstart do not read new files in /etc/event.d https://bugs.launchpad.net/bugs/226145 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs