I had to research nanosleep for a different reason quite a while ago. The nanosleep call is in the glibc library and is done totally in user space with a spin loop. In my case, I was getting inconsistent results running more than one copy of iperf at a time. Unless nanosleep has been re-written since Fedora 6 days, things probably have not changed.
On Wed, Apr 24, 2013 at 10:18 PM, logical american < [email protected]> wrote: > On 4/24/2013 4:06 PM, Wayne E. Van Loon Sr. wrote: > > Do I understand this right, that possibly automatic checks for updates > > is what is freezing your machine? > > > > Wayne > In this case, the update was done manually, after the alert, but if the > machine was set for automatic updates, I do believe the same thing would > occur. I believe that the freezing is occurring sometime during the > update process. Of course further careful investigation is needed. > > -- > CONFIDENTIAL: This email message and/or any attachments is for the sole > use of the intended recipient(s) and may contain confidential information. > Any unauthorized review, use, copying, dissemination, disclosure, retention > or distribution is strictly prohibited. If you are not the intended > recipient, please contact the sender by reply email and destroy all copies > of the original message along with any attachments. This communication > (including attachments) is covered by the Electronic Communication Privacy > Act, U.S.C. Sections 2510-2521. > > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
