Search Results

Yeah having read up on apache logging directives I see that there are much better ways of doing this but I wasn't the one who set the server up. Maybe one day I'll sort it all out...

Anyway, I've...

A client has asked us to set up a different domain (as an alias for their site) which they could use on certain marketing material and hence measure the campaign's effectiveness. We've set it up and...

I'm using vim version 6.1.18, which isn't that old and its the latest available using apt-get.

No, I didn't directly edit the crontab when I got it working, I just temporarily changed the EDITOR...

Cheers Ice, just missed your post before posting my last. Thanks for the reply, I've found a workaround now tho. Its not perfect but it gets the job done, any idea why vim doesn't want to play nice...

Ah ha!

My inkling that the problem may lie with vim seems to have some legs. Temporarily changing the $EDITOR environment variable to /usr/bin/nano and then doing the crontab edit did the job. No...

Thanks for your suggestions guys, sorry for the radio silence, been on holiday up in the mountains and hence arguing with crontab wasn't at the top of my to do list. Anyway back to it...

I've...

Good point larryase. I had had a look at the permissions on the crontab files but not the binary itself. Anyway this is what I got on /usr/bin/crontab:

# ls -l /usr/bin/crontab
-rwsr-xr-x 1...

Thanks for the response RTM.

I forgot to mention before that I had checked for both /etc/cron.allow and /etc/cron.deny, neither of which exist. The man page for crontab doesn't seem to think that...

I'm trying to create a new crontab entry for a user on a debian box but whenever I do a crontab -e or crontab -u username -e then edit the crontab (with vim as my default editor) and :wq. I get the...