Sure NOW it's a known problem.
Has Microsoft secretly infiltrated IBM?

C

________________________
Cris Robinson
Senior Technical Analyst
Desktop Services Technical Support
Liberty Mutual Insurance
603.431.8400.54837
cris.robinson AT libertymutual DOT com

> -----Original Message-----
> From: Pete Tanenhaus [SMTP:tanenhau AT US.IBM DOT COM]
> Sent: Wednesday, August 19, 1998 10:21 AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Win32 client bug!!
>
> It's a known problem. Please turn off schedule log pruning for now
> until we can
> get it fixed.
>
> Pete Tanenhaus, ADSM NT Client Development
> ---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on
> 08/19/98
> 10:08 AM ---------------------------
>
>
> ADSM-L AT VM.MARIST DOT EDU on 08/19/98 03:30:03 AM
> Please respond to ADSM-L AT VM.MARIST DOT EDU
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: Win32 client bug!!
>
>
> Dear ADSM-ers!
> This is a warning for all Windows 32 client 3.1.05 users!
> If you use the dsmsched.log pruning option this can cause your
> filespace to
> fill up completely.
> Yesterday I installed the 3.1.05 client on 3 Windows NT machines.
> After the
> backup the ADSM scheduler starts pruning the dsmsched.log which never
> finishes. It created a dsmprun.log which took up all the available
> free disk
> space!
> This sounds like a serious bug in the ADSM client code.
> Kindest regards,
> Eric van Loon
>
>
>