BTW, I note that the Ubuntu guide you referred to mentioned using the following config directives in the saned.socket unit file
Code:
# Defaults for the saned initscript, from sane-utils Code:
[Unit] |
Quote:
|
I changed saned.socket by removing the first lines, now it's exactly the same as yours, but still no luck.
I also updated the host to 1.0.27 via github, nothing changes. It's very interesting that you get the same behaviour I have using StandardInput=null. I'm using StandardInput=socket, as you do, but it may be that, for some reasons, this option is not set, and the issue is due to that... |
What happens if you remove (or comment out) the User= and Group= directives?
|
Nothing...
|
Does /etc/default/saned exist? If so, what does it contain?
|
Well, I don't know what happens, but now it works...
Looking at the log, now the correct IP appears asking access, and the access is granted. I can use the scanner from the client. The only thing that occurs to me is that I didn't perform a reboot after the upgrade to 1.0.27. After the reboot, now it seems to work, it may be thanks to the update. At least, this seems to me the only possibility. I will test it in the next few days, and let you know if it stops working again. Thanks a lot for the help, I was completely stuck... |
Glad to have walked with you on this one, and good to read of you success with this finally! :)
|
All times are GMT -5. The time now is 05:54 PM. |