Date: Sat, 21 Aug 1999 19:11:33 -0700 From: Doug <Doug@gorean.org> To: freebsd-current@freebsd.org, dbaker@distributed.net Subject: Weird differences in rc5 behavior on -current vs. -stable Message-ID: <37BF5C55.519542EF@gorean.org>
next in thread | raw e-mail | index | archive | help
I have a 3.2-Stable and a 4.0-Current system at home, both running rc5des. On both systems I set the priority in the rc5 options menu to '0', indicating lowest possible priority. On the -Stable system it's running at nice level '0', but it seems to be taking advantage of the idprio stuff since in general my system seems much "snappier," than when I was running 2.2.8 on the exact same machine. On the -current box rc5des shows up as nice level 20, and although it's a pretty snappy system (this is my workstation machine with a celeron 300A and lots of ram) I thought the difference to be pretty strange. The rc5des.ini files for both machines are identical (except for the random value). Also, when rc5des runs on the -current system I get this: ps -ax | grep rc5des 59048 p0 S 0:00.02 _su -m -c /usr/local/distributed.net/rc5des -quiet (c 59062 p0 RN 0:01.63 /usr/local/distributed.net/rc5des -quiet whereas on the -stable system there is no ghost su process. This is with the latest version of rc5 installed from the ports. These aren't major problems, but it's often the small things like this that indicate an area of concern elsewhere, so I thought I'd mention it. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?37BF5C55.519542EF>