On Jul 18, 2014, at 3:13 PM, Gene Heskett <ghesk...@wdtv.com> wrote:
> On Friday 18 July 2014 15:49:47 Debra S Baddorf did opine
> And Gene did reply:
>> ps auxww | grep net
>
> Except for PID's both machines are identical:
> shop:
> gene@shop:/etc$ ps auxww | grep net
> root 13 0.0 0.0 0 0 ? S Jul11 0:00 [netns]
> root 1128 0.0 0.0 1984 684 ? Ss Jul11 0:00
> /usr/sbin/inetd
> gene 15807 0.0 0.0 3352 888 pts/5 S+ 16:03 0:00 grep
> --color=auto net
>
> lathe:
> gene@lathe:/etc$ ps auxww | grep net
> root 13 0.0 0.0 0 0 ? S Jul17 0:00 [netns]
> root 4386 0.0 0.0 2132 748 ? S 15:45 0:00
> /usr/sbin/inetutils-inetd
> gene 4427 0.0 0.0 3352 884 pts/1 S+ 16:03 0:00 grep
> --color=auto net
>
> Humm,no they are not! but a bare inetd is not now available from the repos.
> The shop box apparently has (its a 2 year old install) openbsd-inetd
> whereas the lathe has inetdutils-inetd. Shouldn't they work alike?
>
> Cheers, Gene Heskett
Ahh! OK — inetd not xinetd.
Heres an AMANDA specific instruction:
Steps
1. Edit /etc/inetd.conf and add this line to the end of the file, if there is
any old amanda related lines comment them out:
amanda stream tcp nowait amandabackup /usr/lib/amanda/amandad amandad
-auth=bsdtcp amdump amindexd amidxtaped
my comment: change “amandabackup” to your username
check that the location is right for you
change to “auth=bsd” if that’s what the
working node has
2. Edit /etc/services and add this line to the end of the file, if there is any
old amanda related lines comment them out:
amanda 10080/tcp # amanda backup services
3. Restart the inetd demon and check for errors in the system log files
Deb Baddorf
I defer to anybody else who still uses this, but if no other suggestions, try
the above!
I used to use it; and it does look familiar.
