Archived

This topic is now archived and is closed to further replies.

raise() and signal()

This topic is 5132 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

ok, I''ve set up some custum signal handlers for SIGINT and SIGSEGV in my program(mud server actually) band i''ve been playing around some with them, now there are 32 defined signals and it accepts signals up to 64. so does that mean that they planned ahead or that you can implement your own custom signals? perhaps a bad idea to mess with the signals if you want to be compatible with the future anyone know if this is a good or bad idea? - Damage Inc.

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Use them at your own risk.

and why would you need anything other than 2 user defined signals, anyway?

sounds like you''re trying to use signals to do something something else is better suited for.

Share this post


Link to post
Share on other sites
SIGUSR1 and SIGUSR2 are defined for a reason. If you have to use signals to communicate between processes, use those two. If you need more than two, then you should probably be using a different IPC method anyway.

Share this post


Link to post
Share on other sites