>So that's the earliest they will be run. At the other end, >gnome-session waits for all postrun scripts in the JDS_wait >class to complete before the session is started. (A progress bar >is displayed, the label is something like 'completing post >installation confirugation'.). > >The current consumers are at the desktop level (note that >postrun is JDS Consolidation Private), so that should be early >enough but not too early for the installation of desktop components. >I agree this could be a limitation if postrun was used outside >the desktop stack.
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. Will its use be sufficiently discouraged? (And will current postrun consumers be fixed to run more efficiently)? I note that this is a lot worse for people who update biweekly,, but I also wonder why postrun needs to run at standard priority? Some systems will run certain services faster and appear up more quickly if postrun is run at a lower CPU priority. Casper
