PMXBOT Log file Viewer

Help | Karma | Search:

#pypa-dev logs for Tuesday the 19th of July, 2016

(Back to #pypa-dev overview) (Back to channel listing) (Animate logs)
[13:39:42] <sigmavirus24> EWDurbin: I have a sys administration related question for you if you have the chance
[13:39:51] <EWDurbin> sigmavirus24: hit me
[13:41:05] <sigmavirus24> So, I'm securing the jenkins servers that I run for PyCQA. I realized that we weren't using tmpfs as /tmp and I made it read-only like I usually do but apparently, Python's multiprocessing uses /tmp for locking/synchronization. Have you run into something similar before?
[13:41:28] <sigmavirus24> (Flake8 uses multiprocessing, and I want to lint pushes/merge requests)
[13:43:44] <sigmavirus24> (Also to be clear, I don't remember why I tend to mount it as read only)
[13:45:29] <EWDurbin> sigmavirus24: it should respect the environment variables to move temp directory/files in Python
[13:45:52] <EWDurbin> TMPDIR, TEMP or TMP environment variables
[13:46:22] <EWDurbin> so you could create a temporary directory just for your jobs (even per job!) and set the environment variable when running your processes
[13:47:31] <EWDurbin> regarding read only temp, i can see some situations where that is a safe bet if processes don't create their temp files/dirs with sane permissions. or if the user/group story on the server is unclear/poorly managed
[13:47:46] <EWDurbin> like "give errrrbody root/sudo" or whatever
[13:49:43] <EWDurbin> so sigmavirus24 you have options if you'd like to maintain your read only /tmp. i actually _really_ like the idea of per job temp directories. you should write a jenkins plugin for dat
[13:51:27] <sigmavirus24> EWDurbin: I'd be surprised if that doesn't exist
[19:03:30] <wismer> dstufft: I believe I got the merge conflicts for those two remaining PR's resolved. There's another thing I could tag onto one of them that addresses https://github.com/pypa/warehouse/issues/1369, but I don't know if you prefer that to be a separate PR