Hot answers tagged cron
If you are using kerberos enabled NFSv4 ( and I would be highly surprised if you are ) then you need to create some kind of user keytab and use something like kstart at the beginning of the cron job to obtain a kerberos tgt. Otherwise, you should not need any kerberos credentials to access the NFS filesystem. This problem has been around forever in AFS ...
I had the same issue. After a lot of trial and error I found that my original line of /path/to/watch IN_CLOSE_WRITE /usr/local/bin/mycommand $@/$# does not work but the following does work: /path/to/watch IN_CLOSE_WRITE /bin/sh /usr/local/bin/mycommand $@/$# I guess incron doesn't honour scripts with a shebang (yet?) and needs an interpreter within the ...
If your workstations are not reliably powered on then anacron is the tool for the job as the manpage says ...it does not assume that the machine is running continuously. Hence, it can be used on machines that aren’t running 24 hours a day, to control regular jobs as daily, weekly, and monthly jobs. Further down it says how ...
It's not a general answer, but an answer to my problem. My use case was to allow jobs to start EC2 instances. Amazon provides functionality to allow jobs on specific instances to access AWS functionality without storing credentials on the instance itself: http://docs.aws.amazon.com/IAM/latest/UserGuide/role-usecase-ec2app.html
Of course any upload in the terrabyte range is going to take some time, how slow is your "slow" uplink? A 1 terrabyte upload over a 10Mbit uplink will take 1024*1024 = 1048576 seconds = 290 hours = 12 full days. I would take a look at Amazon's bulk upload by shipping a NAS appliance Take a look at http://aws.amazon.com/importexport/
Only top voted, non community-wiki answers of a minimum length are eligible