sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2024-12-24 21:34:56 +03:00
Code
0d30d74e89
samba-mirror/docs-xml/smbdotconf/printing/printcapcachetime.xml

19 lines
570 B
XML
Raw Normal View History

adding docs for 'printcap cache time' -- patch from Lars (This used to be commit bc2b0b8ae955966f760e9ec38659befb6641bc3b)
2004-05-20 20:34:25 +04:00
<samba:parameter name="printcap cache time"
docs:smbdotconf: make formatting of headers uniform. Signed-off-by: Michael Adam <obnox@samba.org> Reviewed-by: Jeremy Allison <jra@samba.org>
2015-05-01 00:32:45 +03:00
context="G"
type="integer"
Update DTD location (This used to be commit 889dfcc532bd3357314313fe8f70a022a174eef4)
2005-03-13 01:41:20 +03:00
xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
adding docs for 'printcap cache time' -- patch from Lars (This used to be commit bc2b0b8ae955966f760e9ec38659befb6641bc3b)
2004-05-20 20:34:25 +04:00
<description>
<para>This option specifies the number of seconds before the printing
s3-printing: Initiate pcap reload from parent smbd Since commit 7022554, smbds share a printcap cache (printer_list.tdb), therefore ordering of events between smbd processes is important when updating printcap cache information. Consider the following two process example: 1) smbd1 receives HUP or printcap cache time expiry 2) smbd1 checks whether pcap needs refresh, it does 3) smbd1 marks pcap as refreshed 4) smbd1 forks child1 to obtain cups printer info 5) smbd2 receives HUP or printcap cache time expiry 6) smbd2 checks whether pcap needs refresh, it does not (due to step 3) 7) smbd2 reloads printer shares prior to child1 completion (stale pcap) 8) child1 completion, pcap cache (printer_list.tdb) is updated by smbd1 9) smbd1 reloads printer shares based on new pcap information In this case both smbd1 and smbd2 are reliant on the pcap update performed on child1 completion. The prior commit "reload shares after pcap cache fill" ensures that smbd1 only reloads printer shares following pcap update, however smbd2 continues to present shares based on stale pcap data. This commit addresses the above problem by driving pcap cache and printer share updates from the parent smbd process. 1) smbd0 (parent) receives a HUP or printcap cache time expiry 2) smbd0 forks child0 to obtain cups printer info 3) child0 completion, pcap cache (printer_list.tdb) is updated by smbd0 4) smbd0 reloads printer shares 5) smbd0 notifies child smbds of pcap update via message_send_all() 6) child smbds read fresh pcap data and reload printer shares This architecture has the additional advantage that only a single process (the parent smbd) requests printer information from the printcap backend. Use time_mono in housekeeping functions As suggested by Björn Jacke.
2010-12-23 14:14:21 +03:00
subsystem is again asked for the known printers.
adding docs for 'printcap cache time' -- patch from Lars (This used to be commit bc2b0b8ae955966f760e9ec38659befb6641bc3b)
2004-05-20 20:34:25 +04:00
</para>
More doc fixes by Tom Bork -- thanks :-) (This used to be commit af1abf9986f8d79c891cd8f94e101d5c0f69f261)
2007-03-05 21:33:11 +03:00
<para>Setting this parameter to 0 disables any rescanning for new
or removed printers after the initial startup.
adding docs for 'printcap cache time' -- patch from Lars (This used to be commit bc2b0b8ae955966f760e9ec38659befb6641bc3b)
2004-05-20 20:34:25 +04:00
</para>
</description>
Fix doc defaults report by Tom Bork -- Thanks :-) (This used to be commit 07638766645dbb2377cf17f5e7d66140239ed67e)
2007-03-04 10:01:11 +03:00
<value type="default">750</value>
adding docs for 'printcap cache time' -- patch from Lars (This used to be commit bc2b0b8ae955966f760e9ec38659befb6641bc3b)
2004-05-20 20:34:25 +04:00
<value type="example">600</value>
</samba:parameter>
Copy Permalink