Re: Changingretries
1997-02-26 22:28:38
Subject: |
Re: Changingretries |
From: |
"Dwight E. Cook" <decook AT AMOCO DOT COM> |
Date: |
Wed, 26 Feb 1997 21:28:38 -0600 |
Item Subject: Changingretries
Well, I do see a command line listing for this parameter... it shows
(-ch=0) and where I haven't read it I've found if it can be specified
on the command line you can also specify it in the OVERRIDE CLIENT
OPTIONS (am I using the right name here?) field on a scheduled
event... if it is not a scheduled event I'd just let the client shoot
themselves in the foot AND alter your billing to be based on
COMMUNICATED MB from accounting records... cause it will move the data
to the server, then figure out that it changed, then retry...
And that last comment might be a little premature 'cause I don't know
if all that failed data really is reflected in communicated data
field. I sure hope so...
later
Dwight
______________________________ Reply Separator _________________________________
Subject: Changingretries
Author: ADSM-L at unix,sh/DD.RFC-822=ADSM-L AT VM.MARIST DOT EDU
Date: 2/26/97 12:18 PM
Is there a way to have the administrator override the changeretries that
are in the client option files? I see that the default is 4 and although I
doubt that most of the clients even put this in, most get 4 then. I don't
really want to update each clients file and would like this set to 1 or 2 but
not four. I can't seem to find how you set this for all nodes with an
administative command. Can I do this and if I can how or where can I
find this information. Thanks, jane
Jane Dagostino-Ssyder
University of Minnesota
|
|
|