How to keep a long-running process run with Kerberos and Andrew file system?

Question

I am running a bash script on a Scientific Linux server. The script has a loop for copying files and running some programs. The process for running the script probably takes a day or two. But I always can't finish running the script, because of the following error:

cp: cannot open `somefile' for reading: Permission denied

I suspect that the cause is due to Kerberos and/or Andrew file system on the server.

How can I make my long-running script run well to finish? Thanks.

If you insist on not talking to the right people, then that would certainly be better than here. — Michael Hampton, Jan 11 '16 at 01:01
related: https://unix.stackexchange.com/questions/724902/how-does-one-send-new-commands-to-run-to-an-already-running-nohup-process-or-run — Charlie Parker, Nov 14 '22 at 22:37

score 1 · Answer 1 · answered Jan 11 '16 at 02:23

1

You should use kstart (which is packaged in EPEL for Scientific Linux) to run your process. It will keep refreshing your Kerberos ticket, as well as run aklog if you use -t.

answered Jan 11 '16 at 02:23

jsbillings

24,406

do you know if your suggestions works for this: https://unix.stackexchange.com/questions/724902/how-does-one-send-new-commands-to-run-to-an-already-running-nohup-process-or-run ? – Charlie Parker Nov 14 '22 at 22:37

How to keep a long-running process run with Kerberos and Andrew file system?

1 Answers1