Bug 4375 - chkconfig now prints its version all over the place
chkconfig now prints its version all over the place
Status: CLOSED NEXTRELEASE
Product: Red Hat Raw Hide
Classification: Retired
Component: chkconfig (Show other bugs)
1.0
i386 Linux
high Severity low
: ---
: ---
Assigned To: Erik Troan
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-08-05 13:08 EDT by Jay Freeman
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-05 13:48:43 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 Jay Freeman 1999-08-05 13:08:24 EDT
== Installed chkconfig-1.0.6-3, and now I get:

[root(3)@ironclad RPMs]# rpm -Uhv initscripts-4.28-
2.i386.rpm
initscripts ###############################################
chkconfig version 1.0.6
chkconfig version 1.0.6
chkconfig version 1.0.6
[root(3)@ironclad RPMs]# rpm -Uhv heartbeat-0.4.1-
2.i386.rpm
heartbeat   ###############################################
chkconfig version 1.0.6
[root(3)@ironclad RPMs]# rpm -Uhv nscd-2.1.2-3.i386.rpm
nscd        ###############################################
chkconfig version 1.0.6

== Then I got an e-mail:

From: root@mail.saurik.com (Cron Daemon)
To: root@mail.saurik.com
Subject: Cron <root@ironclad> run-parts /etc/cron.hourly
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/>
X-Cron-Env: <LOGNAME=root>

chkconfig version 1.0.6

== Checked up on that:

[root(3)@ironclad RPMs]# cat /etc/cron.hourly/*
#!/bin/sh
/sbin/chkconfig innd && su - news -c /usr/bin/nntpsend
#!/bin/sh
su - news -c /usr/bin/nntpsend

== Tried it for myself:

[root(3)@ironclad RPMs]# chkconfig
chkconfig version 1.0.6

== Just a TAD annoying :)
Comment 1 Bill Nottingham 1999-08-05 13:48:59 EDT
fixed in chkconfig-1.0.7.

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