All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 3601] New: DHCPD S80dhcp-server startup script issues
Date: Wed, 13 Apr 2011 14:19:01 +0000 (UTC)	[thread overview]
Message-ID: <bug-3601-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=3601

           Summary: DHCPD S80dhcp-server startup script issues
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: dmitry at radiofid.ru
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


1. DHCPD is currently unusable by default due to line 15 in S80dhcp-server
script which is unconditional 'exit 1'.

2. DHCPD is always started. There are no means to disable dhcpd startup on
boot.
I suggest to rename S80dhcp-server to dhcp-server and use S* symlink when
needed.

3. Improper check in line 19:
test -f /usr/sbin/dhcpd || exit 0
I suggest to use execute permission check:
test -x /usr/sbin/dhcpd || exit 0

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2011-04-13 14:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 14:19 bugzilla at busybox.net [this message]
2013-11-14  0:16 ` [Buildroot] [Bug 3601] DHCPD S80dhcp-server startup script issues bugzilla at busybox.net
2013-11-14 12:07 ` bugzilla at busybox.net
2013-11-18 10:41 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-3601-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.