I've run LDM without portmapper/rpcbind given they are both ginormous
security risks. It delays the startup/shutdown and other admin functions
since LDM tries to RPC but fails, then it tries again, etc...until it
figures out it is never going to work and defaults to 388 and everything
works fine afterwards.
Personally, I'd rather see it assume 388 and fall back to
portmapper/rpcbind in the event of 388 failure, but that's just me :)
I ended up turning portmapper/rpcbind back on because I was getting
annoyed at the startup/shutdown delays. Now I just have 18 more things to
worry about because of it.
-Tyler
> 111 is the portmapper/rpcbind port. Since LDM runs by means of RPC, I
> don't think it's possible to turn off RPC, though the authors of LDM may
> know better.
>
> Bret Whissel
> System Administrator
> Department of Meteorology
> Florida State University
>
> On Mon, 2009-09-28 at 14:59 -0500, Peter Laws wrote:
>
>> Peter Laws wrote:
>> > Having, for better or worse, moved well past the world of NIS and RPC
>> (and
>> > CSH :-), I want to disable RPC on our LDM servers. Port 388 seems to
>> work
>> > well enough.
>> >
>> > Is it as simple as reregistering the program? Should I be setting
>> > something in a config file somewhere?
>>
>> And a related question ... what would cause LDM to make a request via
>> 111/tcp versus 388/tcp? Can that be controlled in the config?
>>
>>
> _______________________________________________
> ldm-users mailing list
> ldm-users@xxxxxxxxxxxxxxxx
> For list information or to unsubscribe, visit:
> http://www.unidata.ucar.edu/mailing_lists/
