New answers tagged

0

Unfortunately, it's not emphasized enough that the environment processes started by cron get is very simple, it contains only the most vital variables and values. You can check it by running a shell script that contains only #!/bin/bash set > /tmp/myset.txt You will see that there is no DISPLAY variable set there that would be needed to run any ...


2

I doubt many folks have done this so far so I guess you will have to live with hints, not facts. In your shoes, I would go to single user mode (runlevel 1), create a clone node of /dev/null (mknod /dev/nihil c 1 3; chmod 666 /dev/nihil), delete /dev/null, create a fifo called /dev/null and write a script that reads that fifo and writes the log. Then switch ...


0

@jojo - Thanks for your comment. Here the proposed answer: Seems you used crontab instead of crontab -e. If option is omitted, default is crontab -r which is delete (check with crontab --help).


0

Not quite sure what you want to accomplish with screen in this scenario and why it is needed at all. But you are piping (with | .. > ) the output of screen to the dump file, not the output of the program which runs in screen. You either have to enclose the complete commando with quotes - or probably better put the commando in a script file and simpy call the ...


3

I use supervisord to do that. Cron's fine for starting it once, and keeping it running (use @reboot), but you need something a little less basic to keep an eye on things. My config files are per application (and in ubuntu something like /etc/supervisord/conf.d/foo.conf) This is my ttrss update script file but its a good starting point. command=php ...


0

Cron tab requires at least the first and last lines of the file not to be actual cron instructions. You can put comments instead - such as those below in a file: # START CRON JOB LIST * * * * * /path/to/script/script1.sh 0 3 * * 0 /path/to/script/script2.sh 5 0 * * 1 /path/to/script/script3.sh # END CRON JOB LIST Install it like so sudo crontab -u user ...


1

Where is it located? Cron tabs /etc/crontab /usr/lib/cron/tabs/* Source Mac OS X 10.9 - Artifacts Location


0

I had the same issue and solved just login directly with the user (in my case, using Putty). Before the first login, tried changing access.conf and didn't work. Just after add a password to the user and changed you shell to bash that solved my PAM configuration error, so I can finnally return the user to a non-shell and with su userInTrouble from root user ...


2

Those are different kinds of cron locations, although they are handled by the same daemon (cron). The configuration that you find under /etc/cron.d is system-wide and it's run with the user that you specify just before the command, which is nice. But what happens when a non-(root|administrator) user wants to set their own crons without root-user ...


2

Most likely the DNS server has recursive on and they are using your DNS server for this reason. I would make sure you disallow recursive DNS.



Top 50 recent answers are included