rsnt_translations
56,430
edits
Frequently Asked Questions: Difference between revisions
Marked this version for translation
No edit summary |
(Marked this version for translation) |
||
| Line 146: | Line 146: | ||
For jobs which are already running, the start time reported by <tt>squeue</tt> is perfectly accurate. | For jobs which are already running, the start time reported by <tt>squeue</tt> is perfectly accurate. | ||
==What are the .core files that I find in my directory?== | ==What are the .core files that I find in my directory?== <!--T:52--> | ||
<!--T:53--> | |||
In some instances a program which crashes or otherwise exits abnormally will leave behind a binary file, called a core file, containing a snapshot of the program's state at the moment that it crashed, typically with the extension ".core". While such files can be useful for programmers who are debugging the software in question, they are normally of no interest for regular users beyond the indication that something went wrong with the execution of the software, something already indicated by the job's output normally. You can therefore delete these files if you wish and add the line <tt>ulimit -c 0</tt> to the end of your $HOME/.bashrc file to ensure that they are no longer created. | In some instances a program which crashes or otherwise exits abnormally will leave behind a binary file, called a core file, containing a snapshot of the program's state at the moment that it crashed, typically with the extension ".core". While such files can be useful for programmers who are debugging the software in question, they are normally of no interest for regular users beyond the indication that something went wrong with the execution of the software, something already indicated by the job's output normally. You can therefore delete these files if you wish and add the line <tt>ulimit -c 0</tt> to the end of your $HOME/.bashrc file to ensure that they are no longer created. | ||
</translate> | </translate> | ||