Rusty Ballinger wrote:
> Is /usr/sbin in your $PATH? If not, does /usr/sbin/rpcinfo -p work?
Yes that works here is what it gives me when i do that :
[root@Blackhawk nickh]# /usr/sbin/rpcinfo -p | grep fam
391002 2 tcp 880 sgi_fam
>
>
> Hoo, hey, look at that: http://www.xinetd.org/
>
> Bummer. From the FAQ:
>
> Q. xinetd doesn't work well with RPC, I need RPC and I really want to
> run xinetd. Can I?
>
> A. Yes. xinetd and inetd should happily coexist. Have your RPC stuff run
> from your normal inetd (removing all other services from your
> inetd.conf), then have xinetd run all your other services.
>
> fam does use RPC, sort of; libfam makes an RPC call to ask the portmapper
> what port to connect on.
>
> On the other hand, xinetd source does come with a program for converting
> inetd.conf to xinetd.conf; here's what it gave me for fam's entry:
>
> service sgi_fam
> {
> # itox didn't give this next line, but looking at the files
> # from your RH7 box make me think it might be a good idea.
> disable = no
> type = RPC
> rpc_version = 1-2
> socket_type = stream
> protocol = tcp
> wait = yes
> user = root
> server = /usr/local/bin/fam
> }
OK i added that to /etc/xinetd.d no problem there:::
>
>
> Try putting that in /etc/xinetd.d/fam, and going "killall -HUP xinetd"
> (hopefully that's one similarity between inetd & xinetd... according to
> the FAQ, it "understands different signals", and the unofficial tutorial
> says you should use -USR1 or -USR2, so you might try one of those if -HUP
> doesn't work). Then try running "/usr/sbin/rpcinfo -p | grep fam" to
> see whether xinetd registered it with the portmapper.
I did the killall -HUP , killall -USR1 and USR2 then i ran "/usr/sbin/rpcinfo
-p | grep fam" again to see what it gave me after killall that i ran and all
said the same thing.
[root@Blackhawk nickh]# /usr/sbin/rpcinfo -p | grep fam
391002 2 tcp 880 sgi_fam
and i tried uninstalling fam from the bad install im getting and it wont
uninstall the rpm it gives me this::
[root@Blackhawk rpm]# rpm -e fam-2.6.4-1
Removing fam from rpc...
Original file saved as /etc/rpc.O2
Removing fam from inetd.conf...
Original file saved as /etc/inetd.conf.O1
Restarting inetd...
inetd: no process killed
execution of fam-2.6.4-1 script failed, exit status 1
[root@Blackhawk rpm]#
so no it still doesnt work at all when i try to install it again just does the
same thing as before
>
>
> Let me know where that doesn't work. If we can get it to work through
> xinetd, that will be best, but if we can't do that, there are a couple
> of other ways we can do it.
>
> --Rusty
Thx again man for the help
Nick
--
Source code, list archive, and docs: http://oss.sgi.com/projects/fam/
To unsubscribe: echo unsubscribe fam | mail majordomo@xxxxxxxxxxx
|