|
When you use the setitimer() function you can't help but use signals. setitimer uses signals as a trigger. I simply added another signal to shut down gracefully. If you use setitimer() at all, you will by necessity use signals (at least this is true on linux - if this isn't true on OS/400 then just say so).
My complaint was that you used the signal() API, not that signals were sent to the process.
It's true that setitimer() sends a signal to your program. That does not, however, mean that you have to use signal() to catch it. My assertion is that it'd be a better example if you used sigaction() instead of signal().
Because the example is relevant to the post that setitimer() could solve the problem.
I already suggested that setitimer() could solve the problem. You responded to that with "Look at my wonderful Linux C program". Unfortunately, that program neither works on the iSeries, or is written in RPG, consequently doesn't do an iSeries RPG programmer any good.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
