Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>
Date: Fri, 14 Aug 2009 14:27:47 -0400
EMC has finally provided a work around to me that is working 100% of the time! Instead of using: nsrports -S 7937-7940 use: nsrports -S 7938-7941 Frank On 5/5/09 3:14 PM, Blackburn, Marvin wrote: We
Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>
Date: Sat, 15 Aug 2009 07:49:49 -0400
Sorry to keep responding to my own posts, but I've just discovered that what I pointed out yesterday is not completely correct. With the current releases of 7.5.1 -- use "nsrports -S 7938-7940", and
Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>
Date: Tue, 5 May 2009 14:23:26 -0400
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 c
Author: "Blackburn, Marvin" <mblackburn AT GLENRAVEN DOT COM>
Date: Tue, 5 May 2009 15:14:55 -0400
We are having the same issues. However, our systems seem to just stop responding after several days. We have done what EMC suggested with starting the ntp afterwards, but this hasn't fixed the proble
Author: Francis Swasey <Frank.Swasey AT UVM DOT EDU>
Date: Tue, 5 May 2009 15:31:53 -0400
Is your error only on reboots? No. If I get it running and then stop it and try to start it again, it's the same game all over again. What do you mean about starting ntp afterward? -- Frank Swasey |