Bug 22 - error message after 'sudo kill'
error message after 'sudo kill'
Status: RESOLVED FIXED
Product: Sudo
Classification: Unclassified
Component: Sudo
1.6.3
PC Linux
: normal normal
Assigned To: Todd C. Miller
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2001-01-20 15:46 MST by laurent.crepet
Modified: 2001-01-20 19:54 MST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description laurent.crepet 2001-01-20 15:46:12 MST
The second sudo command I run returns an error, but do the job.
Here is the ouput of the problem.

[lct@lilinuxred lct]$ ps auxw | grep dnrd
nobody    7152  0.0  0.3  1240  620 ?        S    16:07   0:00 /usr/sbin/dnrd
[lct@lilinuxred lct]$ sudo kill 7152
[lct@lilinuxred lct]$ ps auxw | grep dnrd
[lct@lilinuxred lct]$ sudo /usr/sbin/dnrd
ERROR: Couldn't kill dnrd: No such process
[lct@lilinuxred lct]$ sudo gview /var/log/sudo.log
[lct@lilinuxred lct]$ ps auxw | grep dnrd
nobody    7193  0.0  0.3  1252  648 ?        S    16:12   0:00 /usr/sbin/dnrd
[lct@lilinuxred lct]$


[lct@lilinuxred lct]$ sudo -V
Sudo version 1.6.3p5


/var/log/sudo.log:
Jan 20 16:12:02 : lct : HOST=lilinuxred : TTY=pts/4 ; PWD=/home/lct ; USER=root
    ; COMMAND=/bin/kill 7152
Jan 20 16:12:12 : lct : HOST=lilinuxred : TTY=pts/4 ; PWD=/home/lct ; USER=root
    ; COMMAND=/usr/sbin/dnrd
Jan 20 16:12:54 : lct : HOST=lilinuxred : TTY=pts/4 ; PWD=/home/lct ; USER=root
    ; COMMAND=/usr/X11R6/bin/gview /var/log/sudo.log


/etc/sudoers:
# sudoers file.
#
# This file MUST be edited with the 'visudo' command as root.
#
# See the sudoers man page for the details on how to write a sudoers file.
#

# Host alias specification

# User alias specification
User_Alias  MADMINS = lct

# Cmnd alias specification

# User privilege specification
root    ALL=(ALL) ALL
MADMINS ALL=(ALL) ALL
Comment 1 Todd C. Miller 2001-01-20 15:54:59 MST
This really has nothing to do with sudo since sudo didn't generate the error
message you are seeing.  The most likely explanation is that when you start dnrd
it tries to kill the old dnrd process based on the contents of a pid file
somewhere (probably in /var/run).