Your message dated: Tue, 29 May 2001 16:43:11 EDT
--------
> What appears to be the problem and which I should have made clearer is
> that inetd is not interpretting the return value of the forking child
> properly and aparently instead is attempting to spawn forty copies of
> amandad. So it is running into the inetd connection limit but its never
> actually launching anything.
>
> Incidentally, Amanda works on my Solaris 7 boxen with BSM enabled so I
> guess what I should have asked is this:
>
> First, does anyone have Amanda running with Solaris 8 and BSM auditing?
>
> Secondly, if not, would you classify the signalling problem as a Solaris
> problem or an amanda problem? I'm pretty certain it is a Solaris problem
> but I want to make sure that its not a bug that still allows amandad to
> run under less-observed conditions but makes it barf under an audited one
> (ala Schrodinger's cats). I'll submit as a bug to Sun - hopefully someone
> can confirm this behaviour though.
Kevin,
I have seen this problem. I suspect it is a Solaris problem but I
can't be sure since I have not investigated it fully. However, I have
gotten it to work using a hack.
Make a small script called "run-amandad" and put it in the directory with
the other amada executables <amanda-path>:
#!/bin/sh
su amanda -c <amanda-path>/amandad
Then change your inetd.conf line to:
amanda dgram udp wait root <amanda-path>/run-amandad amanda
I've been using this for a while and I haven't had any problems with it.
Regards,
Dan Lorenzini Greenwich Capital Markets
[EMAIL PROTECTED] 600 Steamboat Road
203-625-6088 Greenwich, CT 06830
**********************************************************************
This e-mail is intended only for the addressee named above.
As this e-mail may contain confidential or privileged information,
if you are not the named addressee, you are not authorised to
retain, read, copy or disseminate this message or any part of it.
************************************************************************
