This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig42C0110941AE2353D253F8C6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
could you send a tcpdump of the traffic between scanimage and saned? I
don't have xinetd running, so it's hard to te
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
On Thursday 19 September 2002 00:15, Robert Kleemann wrote:
> 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 had a very similar problem when I forgot to create the sa
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enig97ABF95867FD8DFC70AE985C
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Hi,
Robert Kleemann wrote:
> Sure, I ran "tcpdump -i any -x -s 1024" and then ran "scanimage -L"
> locally. You can fin
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
Hi,
On Thu, Sep 19, 2002 at 12:48:13PM -0700, Robert Kleemann wrote:
> The bash error was due to overly restrictive permissions that I had on
> the /root directory.
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?
> 1) If
Hi,
On Thu, Sep 19, 2002 at 10:21:38AM +0100, Martyn Ranyard wrote:
> On Thursday 19 September 2002 00:15, Robert Kleemann wrote:
> > 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 w
> 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
