>... Trussing the inetd binary and attempting to connect to the amanda service
>reveals the following error:
>
>auditsys(36, 0xFFBEF4A0) Err#22 EINVAL
>write(2, " i n e t d : s e t a u".., 20) Err#96 EDESTADDRREQ
You might run that again with "-w 2" or "-w all" on the truss line.
I think that will display the whole message.
>But at least we know what the problem is now ... somehow amandad causes inetd
>to fail the auditing process, which leads to it being killed.
Does the amandad entry in inetd.conf look similar to the other entries
post-BSM? In other words, did BSM alter inetd.conf and maybe the standard
line no longer works?
Is all the rest of BSM working for you, i.e. the daemon is running,
you can display the audit trails, etc? In particular, do you have any
other UDP services, such as talkd (just to test), that are working?
The EDESTADDRREQ error implies inetd (note: inetd, not amandad) didn't
have a connection fully set up when it tried to do something. Maybe that
was to auditd? Or maybe it just plain screwed up?
Note that I don't know anything about BSM other than what I've read on
the web documention in the last 10 minutes.
>- John
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
