On Thu, May 16, 2013 at 03:02:53PM -0400, Jean-Louis Martineau wrote:
> On 05/16/2013 02:53 PM, Brian Cuttler wrote:
> >/tmp/amanda/amandad - which was created by the manual run
> >of amandad, no new files.
>
> If telnet do not create a new debug file it is because amandad is not
> executed, which means SMF is misconfigured.
> I can't help with SMF.
OS specific issue, I can appreciate that. Thank you.
Does anyone have a clue as to how I've misconfigured SMF on Solaris 10?
My amanda config on Finsen, which is a solaris 10/x86 amanda server
that has only itself as a client, has the following entry in inetd.conf
amanda stream tcp nowait amanda /usr/local/libexec/amanda/amandad
amandad -auth=bsdtcp amdump
This is identical to the entry in inetd.conf on Grifserv, the new
amanda client I'm trying to upgrade for amanda server Curie.
service output information is identical on the two machines.
# svcs -l svc:/network/amanda/tcp:default
fmri svc:/network/amanda/tcp:default
name amanda
enabled true
state online
next_state none
state_time Thu May 16 14:31:24 2013
restarter svc:/network/inetd:default
contract_id
The manifest services give every indication of being identical.
[finsen]: /var/svc/manifest/network > ls -l *amanda*
-rw-r--r-- 1 root root 2320 Feb 9 01:05 amanda-tcp.xml
-rw-r--r-- 1 root root 2485 Feb 9 01:05 amanda-udp.xml
-rw-r--r-- 1 root root 2292 Feb 27 2009 amandaidx-tcp.xml
# ls -l *amanda*
-rw-r--r-- 1 root root 2320 May 16 14:31 amanda-tcp.xml
# wc amanda-tcp.xml
82 227 2320 amanda-tcp.xml
# cksum amanda-tcp.xml
4135061186 2320 amanda-tcp.xml
... I'm going to have another look at the dumptype definitions.
---
Brian R Cuttler [email protected]
Computer Systems Support (v) 518 486-1697
Wadsworth Center (f) 518 473-6384
NYS Department of Health Help Desk 518 473-0773