Casper.Dik at Sun.COM wrote: >> On Tue, 2008-02-05 at 09:12 +0100, Casper.Dik at Sun.COM wrote: >> >>> I find that postrun currently is an abomination (or at least the >>> consumers are); it runs 10,000s of processes (literally) and takes >>> a long time; making it public would likely make this worse. >>> >> I find that number surprising. It shouldn't be the case and if >> it is, there are bugs to be fixed (probably incorrect or >> unnecessary scripts in the consumers). I fixed a few in some >> scripts in recent development builds, targetting snv_88. >> > > Well, look at the PIDs you get when you login after boot. > > E.g., this system was live upgraded and booted; (17:34 on 1/31) and > dtlogin started on 17:36 on 1/31 has PID 15164, initrd 13010, etc) > > So certainly SOMETHING ran 10,000+ processes. I've seen complaints about > this in other places too. >
Hmmm, too bad process accounting isn't available early on in bootup, that'd at least allow some evidence gathering. Darren
