#5
|
||||
|
||||
Quote:
Quote:
This computer is using a dual-boot but it's x86, but that might still cause problems considering I set the script to run at 4:00 and it seems to be running 6 times a day. Quote:
Quote:
Code:
jared@192.168.2.2:~$ cronjob -e cronjob: command not found I added this script to my crontab a while ago. STOP THE PRESSES. I found the problem. When I made the crontab I was an dumbass and sudo su'd before I did it. FUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUUU UUUUUUUUUUUUUUUUUUUUUU EDIT: Oh yeah. I did that because the command required a sudo. But I can just do it in my regular account and it'll still work right? Also I'm assuming tjhe # sign means the lines are commented in crontab -e, right? Last edited by Jaredvcxz; May 22, 2011 at 04:04:09 AM. |
#6
|
||||
|
||||
As long as you don't go merging your Sudo and handwrite code in the wrong lines. Or merge them at all. End your current command before starting up a new command line, or you could end up stackbooting your OS' every ten minutes [Like I've done on more than one occasion.... >_>]...
Curiously, have you tried isolating Xubuntu on a separate drive or USB and experimenting with your code? That's partially responsible for how I learned how to queue and command. o.o |
#7
|
|||
|
|||
Techno you're terrible at keeping track of other people's computers.
Server: Ubuntu with Vista primary Main: Ubuntu with Win7 primary **** computer that's 5+ years old: Windows 3.11 that I tried using Xubuntu on but GRUB is a dick. |
|