|
Not sure if it came from Unix. It very well may have as it also has Unix like permissions associated with it (RXW etc.). It shows the job info (26 char name) as 'process that last posted to it'. If semaphore is used as a simple locking mechanism, that process can be construed as the one that locked the semaphore. If used for resource accounting.... I suppose it could still be stretched to mean 'last process that locked it' if max value has been reached. If max value has not been reached, then semaphore isn't truly locked out (i.e. processes can still post to it). Elvis -----Original Message----- Subject: Re: Semaphor That is pretty neat! I know that win32 semaphores dont store the id of the processes that have locked it. Is it a feature of Unix that allows your product to determine which job has locked the semaphore? -Steve
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.