Hi, Someone just pointed out to me that, after installing their 1.4_rc1 system /etc/cron.daily/syslog.cron was not working properly. They further researched it and found that sys-apps/psmisc had install killall into /bin instead of /usr/bin /usr/bin is where syslog.cron is looking for killall. So either syslog.cron needs to be updated or sys-apps/psmisc needs to change back to putting killall in /usr/bin. Cheers, Scott
what cron package are you using
vcron. Here is some more information: sbeck@sbeck sbeck $ qpkg -f /etc/cron.daily/syslog.cron app-admin/sysklogd * sbeck@sbeck sbeck $ emerge search sysklogd Searching... [ Results for search key : sysklogd ] [ Applications found : 1 ] * app-admin/sysklogd Latest version available: 1.4.1-r2 Latest version installed: 1.4.1-r2 Homepage: http://www.infodrom.org/projects/sysklogd/ Description: Standard log daemons sbeck@sbeck sbeck $ emerge search psmisc Searching... [ Results for search key : psmisc ] [ Applications found : 1 ] * sys-apps/psmisc Latest version available: 19-r3 Latest version installed: 19-r3 Homepage: http://psmisc.sourceforge.net/ Description: Handy process-related utilities from Debian sbeck@sbeck sbeck $ emerge search vcron Searching... [ Results for search key : vcron ] [ Applications found : 1 ] * sys-apps/vcron Latest version available: 3.0.1-r1 Latest version installed: 3.0.1-r1 Homepage: http://www.vix.com/ Description: The Vixie cron daemon sbeck@sbeck sbeck $
emerge psmisc-21.2 ... it installs binaries into /bin and puts symlinks in /usr/bin
I wasn't really reporting this to get a solution, only to let you know there is a problem with the current setup. Cheers, Scott
there was a problem and its now fixed ;)
*** Bug 10945 has been marked as a duplicate of this bug. ***
Hi, I hate to beat a dead hourse but... Maybe I do not fully understand what "~arch" packages are. It is my understanding that they are "unstested and possibly unstable". It is my experience that you should should make bug fixes in the "stable" branch as well as the "unstable" if they arn't fixed already. The reason for this I think is obvious. I thought that was the reason for the -r1 -r2 etc at the end of the ebuild scripts... Cheers, Scott
*** Bug 11241 has been marked as a duplicate of this bug. ***
*** Bug 12529 has been marked as a duplicate of this bug. ***
*** Bug 12829 has been marked as a duplicate of this bug. ***
