I have problems with this too...Any entry written in inetd.conf won't be
started until you run the inetconv program.  However, when I run this, I
get 
"inetconv: Error /etc/inet/inetd.conf line 32 invalid or inconsistent
fields: service-name protocol" 

-----Original Message-----
From: owner-amanda-users AT amanda DOT org
[mailto:owner-amanda-users AT amanda DOT org] On Behalf Of Jon LaBadie
Sent: Wednesday, February 22, 2006 1:52 PM
To: amanda-users AT amanda DOT org
Subject: Re: Solaris 10 and amanda

On Wed, Feb 22, 2006 at 11:40:43AM -0700, Ali Moeinvaziri wrote:
> 
> I just wonder if anybody has been able to successfully configure a 
> solaris 10 client to work with amanda.
> 
> I have problems connecting to the client through amanda. The amanda 
> inetd.conf entry is converted to solaris 10 service, by using 
> inetdconv utility. The service is enabled and on-line.
> Yet, when I do 'amcheck -c', the client times out.
> 
> Any ideas?

Does amanda even get started?  Check for its debug and/or log files.
The former are probably in /tmp/amanda on the client.  Another way to
check would be replace amandad on the client with a simple shell script
that writes to a log file the date/time, arguments it was called with,
and possibly the environment and user/group ids.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)



__________________________________________________________
Message transport security by GatewayDefender.com
1:52:55 PM ET - 2/22/2006


__________________________________________________________
Message transport security by GatewayDefender.com
2:39:54 PM ET - 2/22/2006