Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Netware\s+Memory\s+question\s+running\s+the\s+scheduler\s*$/: 4 ]

Total 4 documents matching your query.

1. Netware Memory question running the scheduler (score: 1)
Author: Mark Hayden <MHayden AT EPA.STATE.IL DOT US>
Date: Wed, 5 Mar 2003 14:26:47 -0600
I have been reading about a option called " managedservices " that you put in the dsm.opt file to help resolve memory problems that the TSM scheduler causes by not releasing the memory back to the Ne
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00184.html (11,121 bytes)

2. Re: Netware Memory question running the scheduler (score: 1)
Author: Jim Kirkman <jmk AT EMAIL.UNC DOT EDU>
Date: Wed, 5 Mar 2003 16:31:54 -0500
Do it! Run managedservices webclient schedule. I'd advise upgrading to the 5.1.5.6 client to avoid an potential problem with the client trying to grap an invalid port, I believe it was an nwipcport e
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00187.html (11,685 bytes)

3. Re: Netware Memory question running the scheduler (score: 1)
Author: Matt Zufelt <mzufelt AT SUU DOT EDU>
Date: Wed, 5 Mar 2003 14:56:29 -0700
I second Jim's advice. Especially on our servers with large number of files, using the managedservices option saves TONS of memory. We had one server that after a few weeks, DSMC.NLM was using nearly
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00284.html (12,023 bytes)

4. Re: Netware Memory question running the scheduler (score: 1)
Author: bbullock <bbullock AT MICRON DOT COM>
Date: Thu, 6 Mar 2003 11:29:32 -0700
Interesting, I had not heard of the "managedservices" option and thought it was only a netware thing. Surprise, it's on all client versions and looks like it's been around since V 4.2. Once again I l
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2003-03/msg00287.html (13,003 bytes)


This search system is powered by Namazu