113 reputation
7
bio website jakenoble.me
location Derby, United Kingdom
age 29
visits member for 2 years, 5 months
seen Nov 24 at 16:42

I am Jake.

I am a Director at Yolk Creative

I work on bespoke web applications and web sites.

I use PHP, MySQL, jQuery, Knockout JS, Zend Framework, Symfony2, Concrete5 CMS.

I live in Derby, UK.

I am on Twitter

I am on LinkedIn


Oct
22
awarded  Popular Question
Oct
25
revised Find uptime of 'apache2'
added 727 characters in body; edited tags
Oct
25
comment Find uptime of 'apache2'
I do not have it installed, but good call +1
Oct
25
comment Find uptime of 'apache2'
Another version of this worked for me ps --no-headers -o etime -C apache2
Oct
25
accepted Find uptime of 'apache2'
Oct
25
awarded  Editor
Oct
25
revised Find uptime of 'apache2'
added 727 characters in body; edited tags
Oct
25
awarded  Commentator
Oct
25
comment Find uptime of 'apache2'
Yes MadHatter. Basically I want to know was it started just now (5 seconds) or some time ago. Its to check that the restart command actually ran.
Oct
25
asked Find uptime of 'apache2'
Oct
13
comment Monit and Varnish
that has worked perfectly. Now on to the overarching issue. Any ideas on why Varnish's init may not work for me?
Oct
13
accepted Monit and Varnish
Oct
13
asked Monit and Varnish
Mar
26
comment Why is my Rails application hanging?
This is a question. Not an answer.
Nov
22
accepted Effectively managing crontab
Nov
13
comment Effectively managing crontab
Never mind, fixed using serverfault.com/questions/316791/cant-get-cron-hourly-to-work
Nov
13
comment Effectively managing crontab
this still fails, or rather does nothing, I am using 38 * * * * run-parts /var/www/cron/cron.hourly then in /var/www/cron/cron.hourly I have a file called test which just does touch /var/www/cron.txt. Any ideas?
Nov
9
comment Effectively managing crontab
This seems to be a user that the cron is trying to run as, but my cron is run as www-data and not root. Changing root to www-data still fails with /bin/sh: www-data: not found
Nov
9
comment Effectively managing crontab
Hmmm, I have set it up and the only output I am getting via email is /bin/sh: root: not found
Nov
9
comment Effectively managing crontab
Thanks! Just for clarification, the folder /etc/cron.hourly already exists, does this mean I still need to add 01 * * * * root run-parts /etc/cron.hourly to my crontab? Or does it's existence mean that crontab is already aware of it and it'll be run anyway?