Bug 2970 - need lockfile ?
Summary: need lockfile ?
Status: CLOSED FIXED
Alias: None
Product: Sisyphus
Classification: Development
Component: acpid (show other bugs)
Version: unstable
Hardware: all Linux
: P4 blocker
Assignee: Albert R. Valiev
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-11 15:43 MSD by Anton Farygin
Modified: 2007-04-06 15:50 MSD (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Farygin 2003-09-11 15:43:43 MSD 
[root@jabbersample root]# service acpid status
acpid is stopped
[root@jabbersample root]# service acpid start
Starting acpid service:                                                        
                       [ DONE ]
[root@jabbersample root]# service acpid status
acpid is running
[root@jabbersample root]# service acpid start 
Starting acpid service: acpid: can't open /proc/acpi/event: Device or resource busy
                                                                               
                       [FAILED]
[root@jabbersample root]# service acpid status
acpid is dead, but subsystem is locked
[root@jabbersample root]# service acpid stop  
Service acpid is not running.                                                  
                       [PASSED]
[root@jabbersample root]# ps -ax|grep acpid
 2551 ?        S      0:00 /usr/sbin/acpid

Я думаю, что больше ничего не надо объяснять ?
Comment 1 Albert R. Valiev 2003-09-12 09:30:01 MSD 
Fixed in 1.0.2-alt3
Comment 2 Michael Shigorin 2003-09-14 21:07:50 MSD 
Гм.  Точно не _lock_file?

work:~> sudo service acpid restart
Stopping acpid service:                                                 [ DONE ]
Starting acpid service:                                                 [ DONE ]
work:~> l /var/run/acpid.pid
/bin/ls: /var/run/acpid.pid: No such file or directory
work:~> rpm -q acpid
acpid-1.0.2-alt3