Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

8
  • Are you using systemd 230 or more recent? Possibly related to bugs.debian.org/cgi-bin/bugreport.cgi?bug=825394 Commented Aug 5, 2016 at 14:07
  • @user4556274 Trying systemd-run --version tells me the server is using systemd 219. Commented Aug 5, 2016 at 14:11
  • @user4556274 In any case I can confirm that the problem is not that the processes are killed, in fact they do keep running, but that they behave differently. As I said I have a script that contains a simple while True: loop and that script runs fine, is not killed and I'm able to resume it without problems. I have also tried to add some subprocess and multiprocessing calls and they work fine. I'm at a loss of what is happening. Commented Aug 5, 2016 at 14:14
  • Does the python script reside on an AFS or NFS filesystem? Commented Aug 5, 2016 at 15:32
  • 1
    An explanation of what's going on is stackoverflow.com/questions/23571012/… . I don't have experience with AFS, but some pointers on how to extend access to the Kerberos tickets and AFS are given in that question's answers. Commented Aug 5, 2016 at 15:44