-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Jonathan Chong wrote:

If xinetd is running, portmap is running, and sgi_fam is enabled then fam *should* be working? Are you still getting the error?

If it's not working then what does "rpcinfo -p localhost" show? Do you see the fam service registered? If not then try running xinetd by hand with the '-d' switch. That may tell you why it's bombing out. On my suse box the fam config file for xinetd didn't specify a user and so it always silently died. I didn't figure it out until I ran "xinetd -d" from the command line and saw the error message. Once I put a "user = nobody" into the file then fam started up with no trouble.

If fam is running but courier still can't talk to it then I'd start over; go back and walk through the steps again. Portmap, xinetd, sgi_fam. If those three are properly set up and running then this *should* work. Go back over the messages from Gordon and me and see what you might have missed.

iD8DBQFDsvPaZxtYeNk78A8RAj1rAJ47N9fYYcn8G76T7LfSlDwyZAb9jACcDhj4 1NbOtTYVyoCOMXlRDqnPxdI= =YmuU -----END PGP SIGNATURE-----