I use a DOS command line http client tool called httpcmd and it works excellent with the task scheduler in 2000. It'll popup a DOS window when it does its work but shuts it down when its done. I started using it when the WiTango cron process would fail randomly.
I think it comes in the Windows Servers resource kits. You can find it on the web as well. If you need this tool, email me off list. -Erik > I use the task scheduler method and I am doing exactly as you stated in > your post here. I tried and tried to get the cron to run and finally > just had to find another way. My cron ran fine when we were serving on > Win NT boxes, but, when we moved to 2000, for some reason the cron > wouldn't' kick off like it use to. > > The task scheduler method isn't the best, but, it opens a browser with a > home page that I told it to go to. Off that home page I have a taf that > runs. The problem though, was when I needed other tafs to run and of > course I only have one browser, so, I did the next best thing and just > put branch's to the other taf's. I admin, a very unconventional way of > going about things, but, it does what my cron use to do. > > I do wish there was another way. > > Steve Campbell > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 03, 2002 11:55 PM > To: Multiple recipients of list witango-talk > Subject: Witango-Talk: cron help or task scheduler > > I have been banging my head against the old crontab > issue. One reason I'm looking at crontab again is > because the way our NT Admin has set up task scheduler > causes a browser window to open on the server when it > runs my taf files. So if there is way to use the Task > Scheduler to run a taf with out opening a browser > window, great! > > In the meantime, here is the output from my tango.log > 03/10/2002 21:28:46 0 > [Cron] Sent http://localhost:80/cronmail.taf > > and here is my textcron.txt > > # Run this application file all the time (every minute) > * * * * * http://localhost/cronmail.taf > > My test is a simple taf that just sends an email. It is > triggering the cron file every minute, but the taf is > not getting executed. Do I need the t4cgi.exe? > > I tried that: http://localhost/scripts/t4cgi.ext but > IIS can't find scripts directory because it is not in > the web root. I moved it to the web root. No luck. > The manual was not clear on the cgi piece either. > > I have tried every combination of ip/localhost/127.0.0.1 > and the taf fails to execute. The server parses the > crontab file on startup: > [2752] Parsed 1 entries in crontab > C:\Inetpub\scripts\testcron.txt > > I have looked through all the past posts, and I seem to > be doing everything correctly. I have tried with a > blank line at the end of the txt file, and no blank line > with a carraige return at the end of the cron task. > > Any advice would be most appreciated. > > John Newsom >> If you have two WiTango server processes running on the same machine > how do >> you purge all of them in one go? >> >> Also, how do you monitor server status at a per-process level in a >> multi-process environment? >> >> - James. >> >> >> >> > ________________________________________________________________________ >> TO UNSUBSCRIBE: send a plain text/US ASCII email to > [EMAIL PROTECTED] >> with unsubscribe witango-talk in the message body > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > ________________________________________________________________________ > TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > -- +_____ |__ ___ ___ _____ _____ ____ _ _ | ___ __ ___+ | |___|| | | | |__| \ / | |___||__| |___ | | ||___ | |___| | \ | |____ | ||___| ___| + "A multi-disciplinary creative collective based in Denver, Colorado" Erik Kulvinskas www.factorylabs.com ph: 303.573.9100 fx: 303.573.5975 ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
