Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Windows\s+client\s+behavior\s+change\s+at\s+4\.2\.1\.0\s*$/: 4 ]

Total 4 documents matching your query.

1. Windows client behavior change at 4.2.1.0 (score: 1)
Author: Jeff Connor <connorj AT NIAGARAMOHAWK DOT COM>
Date: Tue, 9 Oct 2001 11:08:16 -0400
Not sure how much of an issue this will be for some of you but I thought I'd pass along a change we came across in the Windows 4.2.1.0 client. If you are like us, and don't do a great job of excludin
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-10/msg00374.html (11,310 bytes)

2. Re: Windows client behavior change at 4.2.1.0 (score: 1)
Author: Patrick Boutilier <boutilpj AT STAFF.EDNET.NS DOT CA>
Date: Tue, 9 Oct 2001 12:41:00 -0300
The Linux 4.2.1 client now does this as well. Quoting Jeff Connor <connorj AT NIAGARAMOHAWK DOT COM>:
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-10/msg00376.html (11,920 bytes)

3. Re: Windows client behavior change at 4.2.1.0 (score: 1)
Author: Andrew Raibeck <storman AT US.IBM DOT COM>
Date: Tue, 9 Oct 2001 08:44:58 -0700
I am almost certain that this change in behavior is not deliberate. The APAR is going to be handled as a code defect, not a doc issue. Skipped files are not cause to fail an incremental backup. Regar
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-10/msg00378.html (12,225 bytes)

4. Re: Windows client behavior change at 4.2.1.0 (score: 1)
Author: Jeff Connor <connorj AT NIAGARAMOHAWK DOT COM>
Date: Tue, 9 Oct 2001 11:57:57 -0400
Thanks Andy. Can you find out if this is really a defect or working as designed? The PMR we opened for the problem is 15935,180. Here is an example from our dsmsched.log: Thanks Jeff 10/05/2001 02:07
/usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-10/msg00381.html (14,388 bytes)


This search system is powered by Namazu