Re: [cups-devel] Life time of CUPS subscriptions
Michael Sweet <[email protected]>
| Newsgroups | gmane.comp.printing.cups.devel |
|---|---|
| Message-ID | <[email protected]> |
Till, > On Jan 9, 2016, at 8:03 PM, Till Kamppeter <[email protected]> wrote: > > Hi, > > I am working on a CUPS environment on mobile devices where the CUPS daemon is running on-demand, meaning that it is started by socket activation and stops after a certain time (30 or 60 seconds) of inactivity. > > In the current CUPS, the scheduler is prevented from automatically shutting down if there are subscriptions from any applications. Please file a bug - we should not be doing this for push notifications (e.g. dbus and rss as shipped in CUPS). For pull (ippget) notifications we will want to keep running since the client doing the pull will cause cupsd to restart... :/ > ... > Would it be then perhaps even a good idea if the entries in subscriptions.conf had the requesters PID and CUPS checks from time to time whether the requester is still alive and cleans up if needed? No, because then subscriptions cannot exist beyond the life of an application which is definitely not how they are supposed to work... _________________________________________________________ Michael Sweet, Senior Printing System Engineer