On Fri, Dec 11, 2015 at 7:57 PM, Josef wells <[email protected]> wrote: > > On Dec 11, 2015 19:33, "Josef wells" <[email protected]> wrote: >> >> >> On Dec 11, 2015 19:19, "Martin Møller Skarbiniks Pedersen" >> <[email protected]> wrote: >> > >> > On 12 December 2015 at 00:47, Josef wells <[email protected]> >> > wrote: >> >> >> >> That also says that this is for buffering output files, that is not >> >> what I'm seeing g in ~/.parallel >> >> >> >> Josef >> > >> > Please answer below and not top-post then it is easier to follow the >> > discussion. >> > >> > linelen-<hostname> is something with the maximum length of the >> > command-line on the remote-hosts. >> > These files should be small so it should be ok if they are located on a >> > network share. >> > >> > Are you using -X or -m ? >> > >> > Regards >> > Martin >> >> Not using -m/-X.. Called program doesn't support multiple args in that >> way. >> >> Using lsf to batch ~1000 jobs, each one, in is calling parallel to do git >> clones on that machines local disk. These machines are far/slow to my ~. >> >> Josef > > Maybe if I give: > --max-line-length-allowed foo > > It will not create/check these files. I'll give it a try. > > Josef
I should stop thinking about this tonight, since that option clearly doesn't do what I imagined only minutes ago. Any suggestions? I tried setting $HOME to something else, but it doesn't seem to propagate through the various shells I'm calling. Josef
