Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   Shell execution generating error, posted by Steve Jones on Tue Sep 19 20:37:59 2006 
    icon2.gif   Re: Shell execution generating error, posted by Stefan Ritt on Fri Sep 22 07:42:57 2006 
       icon2.gif   Re: Shell execution generating error, posted by Steve Jones on Fri Sep 22 19:31:15 2006 
Message ID: 1953     Entry time: Fri Sep 22 19:31:15 2006     In reply to: 1946
Icon: Reply  Author: Steve Jones  Author Email: steve.jones@freescale.com 
Category: Bug report  OS: Other  ELOG Version: 2.6.2-1714 
Subject: Re: Shell execution generating error 

Stefan Ritt wrote:

Steve Jones wrote:
When started as root *but not running as a daemon* shell execution results in the following errors that are sent to Standard Error:
Cannot restore original GID/UID.
Cannot remove pidfile "/var/run/cr-elogd.pid"
; Permission denied
Cannot restore original GID/UID.
Cannot remove pidfile "/var/run/cr-elogd.pid"
; Permission denied


The "/var/run/elogd.pid" file is created from elogd to indicate under which PID it is running. If you run elogd once under root, this file then belongs to root. If you afterwards run it under a user account, it cannot delete or change the file belonging to root. In that case, just delete that file manually.




Quote:

When a process starts via the normal startup process it is started as root then the process changes to run as nobody -- so the pid file will always be owned by root. Yes? Then, shell commands wil not be able to deal with the pid file, right? Why would the shell exec want to deal with the PID file anyway?

Just curious. As long as this does not pose a problem then I will nto worry about it.
ELOG V3.1.5-2eba886