The debug logs *do* look different, so this was at least a minimal improvement:
On Wed, Jul 16, 2008 at 2:26 PM, Mister Olli <[EMAIL PROTECTED]> wrote:
> amandad: debug 1 pid 80108 ruid 1002 euid 1002: start at Wed Jul 16
> 20:21:46 2008
vs. (earlier)
> -auth=bsd: debug 1 pid 76969 ruid 1002 eui
hi...
the problem seems to be related to something different. I fixed the
inetd config and put in a 'amandad' and also replaced that with the
'/usr/local/libexec/amanda/amandad' but still no success.
The debug file looks exactly the same like before:
# cat amandad/amandad.20080716202146.debug
a
Mister Olli wrote:
hi...
my /etc/inetd.conf looks like this on all of my freebsd 7 systems.
amanda dgram udp waitamanda /usr/local/libexec/amandad
-auth=bsd amdump amindexd amidxtaped
A 'amandad' is missing, it should be:
amanda dgram udp wait amanda /usr/local/libexec/amandad
On Wed, Jul 16, 2008 at 9:46 AM, Mister Olli <[EMAIL PROTECTED]> wrote:
> amanda dgram udp waitamanda /usr/local/libexec/amandad
> -auth=bsd amdump amindexd amidxtaped
It looks like amandad is thinking that -auth=bsd is its name, which
means that it saw that in argv[0]
Try
amanda dg
hi...
my /etc/inetd.conf looks like this on all of my freebsd 7 systems.
amanda dgram udp waitamanda /usr/local/libexec/amandad
-auth=bsd amdump amindexd amidxtaped
and it works like a charm, except for that one system... gladly I'm only
the backup-administrator of that system. I wa
Mister Olli wrote:
Hi...
when I try to do an 'amcheck' on my daily backup jobs I have one system,
that does not pass the selftest.
it's configured identically to some other machines that work like a
charm.
the debug output of 'amandad' on the client side looks like this:
-auth=bsd: debug 1 pid
Hi...
when I try to do an 'amcheck' on my daily backup jobs I have one system,
that does not pass the selftest.
it's configured identically to some other machines that work like a
charm.
the debug output of 'amandad' on the client side looks like this:
-auth=bsd: debug 1 pid 76969 ruid 1002 euid