SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
01-12-2008, 05:31 AM
| ||||
| ||||
 Re: limiting daemons to specific interfaces In article <Pine.SOL.4.44.0309142327340.18240-100000@tomato.shitty.org>, smuellerBUT@ANOSPAMDOMAINt3l.net wrote: > So most software is capable of only binding to a specific interface or > address that would normally be specified in a configuration file right?? > > How does one do this with nfsd, mountd, statd and lockd? > I've looked at the man pages and while nfsd -t may seem like the way to > go, I can't figure out how they want the device specified in > /etc/netconfig. > > I've attempted to specify the device as the system hostname (which should > at least bind it to the ipaddress of said hostname). > > Anyone else had much success with this? > Remove the obvious to reply via e-mail. You've got it backwards. nfsd, mountd, statd, and lockd are general services. They don't bind to specific IP addresses but offer their services to the network. A remote or local client must bind to those services through an IP address. This is where you change things--on the remote host--not on the server itself. Traffic will come into the system from one or more IP addresses or NICs. More accurately, a process will bind to an IP address and port number. The IP address is associated with an interface. -- DeeDee, don't press that button! DeeDee! NO! Dee...      |
 |
« Re: Optimising performance of Perl binary on Solaris
|
Re: limiting daemons to specific interfaces »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 05:15 AM.
