xinetd popper problem 0.0.0.0 already in use

Sigh. I like linux, but it sure is a pain in the ass to get working sometimes. I have the qpopper popper program running under xinetd. When I try to access it from across my subnet via telnet I get rejected on the client side and a message prints out on the lfs system console to the effect that

xinetd qpopper addtl info

Further to my last on popper/xinetd not working from another client on the same subnet, I rebuilt qpopper with debugging support. Here's an extract from sys.log when the attempt to connect from another client occurs: Apr 26 13:50:08 wiggle_butt xinetd[16303]: Reading included configuration file:

RE: ATA Drives as SCSI Drives?

On Feb 12, 2008 9:39 PM, Sharif Oerton [EMAIL PROTECTED] wrote: On Wed, 13 Feb 2008 15:01:06 Mark Olbert wrote: Quick question: I have 3 SATA hard disks, a PATA DVD-R/W, and a PATA Zip drive in my LFS6.3 system. All five devices show up as SCSI devices (e.g., sda, sdb, sdc, sdd, sr0

ATA Drives as SCSI Drives?

Quick question: I have 3 SATA hard disks, a PATA DVD-R/W, and a PATA Zip drive in my LFS6.3 system. All five devices show up as SCSI devices (e.g., sda, sdb, sdc, sdd, sr0). That's not a big deal -- although it took me a little while to figure out how the DVD-R/W was named -- but it strikes me as

Connectivity Problem Resolved..mostly

Thanks to everyone who made suggestions on what might be wrong with my LFS 6.3 system. I'm now able to connect to the new LFS box over either telnet or ssh. The solution involved paring away some complexity, which I'd probably misconfigured (e.g., reverting to an unwrapped sshd), and then

RE: Various Issues, Mostly Connectivity

and one which doesn't? - Mark -Original Message- From: Valter Douglas Lisbôa Jr. [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 10:04 AM To: [EMAIL PROTECTED]; LFS Support List Subject: Re: Various Issues, Mostly Connectivity On Tuesday 12 February 2008 13:52:16 Mark Olbert

RE: Connectivity, continued

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

RE: Connectivity, continued

- From: Theodore Heise [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 12, 2008 10:56 AM To: [EMAIL PROTECTED]; LFS Support List Subject: Re: Connectivity, continued On Tue, 12 Feb 2008, Mark Olbert wrote: Can someone tell me how I can get xinetd, or telnetd, or something!!! to log some

Connectivity, continued

Okay, this is starting to be a whole lot less fun... Can someone tell me how I can get xinetd, or telnetd, or something!!! to log some additional error messages to some log about connection attempts against telnetd? I've tried using server_args=telnetd -D options -debug in the xinetd.d config

Various Issues, Mostly Connectivity

I've built an LFS 6.3 system, it boots fine (with one oddity; see below), but am running into several issues that are preventing me from deploying it (it's destined to be a firewall/router). 1) I compiled framebuffer support into the kernel. When the system boots, about half the time the effect

Various Issues Followup

Oops, forgot to include this: When attempting to connect to ssh on the new LFS system (from the old system): [EMAIL PROTECTED]:/home/mark# ssh -v -l mark wiggle_butt OpenSSH_4.1p1, OpenSSL 0.9.8c 05 Sep 2006 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Connecting to wiggle_butt

RE: Various Issues Followup

, 2008 8:12 AM To: [EMAIL PROTECTED]; LFS Support List Subject: Re: Various Issues Followup 2008/2/12, Mark Olbert [EMAIL PROTECTED]: Oops, forgot to include this: When attempting to connect to ssh on the new LFS system (from the old system): [EMAIL PROTECTED]:/home/mark# ssh -v -l mark

RE: Connectivity, continued

Of Jeremy Henty Sent: Tuesday, February 12, 2008 9:09 AM To: lfs-support@linuxfromscratch.org Subject: Re: Connectivity, continued On Tue, Feb 12, 2008 at 08:59:38AM -0800, Mark Olbert wrote: sshd[2417]: Server listening on :: port 22. sshd[2417]: error: Bind to port 22 on 0.0.0.0 failed

Chapter 7: Symlinks to Devices and udevtest

Everything was going along swimmingly with 6.3 until I hit chapter 7, symlinks to devices and udev... How is udevtest supposed to work? On my system, udevtest /sys/block/hdd gives: This program is for debugging only, it does not run any program, specified by a RUN key. It may show incorrect

Dual Core?

This is probably a silly question, but I haven't been able to find an answer in the mailing list archives. If built on a dual-core system, does LFS take advantage of the dual cores? - Mark -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ:

Test Message

Sorry to do this, but this email list is kind of funky about what email addresses it's willing to accept messages from without moderator approval (which apparently takes a l-o-n-g time; I'm not complaining, but I have a problem that I need help with ASAP). So this is essentially just a check

LFS 6 System Won't Boot

I have an oddball problem that is causing me to rip out hair :) My LFS 6 system, which has performed like a champ for years, suddenly stopped booting the other day. Initially the problem was that it couldn't see /dev/sda1, /dev/sda3 and /dev/sda4 (which is how my SATA drive shows up in the

System Doesn't Boot Part 2

Some additional info: I checked the logs after the last failed/hanging boot, and the system log shows most, if not all, of the shell scripts executing (I can tell by the messages they log). But I never get a login prompt on the screen, and it looks like the system hangs. I did notice one

Re: System Doesn't Boot Part 2

, Jan 26, 2008 at 03:08:18PM -0800, Mark Olbert wrote: Some additional info: I checked the logs after the last failed/hanging boot, and the system log shows most, if not all, of the shell scripts executing (I can tell by the messages they log). But I never get a login prompt on the screen

Re: System Doesn't Boot Part 2

@linuxfromscratch.org Sent: Saturday, January 26, 2008 3:39:07 PM Subject: Re: System Doesn't Boot Part 2 On Sat, Jan 26, 2008 at 03:08:18PM -0800, Mark Olbert wrote: Some additional info: I checked the logs after the last failed/hanging boot, and the system log shows most, if not all

Re: System Doesn't Boot Part 2

them. This mailing list has been great so far, I feel like there's just a little more to go...after which I'll start building that new system. - Mark - Original Message From: Mark Olbert [EMAIL PROTECTED] To: LFS Support List lfs-support@linuxfromscratch.org Sent: Saturday, January 26

Success...sort of

Ken's comments on this thread about my udev setup being badly messed up (and perhaps my system being totally hosed) prompted me to do something a little unusual: I copied all of the udev binaries over from my working slackware partition to the non-functional LFS partition. I then copied over

SASL and PAM under Postfix

I am having trouble getting SASL and PAM to play nicely together (Im using postfix as my MTA). When I run cyrus-sasls saslauthd in debug mode, and then telnet to the smtp port on my pox, I see the correct authentication mechanisms being offered, which include plain. But when I do an AUTH

RE: SASL and PAM under Postfix

Of Archaic Sent: Saturday, August 06, 2005 10:21 AM To: BLFS Support List Subject: Re: SASL and PAM under Postfix On Sat, Aug 06, 2005 at 10:08:51AM -0700, Mark Olbert wrote: But when I do an AUTH PLAIN with my base64 encoded credentials, pam refuses to authenticate. The saslauthd debug trace shows