[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2008-02-13 Thread Jeremy Nickurak 
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/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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2008-02-13 Thread Kees Cook 
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 contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2008-02-13 Thread Jeremy Nickurak 
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: 4.2.32-1ubuntu1
  Version table:
 *** 4.2.32-1ubuntu1 0
500 http://ubuntu.arcticnetwork.ca hardy/main Packages
100 /var/lib/dpkg/status

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2008-02-13 Thread Kees Cook 
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
ionice -c $IONICE_CLASS $priority -p $$ > /dev/null 2>&1 || true

-n and -p are used correctly here.  Am I misunderstanding something?

** Changed in: findutils (Ubuntu)
 Assignee: Martin Pitt (pitti) => Kees Cook (keescook)
   Status: In Progress => Invalid

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2008-02-10 Thread Martin Pitt 
** 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 Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2008-02-10 Thread Jeremy Nickurak 
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 the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-28 Thread C 
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.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-27 Thread Magnus Wissler 
 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.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-27 Thread Magnus Wissler 
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 should I report this as a new bug?

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-21 Thread Martin Pitt 
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 is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-20 Thread Brian Murray 
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".

** Tags added: verification-done

** Tags removed: verification-needed

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-18 Thread Martin Pitt 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-18 Thread Matt "Cyber Dog" LaPlante 
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/cron.daily/slocate replaces this functionality.  Since the script included 
with slocate is not broken (at least in this regard), anyone who has slocate 
installed is essentially unaffected by this bug.

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-18 Thread Kees Cook 
** 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 ionice with the -p flag, however according to 
the ionice man page, the -p flag specifies a pid.  This causes ionice to fail 
to run.
  cd / && nice -n ${NICE:-10} ionice -c ${IONICE_CLASS:-2} -p 
${IONICE_PRIORITY:-7} updatedb
  
  > ioprio_set: No such process
  
  " -p Pass in a process pid to change an already running  process. "
  
  TEST CASE:
  1) force updatedb (/etc/cron.daily/find) to run via 'sudo 
/etc/cron.daily/find'
- 2) while updatedb runs, examine io priority with "ionice $(pidof updatedb)"
+ 2) while updatedb runs, examine io priority with "ionice -p $(pidof updatedb)"
  3) should report "best-effort: prio 7" (broken behavior shows "none: prio 0")

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-18 Thread Brian Murray 
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.slocate has 'IONICE_PRIORITY' with '-n'

Additionally, when I installed the proposed package the file
'/etc/cron.daily/find.notslocate.dpkg-new' was created and this has
'IONICE_PRIORITY' with '-n' in it.  From looking at the slocate package
it is also included in all the -desktop tasks.  Hence my question.

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-18 Thread Brian Murray 
** 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 ionice with the -p flag, however according to 
the ionice man page, the -p flag specifies a pid.  This causes ionice to fail 
to run.
  cd / && nice -n ${NICE:-10} ionice -c ${IONICE_CLASS:-2} -p 
${IONICE_PRIORITY:-7} updatedb
  
  > ioprio_set: No such process
  
  " -p Pass in a process pid to change an already running  process. "
  
  TEST CASE:
- 1) wait for updatedb (/etc/cron.daily/find) to run from cron (happens daily 
at 06:25 -- adjust system clock to force a run)
+ 1) force updatedb (/etc/cron.daily/find) to run via 'sudo 
/etc/cron.daily/find'
  2) while updatedb runs, examine io priority with "ionice $(pidof updatedb)"
  3) should report "best-effort: prio 7" (broken behavior shows "none: prio 0")

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-18 Thread Kees Cook 
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.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 ionice with the -p flag, however according to 
the ionice man page, the -p flag specifies a pid.  This causes ionice to fail 
to run.
  cd / && nice -n ${NICE:-10} ionice -c ${IONICE_CLASS:-2} -p 
${IONICE_PRIORITY:-7} updatedb
  
  > ioprio_set: No such process
  
  " -p Pass in a process pid to change an already running  process. "
+ 
+ TEST CASE:
+ 1) wait for updatedb (/etc/cron.daily/find) to run from cron (happens daily 
at 06:25 -- adjust system clock to force a run)
+ 2) while updatedb runs, examine io priority with "ionice $(pidof updatedb)"
+ 3) should report "best-effort: prio 7" (broken behavior shows "none: prio 0")

-- 
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-18 Thread Kees Cook 
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.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-12 Thread Martin Pitt 
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 bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-11 Thread Kees Cook 
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 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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 152692] Re: updatedb cron job re-nices wrong process (pid 7 by default)!

2007-12-09 Thread dAniel hAhler 
** 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 the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs