>>>>> "Sam" == Sam MacDonald <smac at visi.com> writes: Sam> Jay Kline wrote: >> On August 22, 10:41 am Sam MacDonald <smac at visi.com> wrote: >> >> >>> Well sshd works very, very well, except now I can't start an X >>> session using WinaXe. When I attempted to stop sshd on my >>> Linux box as "root" sshd stop It returns the following message >>> Extra argument stop. >>> ****** >>> version Openssh_2.9p2 >>> ****** >>> I can stop and start other demons but it's like this one can't >>> be stopped . The man page doesn't list any way to stop sshd, >>> is it a freight train? Sam. >>> >>> >> >> >> Try "/etc/rc.d/init.d/sshd stop" or even "killall sshd" >> >> Of course, if you are logged in via ssh, it will end your >> session, rather quickly. >> >> Jay >> >> >> >> Sam> That worked very well. So being in the init.d directory and Sam> running sshd stop is different then /etc/rc.d/init.d/sshd Sam> stop Sort of interesting but annoying Depends on what your path is. Not annoying, very important (you don't want the current directory in your path by default, ESPECIALLY as root, for reasons too long and old to go into here). Look what happens with me: [root at tsathoggua root]# which sshd /usr/sbin/sshd [root at tsathoggua root]# cd /etc/init.d/ [root at tsathoggua init.d]# which sshd /usr/sbin/sshd [root at tsathoggua init.d]# ls sshd sshd* [You might have to use "type" instead of "which," I'm an old (t)csh user.] See? I get sshd from my path. /etc/init.d is NOT in my path (nor should it be). R _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list