dids wrote:
Well i figured out the name lookup problem. I reinstalled rman and let SuseConfig do its stuff. I see that http-rman is being called in Inetd, and I can see inetd running.
and i can see http-rman is allocated to 6711 in /etc/services
but i cant get any joy from rman
dids
+AD4- -----Original Message----- +AD4- From: System Administrator +AFs-mailto:root+AEA-CPKWEBSER5.ncr.disa.mil+AF0-On +AD4- Behalf Of Steven T. Hatton +AD4- Sent: 25 April 2000 14:40 +AD4- Cc: Suse-Linux-E +AD4- Subject: Re: +AFs-SLE+AF0- FW: +AFs-SLE+AF0- Does anyone have any advice on how to get +AD4- the man pages working ( susehelp ) 6.3 +AD4- +AD4- +AD4- dids wrote: +AD4- +AD4- +AD4- -----Original Message----- +AD4- +AD4- From: dids +AFs-mailto:diddy+AEA-host.diddyland.top+AF0- +AD4- +AD4- Sent: 25 April 2000 11:48 +AD4- +AD4- To: Steven T. Hatton +AD4- +AD4- Subject: RE: +AFs-SLE+AF0- Does anyone have any advice on how to get the man +AD4- +AD4- pages working ( susehelp ) 6.3 +AD4- +AD4- +AD4- +AD4- ok. there is a problem here in that nslookup doesnt know my +AD4- server ip lookup +AD4- +AD4- +AD4- +AD4- however if i try and access the same pages from the server ( +AD4- which does know the lookup ) +AD4- +AD4- I get the error +AD4- +AD4- +AD4- +AD4- I think that rman isnt lookup, i cant see it in the process +AD4- tree (pstree ) +AD4- +AD4- +AD4- +AD4- I have tried reinstalling the rman package. But i cant see rman +AD4- being called anywhere +AD4- +AD4- in the startup boot actions ? +AD4- +AD4- +AD4- +AD4- where should this be called +AD4- +AD4- +AD4- +AD4- does anyone know which rc.d script should be starting rman ? +AD4- +AD4- +AD4- +AD4- thanks +AD4- +AD4- dids +AD4- +AD4- +AD4- +AD4- on a second note. anyone know which file i need to put +AD4- +AD4- the localhost name ( host.diddyland.top ) to allow +AD4- +AD4- my win9x pcs to know that this is the server +AD4- +AD4- +AD4- +AD4- I'll probably figure the last one out, since it used to work. +AD4- +AD4- +AD4- +AD4- Dids, +AD4- +AD4- It doesn't show up as a separate process. Be srue inetd, or +AD4- xinetd is running. If not, you +AD4- can tell SuSEconfig to make it run by editing the rc.config. +AD4- This can be done in Yast with +AD4- the last option in the admin menu, or it can be done by hand. I +AD4- had a problem with xinetd +AD4- not being configured correctly by Yast so I went back to using +AD4- inetd. The file that tells +AD4- inetd what services to support is called /etc/inetd.conf. I +AD4- believe all this is handled by +AD4- something called tcpd and portmap. Yast will not only configure +AD4- your system to start +AD4- inetd, it will also configure it to run the rman stuff. This is +AD4- covered in the +AD4- documnetation. I don't have time to look it up right now, but if +AD4- you are still stuck I can +AD4- look later. I don't believe having entries in an /etc/hosts file +AD4- will get you around the +AD4- nslookup issue. Try using ip addresses in place of domain names +AD4- in the hosts.allow. I +AD4- believe this is done something like this 123.123.164. which tells +AD4- the system to allow every +AD4- thing sharing the first thre octets. You need the +ACI-.+ACI- at the +AD4- end. I think you also need +AD4- the LOCAL keword in there as well. +AD4- +AD4- HTH +AD4- +AD4- Steve +AD4- +AD4- +AD4- -- +AD4- To unsubscribe send e-mail to suse-linux-e-unsubscribe+AEA-suse.com +AD4- For additional commands send e-mail to suse-linux-e-help+AEA-suse.com +AD4- +AD4- Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/ +AD4- +AD4-
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/