|
Re: [Networker] Getting NetWorker client to skip specified ports at startup
2008-12-17 08:21:06
Be aware, that future clients may require more ports, so you may get
yourself into a situation (as I have) of using nsrports to set the
number of service ports to just what is needed and then upgrading the
client to a new version and finding nsrexecd won't start because there
are not enough ports available.
Then you have to run nsrports to update things and then you can start
nsrexecd to see how many ports the new client needs.
Frank
On 12/17/08 7:14 AM, Kenneth Holter wrote:
Good. Thanks for the quick reply.
On 12/17/08, Davina Treiber <Davina.Treiber AT peevro.co DOT uk> wrote:
Kenneth Holter wrote:
I forgot to add "nrsports" to the list of available option. So if I
understand correctly, using "nsrports" need to be issued once per server,
and the change will be persistent between reboots? I prefer "nsrports"
over
the other options, so I'll go for this one if anyone confirms my
assumption
about persistence.
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
|
|
|
