> But if you used user saned.saned why bash tried to access /root?
> And if you run as root why it couldn't read inside /root?
I think it has to do with the fact that when root starts a new shell
with reduced permissions, the new shell tries to read /root/.bashrc If
it can't read it then it is a n
Thanks for the help. I think I'm making progress.
The bash error was due to overly restrictive permissions that I had on
the /root directory. (700 instead of 755) I changed these and the
problem went away. I also changed #!/bin/bash to #!/bin/sh although
I'm not sure what effect this will have s
At Thu, 19 Sep 2002 09:52:38 +0200,
Jochen Eisinger wrote:
> could you send a tcpdump of the traffic between scanimage and saned?
Sure, I ran "tcpdump -i any -x -s 1024" and then ran "scanimage -L"
locally. You can find the output at:
http://www.kleemann.org/crap/tcpdump1
I'm trying to verify th
I've been banging my head on this all afternoon so it's time to seek
help.
Summary: saned runs fine as a standalone server (saned -d128) but
fails when run from xinetd.
I'm running the redhat 7.3 dist with all updates:
$ rpm -qa | grep sane
sane-frontends-1.0.7-2
xsane-0.84-2
sane-backends-1.0.7-
