Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*polling\s+vs\.\s+prompted\s+scheduling\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*polling\s+vs\.\s+prompted\s+scheduling\s*$/: 2 ]

Total 2 documents matching your query.

1. polling vs. prompted scheduling (score: 1): Author: "Matthew A. Bacchi" <mbacchi AT BTV.IBM DOT COM>; Date: Fri, 12 Jan 2001 09:28:56 -0500; I'm confused. I know what the two different scheduling methods are, but I don't think my server does. I have the server set to do client polling, but I still get error messages in the activity log th; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-01/msg00299.html (10,960 bytes)
2. Re: polling vs. prompted scheduling (score: 1): Author: David Longo <David.Longo AT HEALTH-FIRST DOT ORG>; Date: Fri, 12 Jan 2001 10:12:59 -0500; The most common reason for this message I have found has nothing to do with scheduling methods. It, in my experience, means either the client is down, *SM scheduler is not running on client, or there; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2001-01/msg00306.html (11,675 bytes)

Current List: 1 - 2
Page: [1]