jimmybobby wrote:Will try safe mode, what exactly does it do?
Can I still access /etc/rc.local/ from safe mode, or the emergency kernel image?
Safe mode does not automatically mount the Raspbian root filesystem, and it has a limited selection of commands and editors available. After booting, remove the jumper, hit enter to get a prompt, and run:
Code: Select all
mount /dev/mmcblk0p2 /mnt
mv /mnt/etc/rc.local /mnt/etc/rc.local.broken
Then you can edit and rename the file back in the main system. If you installed using NOOBS, the Raspban root will probably be /dev/mmcblk0p6, instead of p2.
: If you meant /etc/init.d/something, then the easiest fix is to remove the start links from all runlevels: "rm /mnt/etc/rc?.d/S*something".
Richard-TX wrote:You need nohup because the parent process will exit and when the parent dies, so do the children.
When a shell exits, any background jobs continue and are inherited by init. It is your responsibility to kill them if you do not want that.
"nohup" is intended for the situation where a session may disconnect unexpectedly, by telephone hangup, rather than shell exit. It redirects input from /dev/null and output to nohup.out. Even then it is usually unnecessary, because hangup signals are sent only to the foreground process group, and dash does not pass the signal on to background jobs at all, and bash often crashes due to loss of terminal before it even sees the signal.