Getting a Grep On Your Log: 101 Ways to Maximize Your Log Usage

You will need to have a firm grasp on tail and head as well as know the difference between less and more in order to truly master your log.

Caution should be used when using cat on your log as it could damage your log permanately (sharp claws and teeth, OUCH!)

--
In a mad world, only the mad are sane!

I have my own website and being a PERL programmer, I wrote my own photo gallery script for my website. I then setup an email address just for my gallery.. Then I wrote another script that is run every 10 minutes from a cron job that logs into the email account, downloads any messages, deletes them and then posts them into the gallery. I used my cell phone to take pictures and from it, I would send my pics to that email address and within 10 minutes, it would be posted in the gallery, with the text of the message being its description.

Now I set this up to be able to post any pics quickly and easily, however, it also works with standard email. You could just work offline and create a message for each picture and store them in your outbox. Then, when you do have access, you can send an entire batch at once. The coding is actually quite simple, and I would be willing provide you with my photo gallery script, I even wrote an auto installer for it. Just upload one file, set permissions and run it in your browser.

Hope you find your solution.

...I can tell you that there are many situations in which access to a client's data is required and unavoidable. We put a clause in our TOS that basically informs clients that because they are in a shared hosting environment (i.e. not the only web site on the server) we may need to access their data occasionally while researching and fixing a problem. This is because we can't control what the other clients are putting on their sites and sometimes vulnerable applications are being used by them. We monitor logs and processes for problems and if we notice any irregularities, we do a complete audit of every client to ensure that we eliminate the problem completely. Because of this, we recommend that all clients encrypt their data for extra security.

ANY shared hosting environment holds the same risks. You can't control what everyone is doing, all you can do is lock the server up as much as possible and keep a close eye on it to minimize the risks as much as possible. Let's face it, if you want more control, privacy and security, then owning your hardware is the way to go. That way you don't have to worry about some young, inexperienced developer from another web site opening up security holes because of bad code.