Automatically adding a timestamp to CORE filenames
Completed
We have noticed that in the current version of NX 5.1.3.38363, the CORE file contains a timestamp in its name. Won't this fill up the disk if there are more errors? Previously, the older CORE file was overwritten with the newer one.
-
I assume Piotr was talking about the core.xxxxxx on the Linux version of mediaserver. The core file is named as core.{epoch_timestamp} sits at "/opt/networkoptix/mediaserver/"
What Piotr asks might be :
1) The file size is relatively large, so he is worried about the disk capacity will be occupied and eaten up.
2) Will it be possible to just overwrite the old core file instead of create new core file. -
That's my take on it too Ichiro I can see this becoming an issue for us to if this is the new default, we currently reserve enough space for one core dump. If there are going to be multiple then it might be worth making the default behavior to overwrite the core and then in situations (which certainly do exist when troubleshooting) being able to enable the new behaviour which allows you to collect core dumps. It seems counter productive to be writing a script to put into cron to clean up core files by default.
Post is closed for comments.
Comments
3 comments