<sigh> I've just had my first really bad experience with OpenSRS support. A fellow who yelled over my questions, and eventually answered "I don't know" to things which I kind of think he should have been able to find out easily. Perhaps he's just having a bad day. :-( Or perhaps I've just become too accustomed to the excellent support I've previously received from OpenSRS.
The question, which this support guy (after some threatening sounding "I know who you are" lines) agreed that discuss-list might be able to answer better than himself, was with regard to access limits on batch.opensrs.net. My understanding from (long-ago) discussions on the matter here was that using rr-n1-tor for batch access would warrant account suspension or public hanging or something, but batch.opensrs.net was available for what e're I'd like to do, since the same availability guarantees were not in place on that host. A cron job should be run on batch, leaving rr-n1-tor for human use. Now I'm told that running an action=process-pending once per minute for the week-end will probably get my account shut off. And (here's the part that really bugs me) OpenSRS tech support is unable to tell me what sort of access limits exist on batch.opensrs.net. The only ways to find out what access limits exist are apparently to check my contract (which predates the existence of batch.opensrs.net, though I also see no mention of this matter in the contracts currently at resellers.tucows.com) or to contact my sales rep, who of course isn't available for escalation until Monday. What's the deal here? Will a once-per-minute cron job running a GET on batch.opensrs.net get my service terminated without notice? How about once every two minutes? Five? Where's the documentation that says so? And why can't a tech support guy answer a question like "what's the default access limit on the restriction you just told me about?" Or was the support guy still suffering from new year's eve? -- Paul Chvostek <[EMAIL PROTECTED]> it.canada http://www.it.ca/
