# tail ._cfg0000_syslog.cron ... # Restart syslogd # /bin/killall -HUP syslogd # whereis killall killall: /usr/bin/killall /usr/man/man1/killall.1.gz /usr/share/man/man1/killall .1.gz # ls -alsh /bin/k* 12K -rwxr-xr-x 1 root root 8.3K Dec 13 00:48 /bin/kill* The previous rev of sysklogd had it correct though: # tail syslog.cron ... # Restart syslogd # /usr/bin/killall -HUP syslogd
killall is in /bin/ ... root@vapier root # qpkg -f /bin/killall -v sys-apps/psmisc-21.2 *
borgy:/bin# ls k* kill borgy:/bin# qpkg -f /bin/killall -v borgy:/bin# borgy:/bin# qpkg -f /usr/bin/killall sys-apps/psmisc * How'd that happen?
Garen; guess you got an old psmisc. would you upgrade please, or either edit your cron snippert yourself to manage :p athlon /root # grep killall /var/db/pkg/sys-apps/psmisc-21.2/CONTENTS obj /bin/killall c15c22ed740d42d609d73778c78b1f81 1040077390 sym /bin/pidof -> killall 1040077390 sym /usr/bin/killall -> /bin/killall 1040077390 obj /usr/share/man/man1/killall.1.gz 4bad081a631037450637fcec5b2fc874 1040077390
# qpkg -i psmisc sys-apps/psmisc-19-r3 * ... Hm. I don't believe I've ever rebuilt this one, so it must have come from the stage3 .tbz. I run stable and don't see anything newer avail, and in that case would expect others to run into this too.
(Oh and yeah I can edit the cron script of course, its trivial...just thought I should report it :))
yeah i figured it was just a matter of you not using the new psmisc ebuild (that symlink and stuff is in the new psmisc) woodchip: think its ok to make latest psmisc go stable ?
