Ubuntu

/etc/inittab refers to missing /etc/init.d/powerfail

Bug #62077 reported by GarlicSalt2
2
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Undecided
Unassigned

Bug Description

The normal Debian distribution has a script, called 'powerfail', located in '/etc/init.d/ folder' which is called from init as specified in '/etc/inittab':

-----paste-----
# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop
-----paste-----

However, I've noticed that there is no file '/etc/init.d/powerfail'. I believe that this file is called in case of a UPS device signalllng a power loss. It might also be triggered on a Notebook PC upon low batter condition, but I'm not certain. Either the file omission was accidental, or this shutdown method was replaced by something else, and removal of these lines was accidentally skipped.

Revision history for this message
Malcolm Parsons (malcolm-parsons) wrote :

In Debian, /etc/init.d/powerfail is in 2 packages:
genpower (extra) and powstatd (extra)
In Ubuntu, /etc/init.d/powerfail is in 2 packages:
genpower (universe) and powstatd (universe)

So neither distro has a /etc/init.d/powerfail in the default install.

Revision history for this message
GarlicSalt2 (garlicsalt2) wrote :

Hmmm, does that make it a Debian bug?? ;p

I guess it's just my obsessive/compulsive disorder that makes me inclined to think that if a core part of a program (or OS) references a file or program, that it should be there. Is there a simple fix? Certainly! Comment out the lines I referenced above, and set the packages mentioned above by Malcom to uncomment those lines upon installation. Or, just don't include them in a fresh install of Ubuntu by default, and add them to the end of the inittab file upon installation of the aforementioned packages.

Am I a neat freak for think this way?
Am I nuts??
Am I paranoid???

Answers are: "Maybe", "Absolutely", and "Probably not" respectively.

--Aaron, the sarcastic one!

Revision history for this message
GarlicSalt2 (garlicsalt2) wrote :

Oh, yeah. I'd say that this bug is solved. Depending upon whether this is determined to be an actual bug, then I'd guess that it is confirmed.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.