1. 04 Jun, 2018 1 commit
  2. 09 May, 2018 1 commit
  3. 25 Oct, 2017 1 commit
  4. 05 Sep, 2017 1 commit
  5. 03 Sep, 2017 1 commit
  6. 28 Jul, 2017 2 commits
  7. 27 Jul, 2017 1 commit
  8. 26 Jul, 2017 1 commit
  9. 18 Jul, 2017 1 commit
  10. 15 Jul, 2017 4 commits
  11. 23 Sep, 2016 1 commit
  12. 24 Aug, 2016 1 commit
  13. 25 Jul, 2016 1 commit
  14. 25 Jun, 2016 1 commit
  15. 21 Nov, 2015 1 commit
  16. 13 Nov, 2015 1 commit
  17. 09 Oct, 2015 1 commit
  18. 24 Sep, 2015 1 commit
  19. 04 Jun, 2014 2 commits
    • paulatto's avatar
      Small change on previous commit: apparently (i.e. according to documentation)... · 9982a6c0
      paulatto authored
      Small change on previous commit: apparently (i.e. according to documentation) LoadLeveler send a SIGXCPU after soft_wall is reached and SIGKILL when har_wall is reached. I've added trapping of SIGXCPU.
      
      Wall clock limit is specified as:
        wall_clock_limit = 5:00,4:30
      which would give pw 30 minutes to shut down
      
      
      
      
      
      git-svn-id: http://qeforge.qe-forge.org/svn/q-e/trunk/espresso@11025 c92efa57-630b-4861-b058-cf58834340f0
      9982a6c0
    • paulatto's avatar
      Added the possibility to intercept several signal and trigger a proper stop of... · 63e85afa
      paulatto authored
      Added the possibility to intercept several signal and trigger a proper stop of the code, as if the file prefix.EXIT was found.
      
      Currently intercepted signals are SIGINT (caused by CTRL-C), SIGTERM (by default sent by PBS one minute before wall time expires), SIGUSR1, SIGUSR2
      
      In order to compile this code add -D__TERMINATE_GRACEFULLY to MANUAL_DFLAGS in make.sys
      
      This code partially conflicts with __TRAP_SIGUSR1, although they can both be compiled ony the last signal handler set will work. However they do the same thing, so __TRAP_SIGUSR1 could eventually be removed as it is less general. 
      
      You can change the delay between the alert and the end of allocated wall time depending on the queue system. Here are some examples:
      
      * with PBS:
        send the signal 120 seconds before the end:
        #PBS -l signal=@120
      
        send signal SIGUSR1 10 minutes before the end:
        #PBS -l signal=SIGUSR1@600
      
        you cand also send a signal manually with qsig, or send a signal and then stop:
         qdel -W 120 jobid
        will send SIGTERM, wait 2 minutes than force stop.
      
      * with LodLeveler:
        According to documentation, a SIGUSR1 or a SIGTERM is sent, depending if the job will be restarted or not; SIGKILL follows after 2 minutes. There is no mention if this delay can be changed.
      
      
      
      git-svn-id: http://qeforge.qe-forge.org/svn/q-e/trunk/espresso@11024 c92efa57-630b-4861-b058-cf58834340f0
      63e85afa
  20. 09 May, 2014 1 commit
  21. 07 Nov, 2013 1 commit
  22. 05 Nov, 2013 1 commit
  23. 04 Nov, 2013 1 commit
  24. 10 Oct, 2013 2 commits
  25. 09 Apr, 2013 1 commit
  26. 07 Apr, 2013 1 commit
  27. 12 Mar, 2013 1 commit
  28. 11 Mar, 2013 1 commit
    • paulatto's avatar
      All c/fortran interfaces replace with iso_c_binding. · 0db771c5
      paulatto authored
      f_mkdir replaced with a more explicit f_mkdir_safe, f_mkdir is now a direct wrapper of the POSIX function.
      
      f_mkdir_safe now checks if a directory exists and is writable before creating it, it will only return error if at the end the directory is not writable
      Possible causes: file exists but is not a directory; exists and is a directory, but not owned by the user; broken filesystem; perverted umask
      
      check_tempdir does not change directly, but it benefits from the changes in f_mkdir_safe
      
      parallel_mkdir replaced with check_tempdir where it was necessary
      
      
      
      git-svn-id: http://qeforge.qe-forge.org/svn/q-e/trunk/espresso@10052 c92efa57-630b-4861-b058-cf58834340f0
      0db771c5
  29. 10 Mar, 2013 2 commits
  30. 02 Mar, 2013 1 commit
    • giannozz's avatar
      Some cleanup of tmp_dir creation. It may break a few things, in particular the · 6fd01597
      giannozz authored
      restart mechanism (it is already rather broken anyway). Notable changes:
      - variable "restart" is set to true if restart_mode='restart' on input,
        independently upon the value of other variables
      - the way tmp_dir and wfc_dir are created if not existent is simplified
      - f_mkdir returns -1 if directory exists, 0 if created, 1 if error
      - data-file.xml is no longer removed/renamed if restart_mode='from_scratch'. 
        I don't remember why it was done (although I remember there was a reason)
        and cannot see why it should be done. If restarting is dictated by input
        options, it shouldn't matter whether there is already a data-file.xml file
        on disk or not
      
      
      git-svn-id: http://qeforge.qe-forge.org/svn/q-e/trunk/espresso@10031 c92efa57-630b-4861-b058-cf58834340f0
      6fd01597
  31. 21 Feb, 2013 1 commit
  32. 24 Oct, 2012 1 commit
  33. 16 Oct, 2012 1 commit