l i n u x - u s e r s - g r o u p - o f - d a v i s
L U G O D
 
Next Meeting:
August 5: Social gathering
Next Installfest:
TBD
Latest News:
Jul. 4: July, August and September: Security, Photography and Programming for Kids
Page last updated:
2001 Dec 30 17:14

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] sshd dying on debian (potato)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] sshd dying on debian (potato)



* Peter Jay Salzman <p@dirac.org> [011229 15:00], about 

:this reminds me of ajay asking why networked printing didn't work.  i
:suggested that he look at /var/log/messages.  i don't think he liked
:that suggestion because it took him a couple of days to get around to
:looking at the logs and said that in the meantime he wanted another
:solution.  nobody offered one.

>-- End of excerpt from Peter Jay Salzman

JUST to clarify!  ;)

I Always look at the log files.  In fact, on my own machine I have tail (or
colortail) -f running of various log files on various consoles.  (or
sometimes on xterms, especially when it's on other systems..)

What I didn't like was putting lpd in verbose mode, because I had already
previously put lpq in verbose mode, and it was INSANE.  I usually find
workarounds to problems (like logging into the print server and printing it,
which also lets me know printing works locally), then get around to fixing
them 'when I have time'/later.
(And I fixed it because I happened to notice it referring to a different
config dir than I had expected, I'm sure someone who didn't realize the
significance of that would have obtained nothing from putting lpr in verbose
mode.)

sshd though isn't as verbose as lpr/LPRng, so putting that in verbose mode
won't be as bad.  That definitely sounds important though, ssh dying that
is.. (more urgent/etc too) Especially considering all the ssh exploits, that
also makes it that much more of a good idea to be running a recent version. 
And I'd definitely check (eg google) if many others are having that problem,
it shouldn't be that hard to find.  Heck, just check the ssh list archives
might be best, actually.

	Actually, just realized Bill said potato, so that means ssh1, v1.2.x
(1.2.3 or 1.2.27 prob), and if there are problems with it dying, you should
be able to check the debian list archives, that would definitely be your
best bet, assuming it's not pilot error in some way. ;)
(And the security issue is probably moot if your ssh pkg is up to date,
1.2.3-9.3 it looks like.)

anywho!

	-Ajay

-- 
Milpitas, ca	atallam@telocity.net	HempVille, Planet Talarian
			http://os2man.cjb.net/pictures/
	"I'd rather be forgotten than remembered for giving in..."
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech


LinkedIn
LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
facebook
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.