So I've got a small script that runs at boot and establishes a reverse SSH tunnel.
In BackTrack 5r3 it worked fine by adding it via update-rc.d and letting it run. System would boot, script would run, tunnel would remain alive. In Kali Linux (Deb6), I can't figure out how to make it NOT kill getty at boot. It's in the right run level (2), and it depends on ssh, so in lsb style I tell it to depend on ssh. Everything works fine, and then it gets to the part where it runs my script in dmesg, and it hangs. Now, my script is actually running - the tunnel works. The problem is that because output from the script appears in dmesg, it seems to be preventing the remainder of the boot process. getty never creates the local console sessions and I can't login (I can log in through SSH no problem). Additionally, if I log in via SSH and kill the script, the remainder of the boot process finishes without a problem. I have done some research this morning on making my script lsb compliant and "daemonizing" it to some degree, but I still don't understand why the hell: A) The script is outputting its content to the console, and B) Why that is preventing getty from starting. I can't tell if this is an issue with the script itself, or an issue with the init script that calls it. Any thoughts or ideas? Things I can try? Any feedback is much appreciated. -Jarred -- "The world's my oyster, a hotel room's my prison cell..."
_______________________________________________ General mailing list [email protected] http://brlug.net/mailman/listinfo/general_brlug.net
