The server should shutdown gracefully (cleanup and then exit 0) with
a SIGHUP (kill -1 <pid>). There's signal handling code in the server
that is supposed to catch SIGHUP at least, and begin shutdown. Can
you try kill -1 and see if that works for you?
-sam
On Feb 20, 2006, at 5:49 PM, Kyle Schochenmaier wrote:
Is there any way to stop the pvfs2-server without using the kill
signal?
I'd like to be able to do a profile of some of the execution so I
can work out some of the bottlenecks I'm having with the openIB-bmi
port, however, in order for this to work, I need to have a normal;
non-KILL signal termination for the process. I looked through some
of the code, and wasnt able to find anything, and it appears the /
etc/init.d/* scripts are just kill signals as well.
From the gprof documentation:
"In order to write the `gmon.out' file properly, your program must
exit normally: by returning from main or by calling exit. Calling
the low-level function _exit does not write the profile data, and
neither does abnormal termination due to an unhandled signal."
I'd like to do the profile on the server-side i/o, not the client-
side test programs...
Any ideas?
thanks,
- Kyle
--
Kyle Schochenmaier
[EMAIL PROTECTED]
Research Assistant, Dr. Brett Bode
AmesLab - US Dept.Energy
Scalable Computing Laboratory
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
_______________________________________________
Pvfs2-developers mailing list
[email protected]
http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
