In Linux, on an extremely long running vim session, calls to system() fail with E484 “can't open file /tmp/”

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
6
down vote

favorite
1












I've noticed this only on long running vims in my Linux server. I've narrowed down the E484s to lines of my vimscript that call system.



I just wonder if there is a way to deal with this because so far i have just been closing and restarting vim if this happens. But since the problem is so specific, it would be nice if it could be addressed so i can continue to use the running instance.



It's tricky to test and iterate on this because it takes at least 3 weeks before a vim instance gets into this state.




linux error




share|improve this question
























    up vote
    6
    down vote

    favorite
    1












    I've noticed this only on long running vims in my Linux server. I've narrowed down the E484s to lines of my vimscript that call system.



    I just wonder if there is a way to deal with this because so far i have just been closing and restarting vim if this happens. But since the problem is so specific, it would be nice if it could be addressed so i can continue to use the running instance.



    It's tricky to test and iterate on this because it takes at least 3 weeks before a vim instance gets into this state.




    linux error




    share|improve this question






















      up vote
      6
      down vote

      favorite
      1









      up vote
      6
      down vote

      favorite
      1






      1





      I've noticed this only on long running vims in my Linux server. I've narrowed down the E484s to lines of my vimscript that call system.



      I just wonder if there is a way to deal with this because so far i have just been closing and restarting vim if this happens. But since the problem is so specific, it would be nice if it could be addressed so i can continue to use the running instance.



      It's tricky to test and iterate on this because it takes at least 3 weeks before a vim instance gets into this state.




      linux error




      share|improve this question












      I've noticed this only on long running vims in my Linux server. I've narrowed down the E484s to lines of my vimscript that call system.



      I just wonder if there is a way to deal with this because so far i have just been closing and restarting vim if this happens. But since the problem is so specific, it would be nice if it could be addressed so i can continue to use the running instance.



      It's tricky to test and iterate on this because it takes at least 3 weeks before a vim instance gets into this state.





      linux error





      share|improve this question











      share|improve this question




      share|improve this question










      asked Aug 6 at 15:05









      Steven Lu

      962315




      962315




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          8
          down vote



          accepted










          This happens when some system cron job cleans out "unused" files from /tmp. The solutions are:



          1. Find that cron job and stop it from rm'ing your Vim /tmp files.


          2. Recreate Vim's temporary directory.


          Given the temporary directory name from the error message, you can recreate the directory manually with "!mkdir <dirname>", or you can use this command which you can put in your ~/.vimrc:



          command! Mktmpdir call mkdir(fnamemodify(tempname(),":p:h"),"",0700)


          That command was contributed to the vim_use list by Ben Schmidt.






          share|improve this answer






















          • This is wonderful, exactly the kind of manual workaround i need, thanks!
            – Steven Lu
            Aug 6 at 18:29










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "599"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );








           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fvi.stackexchange.com%2fquestions%2f17019%2fin-linux-on-an-extremely-long-running-vim-session-calls-to-system-fail-with%23new-answer', 'question_page');

          );

          Post as a guest

















          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          8
          down vote



          accepted










          This happens when some system cron job cleans out "unused" files from /tmp. The solutions are:



          1. Find that cron job and stop it from rm'ing your Vim /tmp files.


          2. Recreate Vim's temporary directory.


          Given the temporary directory name from the error message, you can recreate the directory manually with "!mkdir <dirname>", or you can use this command which you can put in your ~/.vimrc:



          command! Mktmpdir call mkdir(fnamemodify(tempname(),":p:h"),"",0700)


          That command was contributed to the vim_use list by Ben Schmidt.






          share|improve this answer






















          • This is wonderful, exactly the kind of manual workaround i need, thanks!
            – Steven Lu
            Aug 6 at 18:29














          up vote
          8
          down vote



          accepted










          This happens when some system cron job cleans out "unused" files from /tmp. The solutions are:



          1. Find that cron job and stop it from rm'ing your Vim /tmp files.


          2. Recreate Vim's temporary directory.


          Given the temporary directory name from the error message, you can recreate the directory manually with "!mkdir <dirname>", or you can use this command which you can put in your ~/.vimrc:



          command! Mktmpdir call mkdir(fnamemodify(tempname(),":p:h"),"",0700)


          That command was contributed to the vim_use list by Ben Schmidt.






          share|improve this answer






















          • This is wonderful, exactly the kind of manual workaround i need, thanks!
            – Steven Lu
            Aug 6 at 18:29












          up vote
          8
          down vote



          accepted







          up vote
          8
          down vote



          accepted






          This happens when some system cron job cleans out "unused" files from /tmp. The solutions are:



          1. Find that cron job and stop it from rm'ing your Vim /tmp files.


          2. Recreate Vim's temporary directory.


          Given the temporary directory name from the error message, you can recreate the directory manually with "!mkdir <dirname>", or you can use this command which you can put in your ~/.vimrc:



          command! Mktmpdir call mkdir(fnamemodify(tempname(),":p:h"),"",0700)


          That command was contributed to the vim_use list by Ben Schmidt.






          share|improve this answer














          This happens when some system cron job cleans out "unused" files from /tmp. The solutions are:



          1. Find that cron job and stop it from rm'ing your Vim /tmp files.


          2. Recreate Vim's temporary directory.


          Given the temporary directory name from the error message, you can recreate the directory manually with "!mkdir <dirname>", or you can use this command which you can put in your ~/.vimrc:



          command! Mktmpdir call mkdir(fnamemodify(tempname(),":p:h"),"",0700)


          That command was contributed to the vim_use list by Ben Schmidt.







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Aug 6 at 21:00

























          answered Aug 6 at 16:42









          garyjohn

          4,639913




          4,639913











          • This is wonderful, exactly the kind of manual workaround i need, thanks!
            – Steven Lu
            Aug 6 at 18:29
















          • This is wonderful, exactly the kind of manual workaround i need, thanks!
            – Steven Lu
            Aug 6 at 18:29















          This is wonderful, exactly the kind of manual workaround i need, thanks!
          – Steven Lu
          Aug 6 at 18:29




          This is wonderful, exactly the kind of manual workaround i need, thanks!
          – Steven Lu
          Aug 6 at 18:29












           

          draft saved


          draft discarded


























           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fvi.stackexchange.com%2fquestions%2f17019%2fin-linux-on-an-extremely-long-running-vim-session-calls-to-system-fail-with%23new-answer', 'question_page');

          );

          Post as a guest
































































          Comments

          Post a Comment

          Popular posts from this blog

          White Anglo-Saxon Protestant

          Image
          White Anglo-Saxon Protestants ( WASPs ) are a social group of wealthy and well-connected white Americans, of Protestant and predominantly British ancestry, who trace their ancestry to the American colonial period. Until at least the 1960s, this group has dominated American society and culture and dominated in the leadership of the Whig and Republican parties. They usually are very well placed in major financial, business, legal and academic institutions and had close to a monopoly of elite society due to intermarriage and nepotism. [1] During the latter half of the twentieth century, outsider ethnic and racial groups grew in influence and WASP dominance weakened. Americans are increasingly criticizing the WASP hegemony and disparaging WASPs as the epitome of "the Establishment". The Random House Unabridged Dictionary (1998) says the term is "Sometimes Disparaging and Offensive". [2] [3] The term WASP is often used as a pejorative to classify their historical dom...
          Read more

          Is the Concept of Multiple Fantasy Races Scientifically Flawed? [closed]

          Image
          Clash Royale CLAN TAG #URR8PPP up vote 2 down vote favorite Many fantasy worlds have multiple humanoid species (elves, orcs, humans, etc) living in the same world, in addition to that, they often have the ability to interbreed. And I can't help but question their believability... fantasy-races reproduction interspecies-relations share | improve this question edited Aug 9 at 14:46 Michael Kjörling ♦ 21.1k 10 85 161 asked Aug 9 at 13:13 Chlodio 118 6 closed as unclear what you're asking by MichaelK, Gryphon, John, Vincent, Frostfyre Aug 9 at 15:25 Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question. ...
          Read more

          One-line joke

          A one-liner is a joke that is delivered in a single line. A good one-liner is said to be pithy - concise and meaningful. [1] Comedians and actors use this comedic method as part of their act, e.g. Jimmy Carr, Tommy Cooper, Rodney Dangerfield, Norm Macdonald, Ken Dodd, Stewart Francis, Zach Galifianakis, Mitch Hedberg, Anthony Jeselnik, Milton Jones, Shappi Khorsandi, Jay London, Mark Linn-Baker, Demetri Martin, Groucho Marx, Dan Mintz, Emo Philips, Tim Vine, Steven Wright and Henny Youngman and Arnold Schwarzenegger. [ citation needed ] Many fictional characters are also known to deliver one-liners, including James Bond, who usually includes pithy and laconic quips after disposing of a villain. [ citation needed ] Examples "A baby seal walks into a club." "A dyslexic man walks into a bra." (Anonymous) "There are three types of people, those who can count and those who can't." "Venison's dear, isn't it?" (Jimmy Carr) "An escala...
          Read more