|
|
|
| |||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
|
|
Get inside! Sample the range of functionality easily built with JMSL Library for Time Series Data Analysis, Heat Maps, Portfolio Optimization, Monte Carlo Simulation, Stock Price Charting and more. Download Now! |
|
#1
|
|||
|
|||
|
Name of core dump file
How can I change default name of core dump file "core", before it will be created ? ( on HP-UX )
Thanks. Vilo |
|
#2
|
|||
|
|||
|
I don't think you can do that with HP-UX.
|
|
#3
|
|||
|
|||
|
no way, core is hard coded.
why do you want change it? |
|
#4
|
|||
|
|||
|
Name of Core dump file
Quote:
We have all executables in one directory. During development of our system 2 different processes sometimes crashed down. When it happens during night or weekend - first core is overwritten by second (of another process) - we loose 1. core for analyse. On True64 UNIX there is a System Parameter for core name f.e. Procesname of exec and something. It means we will have to start second process from another directory. |
|
#5
|
|||
|
|||
|
Recent versions of SunOS also has a way to address this. But not HP-UX.
A cron job could run every five minutes to look for cores and rename them. If both process crash too close together that won't help. Starting each process in a separate directory will work. A core is generated as the default action of one of several signals. If you have the source for the processes, they can catch all of these signals, chdir to another directory, remove the signal handler, and signal themselves with the original signal. If the process is dying due to stack overflow, there will be no stack left to run the signal handler. You can use sigstack() to provide an alternate stack to avoid that problem. I don't know of any other solutions for HP-UX. |
|
#6
|
|||
|
|||
|
i propose, as long you are devlopping and testing:
core are generate in the `pwd` dir of the user starting the proc, so create different user with own home-dirs check permissions and start your progrs using an absolute path sure you need a script to set env vars never do that in production env.: if your progs need a dedicated user (this could be a probl) chmod them setuid (that user) on exec. NOTA: i am quite sure, accurate setting of usr-id && grp-id && PATH will also do the job. |
![]() |
| Viewing: Dev Shed Forums > Operating Systems > UNIX Help > Name of core dump file |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|