| |||||||||||||
|
| |||||||||||||
Poettering: Rethinking PID 1Poettering: Rethinking PID 1Posted Apr 30, 2010 20:03 UTC (Fri) by jwb (guest, #15467)In reply to: Poettering: Rethinking PID 1 by cesarb Parent article: Poettering: Rethinking PID 1
That just sounds like an annoying way to find out late in the process that your bluetooth config is screwed up, and the only savings you gain is 1MB or so of private memory that bluetooth daemons consume.
(Log in to post comments)
Poettering: Rethinking PID 1 Posted May 1, 2010 2:08 UTC (Sat) by zlynx (subscriber, #2285) [Link]
Possibly, if Linux swap wasn't so messed up, you could leave your unused daemons running for days without a problem.
But I know from personal experience, those unused daemons will have all their allocated RAM swapped out into tiny 4K pieces that will take 10-20 seconds for a laptop drive to re-collect.
It's much faster to start the daemon from scratch than to swap it in.
Poettering: Rethinking PID 1 Posted May 6, 2010 2:51 UTC (Thu) by JoeBuck (subscriber, #2330) [Link] Well, if your daemon has a memory leak, it's certainly faster to start it from scratch than to swap it in.
Poettering: Rethinking PID 1 Posted May 6, 2010 15:58 UTC (Thu) by zlynx (subscriber, #2285) [Link]
Unless gvfsd, gdm, cupsd, smbd and bluetoothd *all* have memory leaks, that isn't the problem.
Poettering: Rethinking PID 1 Posted May 1, 2010 8:26 UTC (Sat) by xav (subscriber, #18536) [Link]
Hey, my N900 runs Linux and has only 256Mb RAM. These days it's became my main computer, so I welcome any improvement in RAM or power consumption whatsoever.
|
|
||||||||||||