Hm. I'm not sure what happened then. Purging findutils left
/etc/cron.daily/find there. I deleted it, reinstalled findutils, and now
it appears that /etc/cron.daily/find isn't even in the package any more.
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/
If you have slocate installed, it's cron is likely active instead. grep
for ionice in cron.daily?
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/bugs/152692
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug co
What file is that in? I don't have anything in hardy's /etc/cron.daily
that looks like that:
[EMAIL PROTECTED]:/etc/cron.daily$ grep case.*IONICE *
[EMAIL PROTECTED]:/etc/cron.daily$
[EMAIL PROTECTED]:/etc/cron.daily$ apt-cache policy findutils
findutils:
Installed: 4.2.32-1ubuntu1
Candidate:
I don't see this problem. From debian/locate-cron.daily:
# Avoid providing "-n" when IONICE_CLASS isn't 1 or 2
case "$IONICE_CLASS" in
1|2) priority="-n ${IONICE_PRIORITY:-7}" ;;
*) priority="" ;;
esac
** Changed in: findutils (Ubuntu)
Assignee: (unassigned) => Martin Pitt (pitti)
Status: Fix Released => In Progress
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/bugs/152692
You received this bug notification because you are a member of Ubu
This bug was recently re-introduced to hardy. (Seeing this parameter
mis-use on findutils 4.2.32-1ubuntu1 )
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/bugs/152692
You received this bug notification because you are a member of Ubuntu
Bugs, which is t
Isn't a space in the shebang line (right after #!) really required by
POSIX?
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/bugs/152692
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
The "-" is part of the shell expression. Duh! Ignore my previous
idiotic post.
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/bugs/152692
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
The priority class argument to ionice is still bugged; it passes a
priority class of -2 to ionice if IONICE_PRIORITY is not set, which is
an invalid priority class. I assume priority class 2 is what is intended
here. This affects both /etc/cron.daily/slocate and
/etc/cron.daily/notslocate.
Or shou
Copied to gutsy-updates.
** Changed in: findutils (Ubuntu Gutsy)
Status: Fix Committed => Fix Released
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/bugs/152692
You received this bug notification because you are a member of Ubuntu
Bugs, which i
I've successfully verified this fix by removing slocate from a desktop
install and observing ""none: prio 0" when running the cron job from
package version 4.2.31-1ubuntu2. After updating to the proposed
package, 4.2.31-1ubuntu2.1, the job was then observed to run with "best-
effort: prio 7".
**
Brian: that's indeed another issue (bug 159516).
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/bugs/152692
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ub
Brian:
When the slocate package is installed, it essentially replaces the 'locate'
functionality in findutils. It diverts findutils version of
/etc/cron.daily/find to /etc/cron.daily/find.notslocate to prevent it from
running (cron jobs with a dot in the name do not run). Slocates own
/etc/
** Description changed:
Binary package hint: findutils
I see a couple problems with the /etc/cron.daily/find cron job in the
findutils 4.2.31-1ubuntu2 package (Gutsy RC).
1) There's an extra space in the shebang line (cosmetic)...
#! /bin/sh
2) It's passing a priority to ionic
Is this SRU only for server installs? I'm a bit unclear on how slocate
relates to findutils but on my desktop I have
'/etc/cron.daily/find.notslocate' and '/etc/cron.daily/slocate'.
find.notslocate from findutils 4.2.31-1ubuntu2 or slocate does not have
a reference to 'ionice' at all while
find.
** Description changed:
Binary package hint: findutils
I see a couple problems with the /etc/cron.daily/find cron job in the
findutils 4.2.31-1ubuntu2 package (Gutsy RC).
1) There's an extra space in the shebang line (cosmetic)...
#! /bin/sh
2) It's passing a priority to ionic
testcase, btw, is:
1) wait for updatedb to run from cron
2) examine io priority with "ionice $(pidof updatedb)"
3) should report "best-effort: prio 7" (broken behavior shows "none: prio 0"
** Description changed:
Binary package hint: findutils
I see a couple problems with the /etc/cron.d
I've confirmed that the gutsy-proposed version works correctly for me.
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/bugs/152692
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubunt
Sponsored and accepted into gutsy-updates. Please test.
** Tags added: verification-needed
** Changed in: findutils (Ubuntu Gutsy)
Status: In Progress => Fix Committed
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/bugs/152692
You received this
I updated your diff slightly to use a safer version number (2.1 instead
of 3).
** Attachment added: "findutils_4.2.31-1ubuntu2.1_gutsy-proposed.debdiff"
http://launchpadlibrarian.net/10853915/findutils_4.2.31-1ubuntu2.1_gutsy-proposed.debdiff
--
updatedb cron job re-nices wrong process (pid
** Summary changed:
- updatedb cron job fails
+ updatedb cron job re-nices wrong process (pid 7 by default)!
--
updatedb cron job re-nices wrong process (pid 7 by default)!
https://bugs.launchpad.net/bugs/152692
You received this bug notification because you are a member of Ubuntu
Bugs, which is
21 matches
Mail list logo
