On Sat, Dec 15, 2007 at 01:34:06AM +0100, intrigeri wrote:
> Craig Sanders wrote (14 Dec 2007 23:48:20 GMT) :
> > i.e. is this a complete incompatibility between ionice and vserver
> > (in which case, the bug should be filed against ionice's package
> > util-linux), or is it due to the kernel version and/or kernel
> > compile-time options (i.e. no CFQ scheduler) that you're running?
>
> This is Linux 2.6.22.14, with CFQ scheduler built in the kernel, and
> enabled by default (ie. CONFIG_DEFAULT_IOSCHED="cfq"). ionice works
> well outside the VServers, I use it myself for other tasks. Then it is
> not due to the kernel.
>
> On the other hand, I don't consider this as a ionice bug: ionice
> purpose being to set a program's IO priority, it's quite normal it
> outputs an error message on stderr when it is denied to do its job (be
> it because of grsecurity, VServer, SE-Linux or whatever way to
> restrict root processes capabilities).
>
> That's why I still consider this as a dlocate bug (and locate: see
> #456291).
i've already updated the /etc/cron.daily/dlocate script like so:
if [ -x /usr/bin/ionice ]; then
# don't run ionice if kernel version < 2.6.13
KVER=$(uname -r)
case "$KVER" in
2.[012345]*) ;;
2.6.[0-9]) ;;
2.6.[0-9].*) ;;
2.6.1[012]*) ;;
*) ionice -c3 -p$$ > /dev/null 2>&1 ;;
esac
fi
that should solve the problem. the redirection of stderr is for vserver
and other environments where ionice doesn't work.
the other stuff is to avoid running ionice in kernel versions that don't
support it at all. not really necessary, just seemed a better way of
doing it.
craig
--
craig sanders <[EMAIL PROTECTED]>
BOFH excuse #347:
The rubber band broke
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
