Re: [Networker] Getting NetWorker client to skip specified ports at startup
2008-12-09 00:27:30
use the nsrports command.
something like "nsrports -S 7937-7940" (depending on whether the client is
also a storage node or other functions you may need more ports). That
command needs to be run on the client in question and you need to stop and
start NetWorker on the client for it to take effect
Brendan
On Mon, Dec 8, 2008 at 7:31 PM, Kenneth Holter <kenneho.ndu AT gmail DOT
com>wrote:
> Hi.
>
>
> One of our applications depends on binding to port 9050 at startup. Last
> weekend the application did not come up after a reboot, as the NetWorker
> client had come first to using this particular port. Is there some way of
> getting NetWorker client to _not_ use this port (and maybe other specified
> ports) so that the affected applications do not crash/fail?
>
> Regards,
> Kenneth Holter
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
|
|