Re: [sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?
On 01/31/2018 03:28 AM, Olaf Meeuwissen wrote: Hi, ToddAndMargo writes: Hi Olaf, What is this comment inside /etc/sane.d/saned.conf? # NOTE: /etc/inetd.conf (or /etc/xinetd.conf) and # /etc/services must also be properly configured to start # the saned daemon as documented in saned(8), services(4) # and inetd.conf(4) (or xinetd.conf(5)). Why would I need both to get the saned daemon to work? If you run saned from systemd, ignore the comment. If you run saned from inetd or xinetd (please read the inetd(8) or xinetd(8) manual pages or have a look a their Wikipedia entries for what these daemons do), the usual setup refers to a sane-port "service" in their configuration file, the number of which service is normally defined in /etc/services. BTW, all of this is also documented in the saned(8) manual page, pointed to in the comment itself and the documentation for the files mentioned, which the comment points you to as well, and only a quick search engine request away. Hope this helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join Thank you! -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~ -- 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
Re: [sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?
On 01/29/2018 12:33 PM, ToddAndMargo wrote: On 01/27/2018 03:18 AM, Olaf Meeuwissen wrote: 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, Hi Olaf, What is this comment inside /etc/sane.d/saned.conf? # NOTE: /etc/inetd.conf (or /etc/xinetd.conf) and # /etc/services must also be properly configured to start # the saned daemon as documented in saned(8), services(4) # and inetd.conf(4) (or xinetd.conf(5)). Why would I need both to get the saned daemon to work? -T Anyone? -- 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
Re: [sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?
On 01/27/2018 03:18 AM, Olaf Meeuwissen wrote: 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, Hi Olaf, What is this comment inside /etc/sane.d/saned.conf? # NOTE: /etc/inetd.conf (or /etc/xinetd.conf) and # /etc/services must also be properly configured to start # the saned daemon as documented in saned(8), services(4) # and inetd.conf(4) (or xinetd.conf(5)). Why would I need both to get the saned daemon to work? -T -- 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
Re: [sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?
On 01/27/2018 03:18 AM, Olaf Meeuwissen wrote: 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-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join Thank you! I will remove the /etc/saned one. -- ~~ Computers are like air conditioners. They malfunction when you open windows ~~ -- 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
Re: [sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?
On 01/27/2018 03:18 AM, Olaf Meeuwissen wrote: 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, Hi Olaf, What is this comment inside /etc/sane.d/saned.conf? # NOTE: /etc/inetd.conf (or /etc/xinetd.conf) and # /etc/services must also be properly configured to start # the saned daemon as documented in saned(8), services(4) # and inetd.conf(4) (or xinetd.conf(5)). Why would I need both to get the saned daemon to work? -T -- 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
Re: [sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?
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-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://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
[sane-devel] /etc/sane.d/saned.conf vs /etc/saned.conf?
Hi All, When configuring saned, what is the difference between the access list in /etc/sane.d/saned.conf and /etc/saned.conf Many thanks, -T -- 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
