| |||||||||||||
Day: GNOME OSDay: GNOME OSPosted Aug 8, 2012 11:36 UTC (Wed) by slashdot (guest, #22014)In reply to: Day: GNOME OS by hummassa Parent article: Day: GNOME OS
Well, the problem is that systems can just never get rebooted, and anyway waiting for reboot is suboptimal.
So, you need either the kernel or a daemon that can notice the application files are no longer in use and can zap then quickly.
Not totally sure on the best mechanism for that, but it's definitely possible.
(Log in to post comments)
Day: GNOME OS Posted Aug 8, 2012 13:16 UTC (Wed) by nix (subscriber, #2304) [Link]
Well, once applications fall out of use they never go back into use again (since new invocations will invoke the new one): so have a cronjob that periodically hunts across deleted applications for files no longer in use by anything, and deletes them. This won't be noticeable performance-wise because most deleted applications will be not-in-use the instant they are removed, so can be aggressively deleted.
(Personally, I keep my versioned per-app trees around for a month to allow for later downgrading. I have never had a single problem with the script that deletes them after that much time.)
Day: GNOME OS Posted Aug 8, 2012 16:41 UTC (Wed) by rahvin (subscriber, #16953) [Link]
Wouldn't that cause a severe impact to battery life on battery driven devices? You want everything sleeping unless it's in active use, what you suggest would keep the CPU active even when the device isn't being used. Of course if we don't concern ourselves with battery driven devices it's not a concern.
Day: GNOME OS Posted Aug 8, 2012 17:11 UTC (Wed) by drag (subscriber, #31333) [Link]
You'd only need to run it once a month or something like that. And there are numerous other cron jobs that perform tasks on Linux.
It wouldn't be difficult to put a logic into the cron job to check to see if it's on battery and delay until it's on the charger or above 80% charge or something of that nature.
|
|||||||||||||