Bug 3187 - Isn't it better to touch /var/lock/subsys/* in daemon() ?
Isn't it better to touch /var/lock/subsys/* in daemon() ?
Status: CLOSED DEFERRED
Product: Red Hat Linux
Classification: Retired
Component: SysVinit (Show other bugs)
6.0
All Linux
low Severity low
: ---
: ---
Assigned To: David Lawrence
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-05-31 23:23 EDT by inoue
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-07-01 17:30:14 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 inoue 1999-05-31 23:23:12 EDT
I wonder why init-scripts touch /var/lock/subsys/*
individually; isn't it better function daemon() do this?

I think it is also smart to introduce some function to
remove /var/run/*.pid and /var/lock/* together
Comment 1 Bill Nottingham 1999-06-23 17:56:59 EDT
The one problem with this is that it runs the risk of breaking
previous initscripts; while we maintain our own, we don't
maintain ones for third party software (like ssh, for example...)
Comment 2 Bill Nottingham 1999-07-01 17:30:59 EDT
we'll look at this for a later release...

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