1819803 Members
3010 Online
109607 Solutions
New Discussion юеВ

rpc.mountd

 
SOLVED
Go to solution
Edwin Ruiz_2
Super Advisor

rpc.mountd

Hi everybody!

Can i disable rpc.mountd daemon. I am applying some change on my HP9000 servers for security scans.
10 REPLIES 10
Chris Watkins_1
Respected Contributor
Solution

Re: rpc.mountd

First, edit /etc/rc.config.d/nfsconf to make START_MOUNTD=0 .

Then, do:
#/sbin/init.d/nfs.server stop
#/sbin/init.d/nfs.server start

Not without 2 backups and an Ignite image!
Jeff Schussele
Honored Contributor

Re: rpc.mountd

And if you're not doing *any* NFS at all then in the same file set
NFS_CLIENT=0
NFS_SERVER=0
as well, so they won't start up.
Also run /sbin/init.d/nfs.core stop
as well before you edit the config file.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Edwin Ruiz_2
Super Advisor

Re: rpc.mountd

Thanks! i can do that on line? my servers are on production.. That change will give some problem on future?
Chris Watkins_1
Respected Contributor

Re: rpc.mountd

As long as you remember it's off, the next time you need it.
Nothing like beating your head on the wall over something simple.

If you're not using NFS, and don't plan to... there's no issue.
Not without 2 backups and an Ignite image!
Chris Watkins_1
Respected Contributor

Re: rpc.mountd

0-point this please... I meant to say it last time.
Yes... if you're sure the service isn't in use, do it online.
No problems.
Not without 2 backups and an Ignite image!
Jeff Schussele
Honored Contributor

Re: rpc.mountd

Yes - you can change that on-line AS LONG AS YOU'RE NOT NOW CURRENTLY USING NFS.
If you are, well this is shutting it down & you can see the problem with that I'm sure.

One other thing - run those /sbin/init.d/nfs.???? stop commands *before* you edit the /etc/rc.config.d/nfsconf file or it'll squawk at you when you *do* try to stop them.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Edwin Ruiz_2
Super Advisor

Re: rpc.mountd

thanks for all
Chris Watkins_1
Respected Contributor

Re: rpc.mountd

It may squawk on the others... but not specifically for MOUNTD.
Tested it, on two machines... one actively serving NFS mounts
to a sandbox of ours. I did this live, and with no issues.
(And, yes the mounts are just fine, afterwards.)

Admittedly, I mount all nfs mounts "-o soft".
Can't swear what would happen if mounted hard,
but if mounted soft, editing the nfsconf, then performing
the server stop/start is certainly not a problem.

Now if Jeff is saying it "isn't supported", that's different.
We know how that goes. A lot of things work that aren't supported :)
Not without 2 backups and an Ignite image!
Jeff Schussele
Honored Contributor

Re: rpc.mountd

Hi Chris,

Most scripts in init.d will check the value - here's from nfs.server:

if [ "$NFS_SERVER" -ne 1 ];then
echo NFS_SERVER not set to one in /etc/rc.config.d/nfsconf, exiting.
exit 0
fi

nfs.client is the same. Then they won't stop & you'll have to re-edit the conf file & rerun & re-edit again.... Been burnt by this a couple times...

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Chris Watkins_1
Respected Contributor

Re: rpc.mountd

Ahhh... dead on, on that one. Good point Jeff!

I had just grepped out MOUNTD before testing...
and saw that that "particular" one wasn't an issue.

Edwin, just overlook and zero-point my extra bits here.
Just gaining knowledge, yaknow :-)


Not without 2 backups and an Ignite image!