- 1. log pruning problem (score: 1)
- Author: Cindy Cannam <CCannam AT GENAM DOT COM>
- Date: Wed, 15 Jul 1998 09:06:00 -0500
- To all: Just in the last two days, one of ADSM's 3.1.0.0 clients has placed the following message in the SCHED.LOG: 07/13/1998 00:54:56 ANS1483I Schedule log pruning started. 07/13/1998 00:54:57 ANS1
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-07/msg00536.html (10,851 bytes)
- 2. Re: log pruning problem (score: 1)
- Author: Doug Thorneycroft <dthorneycroft AT LACSD DOT ORG>
- Date: Wed, 15 Jul 1998 07:10:54 -0700
- We had this happen to one of our NT Clients. I deleted the dsmsched.log, and during the next backup, a fresh copy was created. The problem hasn't returned.
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-07/msg00537.html (11,367 bytes)
- 3. Re: log pruning problem (score: 1)
- Author: Cindy Cannam <CCannam AT GENAM DOT COM>
- Date: Wed, 15 Jul 1998 09:52:37 -0500
- Although I manually "pruned" the log down to just a few days worth of info yesterday (I only keep 10 days worth anyway, and QUIET is turned "on"), I didn't delete it. I'll give this a try -- maybe th
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-07/msg00538.html (11,959 bytes)
- 4. Re: log pruning problem (score: 1)
- Author: "Prather, Wanda" <PrathW1 AT CENTRAL.SSD.JHUAPL DOT EDU>
- Date: Wed, 15 Jul 1998 19:07:26 -0400
- Hi Cindy, I had the same problem several times. The way pruning works, is to copy the file up to the desired point, delete the old log, and rename the new. SO the usual problem is not enough space in
- /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1998-07/msg00567.html (12,815 bytes)
This search system is powered by
Namazu