User Tools

Site Tools


platform:how_do_i_run_gams_in_the_background_on_a_unix_machine

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
platform:how_do_i_run_gams_in_the_background_on_a_unix_machine [2007/02/02 16:48]
127.0.0.1 external edit
platform:how_do_i_run_gams_in_the_background_on_a_unix_machine [2012/06/12 17:39]
admin
Line 13: Line 13:
      gams -lo 0 trnsport &      gams -lo 0 trnsport &
  
-The log option flag tells GAMS not to write anything to the screen. +The log option flag tells GAMS not to write anything to the screen. ​You can also use ''​-lo 2''​ which writes the 
-An even better way is to use a small script called "​gamsbatch"​ that +log to ''​trnsport.log''​.
-reads:  +
- +
-     #​!/​bin/​csh -f +
-     set basename=$1:​r +
-     gams $* -ll 1 -lo 2 -lf $basename.log +
- +
-This will write what normally goes to the screen to a log file instead. +
-For example, if called as "​gamsbatch ​trnsport", transport.log will be +
-created. Many GAMS systems contain this script. If not, it can be +
-created and made executable by using "chmod +x gamsbatch"​+
  
 On some systems after you log out even background processes will On some systems after you log out even background processes will
 get killed. On those systems use:  get killed. On those systems use: 
  
-     ​nohup ​gamsbatch ​trnsport +     ​nohup ​gams -lo 2 trnsport ​&
- +
-Now it is safe to log off and go home.+
IMPRESSUM / LEGAL NOTICEPRIVACY POLICY platform/how_do_i_run_gams_in_the_background_on_a_unix_machine.txt · Last modified: 2012/06/12 17:39 by admin