Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Antwort\:\s+\"default\s+client\s+domain\"\s+changes\.\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Antwort\:\s+\"default\s+client\s+domain\"\s+changes\.\.\s*$/: 2 ]

Total 2 documents matching your query.

1. Antwort: "default client domain" changes.. (score: 1): Author: "Mecki M." <rmeschon AT OTELO.IBMMAIL DOT COM>; Date: Tue, 22 Jun 1999 08:37:09 +0200; Hi Tom, surely the domain option is to be used in schedules. the thing about the behavior especially with the incremental command is normal as described in "Installing the clients". The fs is to be a; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-06/msg00884.html (10,629 bytes)
2. Re: Antwort: "default client domain" changes.. (score: 1): Author: Tom Tann{s <tom.tannas AT USIT.UIO DOT NO>; Date: Tue, 22 Jun 1999 12:04:50 +0200; Well... My problem is that the scheduler has to be restarted after using the domain-option. In my opinion, the -domain-option should have effect only to the command using it, not on all commands in a; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/1999-06/msg00891.html (11,244 bytes)

Current List: 1 - 2
Page: [1]