Bug 51335 - initscripts should depend on SysVinit
initscripts should depend on SysVinit
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
7.1
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-08-09 11:59 EDT by Filip Van Raemdonck
Modified: 2014-03-16 22:22 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2001-08-09 11:59:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Filip Van Raemdonck 2001-08-09 11:59:32 EDT
Description of Problem:

initscripts' /etc/init.d/functions uses pidof, which is in SysVinit.
However initscripts does not depend on SysVinit either directly or through
dependencies.
I need to build rpms from time to time, and do this on a Debian system
inside a chroot. When I build an rpm that needed to start a service, and
tested it inside this chroot, startup failed because it didn't have SysVinit.

How to reproduce:

Here's the list of packages I have installed to build the package:

MAKEDEV autoconf automake basesystem bash binutils bzip2 bzip2-devel
chkconfig cpp cracklib cracklib-dicts db1 db2 db3 dev diffutils e2fsprogs
ed file filesystem fileutils findutils gawk gcc gcc-c++ gdbm glib glibc
glibc-common glibc-devel gnupg grep gzip info initscripts kernel-headers
libstdc++ libstdc++-devel libtermcap libtool libtool-libs logrotate m4 make
mingetty mktemp modutils mount ncurses net-tools pam passwd patch perl popt
procps psmisc pwdb rpm rpm-build rpm-devel sed setup sh-utils shadow-utils
slang strace sysklogd tar termcap textutils util-linux vim-common
vim-minimal which words zlib zlib-devel

None of these depend on SysVinit. I installed my package, it went ok,
started the service, worked fine, stopped the service, failed because it
couldn't find pidof.

I know this isn't the most common situation, but just think of someone who
does actually use Redhat, and wishes to use a chroot for some services as a
security measurement. He will run into the same problem.

regards,

Filip
PS. How acceptive are you to new packages? I generally don't care about
things I package for Redhat systems, as they are usually to fullfill very
specific needs, but this one is rather general-purpose and I think it could
be a useful addition.
Comment 1 Bill Nottingham 2001-08-09 12:11:39 EDT
Will be fixed in 6.13-1; thanks for the feedback!

Note You need to log in before you can comment on or make changes to this bug.