[Bug 332210] Re: since an upgrade to jaunty the rc.local is not loaded at startup
[Expired for sysvinit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: sysvinit (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/332210 Title: since an upgrade to jaunty the rc.local is not loaded at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/332210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 332210] Re: since an upgrade to jaunty the rc.local is not loaded at startup
Can somebody reproduce this on a more current release of Ubuntu? rc.local is run as part of the sysvinit compatibility mode handling of runlevel 2, so I don't really see how it would kill off any processes. ** Changed in: sysvinit (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/332210 Title: since an upgrade to jaunty the rc.local is not loaded at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/332210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 332210] Re: since an upgrade to jaunty the rc.local is not loaded at startup
I simple workaround is to use start-stop-daemon. Example: start-stop-daemon --start --background --name tftpd --startas /usr/sbin/in.tftpd -- -svL -m /etc/default/tftpd.rules /unattended/bootdisk.new/tftpboot/ -- since an upgrade to jaunty the rc.local is not loaded at startup https://bugs.launchpad.net/bugs/332210 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
[Bug 332210] Re: since an upgrade to jaunty the rc.local is not loaded at startup
Confirmed in Karmic (2.6.30-6 kernel), although my script ran for ten seconds longer than the 'exit 0'. I had a 'sleep 5' and it ran for 15 seconds. ** Changed in: sysvinit (Ubuntu) Status: New = Confirmed -- since an upgrade to jaunty the rc.local is not loaded at startup https://bugs.launchpad.net/bugs/332210 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
[Bug 332210] Re: since an upgrade to jaunty the rc.local is not loaded at startup
I have the same problem with a different script, which starts autossh. ** Changed in: sysvinit (Ubuntu) Status: Invalid = New -- since an upgrade to jaunty the rc.local is not loaded at startup https://bugs.launchpad.net/bugs/332210 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
[Bug 332210] Re: since an upgrade to jaunty the rc.local is not loaded at startup
I vote for this bug. I have the same problem with the same script on the same distribution. -- since an upgrade to jaunty the rc.local is not loaded at startup https://bugs.launchpad.net/bugs/332210 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
[Bug 332210] Re: since an upgrade to jaunty the rc.local is not loaded at startup
I had the same problem. The (same) script worked in Intrepid, too. The behavior of /etc/rc.local must have changed in Jaunty. My solution is to use start-stop-daemon: start-stop-daemon --start --name acerfand --startas /usr/local/bin/acerfand --background I don't know if it is important, but I removed the in the last line of the script (govern without ). Now the script detaches correctly from the tty: $ ps -Af | grep 'UID\|acerfand' UIDPID PPID C STIME TTY TIME CMD root 3105 1 0 10:18 ?00:00:00 /bin/bash /usr/local/bin/acerfand -- since an upgrade to jaunty the rc.local is not loaded at startup https://bugs.launchpad.net/bugs/332210 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
[Bug 332210] Re: since an upgrade to jaunty the rc.local is not loaded at startup
There's something strange going on here. I have been using the same script (acerfand) and investigated further with modifications to the script. The script ran fine in Intrepid, but in Jaunty when you hit the final exit 0 in rc.local, it exits acerfand as well. acerfand traps this exit, and I used this to print out more information. If I put a sleep 20 in rc.local after running acerfand, it will only be exited after the 20 have expired. I have tried a number of things, including double-backgrounding acerfand (I verified that its parent ID was 1), running it using nohup and running it in the background from a separate script, but all to no avail. This bug should NOT be closed as invalid, as the problem is not with the included script. There has been a change of behaviour in Jaunty which at least needs explaining, and may or may not be a bug in sysvinit or indeed another package. I will try and come up with a trivial script that shows the problem and attach it here. -- since an upgrade to jaunty the rc.local is not loaded at startup https://bugs.launchpad.net/bugs/332210 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
[Bug 332210] Re: since an upgrade to jaunty the rc.local is not loaded at startup
OK a trivial test case that demonstrates the behaviour. /etc/rc.local has: (/etc/init.d/testscript ) sleep 20 exit 0 The executable file /etc/init.d/testscript says: #!/bin/bash MYLOGFILE=/home/user/testscript.log echo Starting testscript at `date` $MYLOGFILE echo Show that the script has detached and has a PPID of 1 $MYLOGFILE ps -ef | grep testscript $MYLOGFILE trap echo script was exited at `date` $MYLOGFILE EXIT while true; do echo testscript in loop at `date` $MYLOGFILE sleep 1 done and the output of testscript.log is: Starting testscript at Wed Apr 8 11:36:27 BST 2009 Show that the script has detached and has a PPID of 1 root 2915 1 0 11:36 tty8 00:00:00 /bin/bash /etc/init.d/testscript root 2919 2915 0 11:36 tty8 00:00:00 grep testscript testscript in loop at Wed Apr 8 11:36:27 BST 2009 testscript in loop at Wed Apr 8 11:36:28 BST 2009 testscript in loop at Wed Apr 8 11:36:29 BST 2009 testscript in loop at Wed Apr 8 11:36:30 BST 2009 testscript in loop at Wed Apr 8 11:36:31 BST 2009 testscript in loop at Wed Apr 8 11:36:32 BST 2009 testscript in loop at Wed Apr 8 11:36:33 BST 2009 testscript in loop at Wed Apr 8 11:36:34 BST 2009 testscript in loop at Wed Apr 8 11:36:35 BST 2009 testscript in loop at Wed Apr 8 11:36:36 BST 2009 testscript in loop at Wed Apr 8 11:36:37 BST 2009 testscript in loop at Wed Apr 8 11:36:38 BST 2009 testscript in loop at Wed Apr 8 11:36:39 BST 2009 testscript in loop at Wed Apr 8 11:36:40 BST 2009 testscript in loop at Wed Apr 8 11:36:41 BST 2009 testscript in loop at Wed Apr 8 11:36:42 BST 2009 testscript in loop at Wed Apr 8 11:36:43 BST 2009 testscript in loop at Wed Apr 8 11:36:44 BST 2009 testscript in loop at Wed Apr 8 11:36:45 BST 2009 testscript in loop at Wed Apr 8 11:36:46 BST 2009 script was exited at Wed Apr 8 11:36:27 BST 2009 This shows: (a) the script was successfully run (b) the script was successfully detached, and became owned by init (PPID 1) (c) it continued to run for 20 seconds (d) the time it terminated coincides with the time the exit 0 is run in /etc/rc.local (e) the 'date' on the exit command is a bit weird. I suspect the trap command line is run at the time it is encountered, rather than when the trap condition is triggered. So it seems at the point /etc/rc.local exits, it terminates processes it has produced, regardless of whether it currently owns them. I was not seeing this behaviour in Intrepid or Hardy. -- since an upgrade to jaunty the rc.local is not loaded at startup https://bugs.launchpad.net/bugs/332210 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
[Bug 332210] Re: since an upgrade to jaunty the rc.local is not loaded at startup
I'm sorry but it haven't been a problem of rc.local. It has been the included script that hangup. ** Changed in: sysvinit (Ubuntu) Status: New = Invalid -- since an upgrade to jaunty the rc.local is not loaded at startup https://bugs.launchpad.net/bugs/332210 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
