-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Noticed the following when conducting torture tests today:
[2006/05/12 14:04:24, 0] printing/pcap.c:pcap_cache_reload(159) Unable to open printcap file /etc/printcap for read! ...which to me, was interesting, because I was not under the impression I was using load printers. Apparently, at some point, it became the default. That's fine, but I don't want it, so I turned it off. However, I still get the error. I see the only other option that is in place now is: printcap cache time = 750 Should this really have any effect if you have "load printers" turned off? Who cares if you can't read the /etc/printcap if you aren't supposed to be using it for anything? At any rate, adjusting it to 0 did not help anything. My final solution was to set "printcap name = /dev/null" Probably not the desired solution. Comments? - -- ---- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - User Support Spec. III |$&| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (MingW32) iD8DBQFEZNBcmb+gadEcsb4RArnRAJsGtSVd2JLtBz9wtH7DnKU9I7sz2wCggyNR Gi1ti7+7OUQyIgi68Jb5XTo= =c4H4 -----END PGP SIGNATURE----- -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
