On 1/29/2014 1:24 PM, Dimitri Maziuk wrote: > On 01/29/2014 10:26 AM, Josh Fisher wrote: > >> ... The question >> is, how do you inform Linux and OSX that a daemon is to be considered >> active even if it would otherwise fall into the category of inactive >> because, say, there is an open TCP socket, but there has not been any >> network traffic in X amount of time? > The converse is also true: how do you tell the system that e.g. syslogd > is to be considered "ok to suspend" even though it's "active" as in > "writing stuff to log files"? > > And then there's cron you need to un-suspend in time to start a > scheduled cron job.
And the timing issue should some daemons need to suspend in any particular order. It is a very complex problem. I believe Linux basically handles PM at the device driver level. This allows a finer grain control over PM, putting individual devices in and out of different power states on the fly in a running system. As a result, it may not be so simple to prevent the NIC from putting its PHY into low power or off states. Perhaps the pm_utils source sheds some light on how a daemon could prevent a system-wide suspend. ------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
