Hi, ToddAndMargo writes:
> Hi All, > > When configuring saned, what is the difference between the access > list in > > /etc/sane.d/saned.conf > > and > > /etc/saned.conf By default, saned looks for saned.conf in the directory that was specified at build time. For most Linux distributions this will be /etc/sane.d, the result of passing a --configdir=/etc option to the configure script (which tags the /sane.d part on by itself). Using the *normal* build and install procedures that are part of sane-backends, there is *no* way you would get an /etc/saned.conf. Any chance you put this there yourself? If you really want to use /etc/saned.conf, you need to use SANE_CONFIG_DIR=/etc saned ... As far as file contents is concerned, both are processed in the same way. It only a matter of which one is used and, as said, the default is to use the first. Hope this helps, -- Olaf Meeuwissen, LPIC-2 FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Software https://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
