[SOLVED] Slackware 13.37 - Start a program from Terminal

Mark Pettit · 04-10-2012, 11:28 PM

Quote:

Originally Posted by jdgr

I'm just using the default terminal that comes preinstalled with slackware 13.37. Nothing fancy.

So judging by the rest of this thread, I would assume that on Ubuntu, the terminal doesn't send the HUP signal to all child processes but Slackware does handle this properly, thus killing all children unless specifically divorced/disowned? Does that sound about right?

Very unlikely. The handling of the HUP signal is not dictated by the parent, but by the child. So Ubuntu's terminal program will be as effective (or ineffective) as Slackware's. The child program will decide, usually because of code that the programmer wrote, to act on the parent dieing, or not. Slackware's FireFox is pretty much as released by Mozilla - it's very seldom that the Slackware maintainers go that deep. But of course Ubuntu and Debian are famous (notorious) for doing this, so what happens from that point on is anyone's guess. Even so, I'd be surprised if they modified this sort of behaviour.

Richard Cranium · 04-11-2012, 12:21 AM

Quote:

Originally Posted by jdgr

Thanks for all the responses, and the nohup and > /dev/null options.

But for an example: I use putty for one of my work programs. It is a telnet based POS and parts system. I start it via the command line like [CODE]putty -load Parts\ Handler & [\CODE] because I have a few different versions I connect to. Now when I do this the program loads the proper session in the background, and I can use the terminal again. But if I close that terminal window, and I just did it again to confirm, my putty window (the child of that terminal) disappears.

I've never had this happen in Ubuntu and it seems weird that it would work differently in Slackware. I understand that certain children may die if the parent is killed, but I would think the terminal would be different since practically everything can be started from the command line. And putty isn't the only program that this happens to, it's just one that everyone here probably knows.

Code:

man screen

Screen is even more useful if you are logging into a remote box somewhere that has screen available on it.

chrissi29 · 04-11-2012, 02:51 AM

Sorry for the dumb question maybe...
But are you simply closing the terminal window, which leads to closing of all child processes
or are you really logging out of it via exit / strg-d?

jdgr · 04-11-2012, 09:14 AM

chrissi29 may be on to something. I just tried it and if I type exit to close the terminal, it didn't kill the child putty window. But when I click on [X] to close, it killed the second putty window I opened (the child of this new terminal). Interesting, I didn't realize the two commands sent different kill signals to the children, but it looks like this was the answer as to why the children close.