[Fwd: List messages rejected]

Bruce Dubbs bruce.dubbs at gmail.com
Tue Jul 31 16:54:40 PDT 2007

-------- Original Message --------
Subject: List messages rejected
Date: Tue, 31 Jul 2007 13:50:31 -0700 (PDT)
From: David Olsson <davidolsson at yahoo.com>
To: blfs-dev-owner at linuxfromscratch.org

Hi.  Sorry to trouble you.  My messages to the list are being held and
rejected.  The last one, my own copy below, was held because, "Message
has a suspicious header".  Can you help me?  I'd like to participate in
BLFS.  Thanks.

Easthampton, MA

----- Rejected Message ----
>From David Olsson Sun Jul 29 18:08:38 2007
Received: from [] by web31814.mail.mud.yahoo.com via HTTP;
Sun, 29 Jul 2007 18:08:38 PDT
Date: Sun, 29 Jul 2007 18:08:38 -0700 (PDT)
From: David Olsson <davidolsson at yahoo.com>
Subject: dhcpcd not stopped by ifdown
To: blfs-dev at linuxfromscratch.org
MIME-Version: 1.0
Content-Type: multipart/alternative;
Content-Length: 1540

I noticed '/etc/rc.d/init.d/network stop' does not kill dhcpcd on my
BLFS system.  For example if I 'telinit 1', then 'telinit 3' I get a fat
error message that tells me I shouldn't be seeing the message and dhcpcd
was already running and oh my please tell the BLFS maintainers about it.
 I traced it to the script
/etc/sysconfig/network-devices/services/dhcpcd.  I seem to have an
infinite lease time and hence my dhcp client is supposed to have exited
when it started.  But it didn't.  I don't see in the dhcpcd man page
that it should.

Following is the script code in question.  Should we eliminate the check
for infinite lease time?

boot_mesg -n "Stopping dhcpcd on the $1 interface..."
# Do nothing with the client daemon if we have an infinate
# lease time as the client exits when started in this case,
# just echo OK.
if [ -e $LEASEINFO ]
    if [ "$LEASETIME" = "4294967295" ]
        # do nothing, just echo ok
        echo ""
    if [ -n "$DHCP_STOP" ]

In the current setup and for a normal shutdown, we're actually better
off that the script didn't kill dhcpcd.  You see, the script would kill
with 'dhcpcd -k'.  That destroys the ip address cache, so we're less
likely to obtain the same address next time.  If shutdown sends sigterm
to dhcpcd, the cache is preserved.  So, when we DO shut down dhcpcd, we
should send it sigterm, not issue 'dhcpcd -k'.  I guess that's what
killproc() would do, so we could probably just not set DHCP_STOP in

~Easthampton, MA

More information about the blfs-dev mailing list