On Thu, Jul 18, 2002 at 09:30:27AM -0400, Charlie Brady wrote: > > On Thu, 18 Jul 2002, Damien Curtain wrote: > > > > But I'm curious here -- what bits do you consider resource hogs? > > > > imp, mysql, pptp > > All optional. > > for i in imp php mysql pptp > do > /sbin/e-smith/db configuration setprop $i status disabled > done > /sbin/e-smith/signal-event post-upgrade > /sbin/e-smith/signal-event reboot
True I can remove those and alot of other things, I can strip it right back to the bones and have a psuedo 4.1.x type install, then again I could just install 4.1.2 on older machines with redhat's updates. You haven't addressed the heavy load on a machine from the increase in actions and events, older machines groan under the load of a 5.x signal-event. On a 4.1.x I see ~65 actions, ~35 events, over 150 actions on 5.5, ~50 events on 5.5. Give or take a few for contribs/my own patches. Perhaps Im the only person on these lists who believes that the minimum requirements of a machine for e-smith has increased since 4.x releases, but what's the point of updating to new releases except for the newer features and some of the really useful contribs. But to throw in a for loop in your response is a bit much, you may be suprised but even I know how to do that much myself. -- Damien -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
