Hello Gustav Schrenk
Your Discussion has gone 30 days without a reply. If you still need help with COMSOL and have an on-subscription license, please visit our Support Center for help.
If you do not hold an on-subscription license, you may find an answer in another Discussion or in the Knowledge Base.
Please login with a confirmed email address before reporting spam
Posted:
1 decade ago
12 mars 2012, 15:18 UTC−4
Depending on your operating system, you may be able to pause the program (less than ideally), but I need this as i run COMSOL on my laptop which uses the network research license at my school, if I leave and just let the computer keep running without the network connection, it eventually quits completely. There is a method in OSX using the kill -STOP #PID that can pause the program. i have tried it, shortly, and will be trying it this afternoon on my ride home for longer term. It goes like this:
-open 'Activity Monitor' , or use ps -axww | grep COMSOL and find the COMSOL instance with a lot of CPU time
-type 'kill -STOP #PID'
-where #PID is the Process ID listed in activity monitor or the first number listed on grep (they should match)
-the program should now instantly be stalled but still open, and probably unresponsive
- type "kill -CONT #PID' to start it up again
Hope this helps, or at least guides you a little. This would be an extremely useful feature (almost like pausing a virtual machine). Good luck.
Depending on your operating system, you may be able to pause the program (less than ideally), but I need this as i run COMSOL on my laptop which uses the network research license at my school, if I leave and just let the computer keep running without the network connection, it eventually quits completely. There is a method in OSX using the kill -STOP #PID that can pause the program. i have tried it, shortly, and will be trying it this afternoon on my ride home for longer term. It goes like this:
-open 'Activity Monitor' , or use ps -axww | grep COMSOL and find the COMSOL instance with a lot of CPU time
-type 'kill -STOP #PID'
-where #PID is the Process ID listed in activity monitor or the first number listed on grep (they should match)
-the program should now instantly be stalled but still open, and probably unresponsive
- type "kill -CONT #PID' to start it up again
Hope this helps, or at least guides you a little. This would be an extremely useful feature (almost like pausing a virtual machine). Good luck.