It works well if I call the script from my computer directly.

But if I call the script using
"<!--#exec cgi="/cgi-bin/xpress.pl" -->" from a web site located in another directory the same server the script can NOT Get Cookies, but only Set Cookies every time I reload this site.

What's wrong.
What is the solution.
I am trying to call the script from a "Form" page.

But your answer was just what I was looking for - Thanks!

[This message has been edited by jnestor (edited 02-09-2000).]

Beyond that, they are masters of spam, sending it to me over and over again at various addresses across all my virtual hosts with the promise that it is a one-time offer to help monitor my host. I am so tired of their bullsh*t, I blocked them from emailing any of my virtuals.

Rackshack has a free monitor included with all their hosting packages ... a central machine that polls each one and emails an address if a machine doesn't respond. I'd look for something similar from your web hosting company or colo facility.

Or, you could do it in reverse ... write something from your own server that emails you periodically, and you'll know you're having trouble if it doesn't get through.

In most cases, email will not be the service which tanks, so software that emails you if your *services* go down can be run more or less effectively from your box.

In any case, I also do receive the InternetSeer spam, though I think they are triggering one of my Outlook rules, and are receiving a nice form letter everytime they send me an email.

To add to what loy said, if you also keep track of things like disk usage, processor usage, and memory usage, and have the script send you an email if it's at dangerous levels, it can also be a good precautionary step.

I can go into a site administration panel and view these things... but what I find is that it tells me that the amount of space used and bandwidth used is way below what is allotted.

However, occassionally the server goes kaput. And it is definitely the server - they have to "reset it" whatever that means. If someone isn't monitoring this thing 24/7, we can lose hundreds of sales in a few hours.

I might try that reverse email thing in combination with internetseer.

quote:

---

I wouldn't be too harsh on InternetSeer - Network connections do go down every now and then, and even if your server is physically up, if the section of internet that has InternetSeer servers go down, then for the people there, it's pretty much the same as your server going down.

---

Agreed ... but two things really pissed me off. This all started when they sent me a notice that my server was down at a time when I was actively using the site myself ... so I went back and checked. Out of all the saved 'down' reports they had sent me, only one corresponded with the actual server logs once I was able to get my hands on them. That's a pretty crappy performance record; for a host that offers a service checking reliability, it sounds like they need a more reliable connection themselves.

The second thing is that, like jkcity, I was signed up without my permission. I also kept it for a while. When I discovered it wasn't accurate, I could NOT get off the list. I used their web form to unsubscribe. I replied to the email in the correct formats to unsubscribe. Finally, in frustration, I emailed abuse, root and postmaster on their domain and told them to knock it off or they were getting blocked. Blocking a domain from sending email altogether is a serious thing and I don't take it lightly. They didn't exactly leave me a lot of choice.

So, yes, they could have their own other connectivity problems, but that's no excuse to keep shoving a poor service down my throat.

"Rackshack has a free monitor included with all their hosting packages ... a central machine that polls each one and emails an address if a machine doesn't respond. I'd look for something similar from your web hosting company or colo facility."

I think the idea is to have a third disinterested party monitoring the connectivity of the hosting company and or web site hosted by the company.

I would look to an outside solution first.

If the box monitoring your server is within the host network, or administered by your host I would tend to question the results obtained.