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 learn something new from the listserv....
I have a few hosts with very large filesystems where the schedule daemon is
not releasing memory. I think I may try this option out.
Just as a question to the group: Is there a reason you would not want to use
this on all the clients? (just have it restart the scheduler at the time of the backup)
Thanks,
Ben
-----Original Message-----
From: Matt Zufelt [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 2:56 PM
To: [EMAIL PROTECTED]
Subject: Re: Netware Memory question running the scheduler
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 3/4 of a gig of RAM. Using managedservices and
dsmcad.nlm solved the problem.
Matt Zufelt
Southern Utah University
>>> [EMAIL PROTECTED] 03/05/03 02:31PM >>>
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 error.
Other than that it's been good, helped with the memory release issue a lot.
Mark Hayden wrote:
> 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 NetWare
> Server....We have had ongoing problems with this forever. I would just
> like to know if anyone is using this option on any NetWare clients????
> Thanks
>
> I would like to try this with the option" managedservices schedule" to
> see if this helps.... What do you think?
>
> Thanks, Mark Hayden
> Informations Systems Analyst
> E-Mail: [EMAIL PROTECTED]
--
Jim Kirkman
AIS - Systems
UNC-Chapel Hill
966-5884
