Okay, I'll take it out of xinetd completely, and maybe take it out from
under tcp wrappers, too.


- Mark


-----Original Message-----
From: Steve Prior [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, February 12, 2008 9:19 AM
To: [EMAIL PROTECTED]; LFS Support List
Subject: Re: Connectivity, continued

  > These messages occur at the end of the boot process (I'm now running 
sshd
> outside of xinetd to see if I can figure out what's causing the
connectivity
> failure I reported in an earlier email).

You don't want to run sshd from xinetd, you should always run it 
standalone.  sshd requires too much overhead on startup to run from 
within xinetd.

Steve

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 2868 (20080212) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 2868 (20080212) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 

-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to