[Networker] NetWorker 7.5.x and tight nsrports settings
2009-05-05 14:28:40
I am finding that nsrexecd does not reliably start on systems where I have used nsrports to
restrict the client to just having the four (4) ports it requires. I am seeing this
specifically on linux clients. I have measured an average failure to start of 65%. This is
with both 7.5 and 7.5sp1.
Since the EMC droid I'm working with is unable to find a machine to test on (give me a break!)
-- can anyone else that has restricted the client to using just four ports comment on whether
or not they are seeing the same problem?
Thanks,
--
Frank Swasey | http://www.uvm.edu/~fcs
Sr Systems Administrator | Always remember: You are UNIQUE,
University of Vermont | just like everyone else.
"I am not young enough to know everything." - Oscar Wilde (1854-1900)
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
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Networker] NetWorker 7.5.x and tight nsrports settings,
Francis Swasey <=
|
|
|