--7ZAtKRhVyVSsbBD2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Mar 27, 2007 at 08:53:19PM +0000, Michael van Elst wrote:
> christos@astron.com (Christos Zoulas) writes:
>=20
> >It is useless in today's systems, and usually does the wrong thing
> >(nices long time running processes). So you have a machine that you
> >use as a web server, httpd will eventually get autoniced. You have
> >a DNS server, named gets autoniced, you have a mail server, well
> >you get the idea.
>=20
> Is that a problem? A niced process isn't slower unless you have
> non-niced processes, e.g. the login session of your friendly admin
> that tries to recover an overloaded system. Having the 'overload'
> processes running nice is at least a minor advantage.
>=20
> Now, if you think about interactive login sessions being autoniced down,
> this can be a nuisance. So the only solution is to disable the autonice
> and to nice down your services explicitely.

If you are running only one service, you're right that it's probably not=20
an issue. If however you have two or more services on the same box, which=
=20
ever one has run less gets more priority. It could well be that the server=
=20
that clocked more time did so as it's the more important service to=20
support. Thus autonice can mess up your QoS.

Take care,

Bill

--7ZAtKRhVyVSsbBD2
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (NetBSD)

iD8DBQFGCbM5Wz+3JHUci9cRAvvVAJ92ipLy/W/KQyqeR0RVPhlLgfEaCQCfUPSU
jU7OQgdqvdqKqeRei1YePic=
=lLFj
-----END PGP SIGNATURE-----

--7ZAtKRhVyVSsbBD2--