init script status option is not runnable by non-root

Bug #891309 reported by David Britton
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Client

Bug Description

Unlike (all?) other daemon init scripts, the status option doesn't work for landscape-client unless run as root.

dpb@amra:~$ ps -ef |grep landscape-clien[t]
root 929 1 0 11:59 ? 00:00:17 /usr/bin/python /usr/bin/landscape-client --daemon --pid-file /var/run/landscape/
dpb@amra:~$ service landscape-client status
 * landscape-client is not running

This appears to be a simple matter of the lock file not being created with read permissions for group or other:

dpb@amra:~$ ll $PIDFILE
-rw------- 1 root landscape 3 2011-11-16 11:59 /var/run/landscape/

Changed in landscape-client:
importance: Medium → Low
milestone: none → backlog
Revision history for this message
🤖 Landscape Builder (landscape-builder) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

Landscape Team

Changed in landscape-client:
status: New → Invalid
Changed in landscape-client:
status: Invalid → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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