> On 4/6/2010 1:13 PM, m.roth at 5-cent.us wrote: >>> On 4/6/2010 12:22 PM, m.roth at 5-cent.us wrote: >>>>> On 4/6/2010 11:56 AM, m.roth at 5-cent.us wrote: >>>>>>>> On 4/6/2010 10:46 AM, m.roth at 5-cent.us wrote: >>>>>>>>> Todd wrote: >>>>>>>>>> m.roth at 5-cent.us wrote, On 04/06/2010 10:51 AM: >>>>>>>>>>> What I was doing: log onto my machine (system run level 5, I >>>>>>>>>>> log >>>>>>>>>>> out, NOT just lock the screen, every single night; therefore, >>>>>>>>>>> there should be no processes running owned by me), and in a >>>>>>>>>>> terminal window, do >>>> <snip> >>>>> it. But, you don't have to start one at all because normal X >>>>> startup >>>>> will do it for you - and correctly. You only need to run ssh-add. >>>> >>>> "Normal X startup" - do you mean login, in runlevel 5, or do you mean >>>> runlevel 3, and startx? >>> >>> These are both infinitely configurable, but I think the defaults end up >>> running /etc/X11/xinit/xinitrc or /etc/X11/xinit/Xsession any way you >>> do >>> it. So the answer is yes. >> >> So, if I'm in runlevel 5, login should start it, correct? > > gdm, not login, but the same difference. > Or rather, its equivalent, since I run KDE. >> Except that the more I think about it, the more I'm back to my original >> problem: if it automagically starts it, why does it not automagically >> STOP it when I log out, the way it does every other of my processes, >> except for >> something I explicitly backgrounded (I mean, I remember when I had to >> nohup things like that)? > > It does stop the one it starts. The one that is still running is the > one you started some time ago (no arguments on the command line in ps). Sorry, you missed the subject of that sentence - I meant, why does it not stop the one I explicitly started? Are you saying that ssh-agent, with no commands, implicitly backgrounds itself? And, for the bigger picture, why should it? If I'm logging off, there's no reason for it to keep running. Any sessions that required it are either established, or shut down. mark