Sponsored Content
The Lounge What is on Your Mind? Do You Sleep With Battery Powered Devices? Post 302321174 by reborg on Saturday 30th of May 2009 07:47:47 PM
Old 05-30-2009
Perderabo,

I took it to mean literally in the bed. I know a lot of people sleep with their mobile phone in the bed either because of on-call work or as an an alarm clock.

Also a question. How well does the pink noise generator work for you? I have often wondered how effective they are.
 

4 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

passthrough devices vs. named devices

I am having trouble understanding the difference between a passthrough device and a named device and when you would use one or the other to access equipment. As an example, we have a tape library and giving the command "camcontrol devlist" gives the following output: akx# camcontrol... (1 Reply)
Discussion started by: thumper
1 Replies

2. SCO

COuld not telnet but server powered

Hi We are running SCO unixware 7.1.1. I am new to unix so hope someone can help. This morning no one could log into the unix server by ssh. Server could not be pinged but the server was powered. We could not also view the screen. We have to manually power it down and it came back up. I... (0 Replies)
Discussion started by: tjsingh
0 Replies

3. Programming

SQL Powered Awk (SPAWK)

If anyone is interesting in using awk with MySQL databases, then I have some good news: I've developed a (shared) library, namely libspawk.so, using MySQL C API and GNU awk's extension feature. If you are using MySQL and you like awk, then you'll find very useful to use SPAWK module. Please... (0 Replies)
Discussion started by: Panos1962
0 Replies

4. Shell Programming and Scripting

Wrapping 'sleep' with my 'resleep' function (Resettable sleep)

This is a very crude attempt in Bash at something that I needed but didn't seem to find in the 'sleep' command. However, I would like to be able to do it without the need for the temp file. Please go easy on me if this is already possible in some other way: How many times have you used the... (5 Replies)
Discussion started by: deckard
5 Replies
sleep(3UCB)					     SunOS/BSD Compatibility Library Functions					       sleep(3UCB)

NAME
sleep - suspend execution for interval SYNOPSIS
/usr/ucb/cc [ flag ... ] file ... int sleep( seconds); unsigned seconds; DESCRIPTION
sleep() suspends the current process from execution for the number of seconds specified by the argument. The actual suspension time may be up to 1 second less than that requested, because scheduled wakeups occur at fixed 1-second intervals, and may be an arbitrary amount longer because of other activity in the system. sleep() is implemented by setting an interval timer and pausing until it expires. The previous state of this timer is saved and restored. If the sleep time exceeds the time to the expiration of the previous value of the timer, the process sleeps only until the timer would have expired, and the signal which occurs with the expiration of the timer is sent one second later. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |MT-Level |Async-Signal-Safe | +-----------------------------+-----------------------------+ SEE ALSO
alarm(2), getitimer(2), longjmp(3C), siglongjmp(3C), sleep(3C), usleep(3C), attributes(5) NOTES
Use of these interfaces should be restricted to only applications written on BSD platforms. Use of these interfaces with any of the system libraries or in multi-thread applications is unsupported. SIGALRM should not be blocked or ignored during a call to sleep(). Only a prior call to alarm(2) should generate SIGALRM for the calling process during a call to sleep(). A signal-catching function should not interrupt a call to sleep() to call siglongjmp(3C) or longjmp(3C) to restore an environment saved prior to the sleep() call. WARNINGS
sleep() is slightly incompatible with alarm(2). Programs that do not execute for at least one second of clock time between successive calls to sleep() indefinitely delay the alarm signal. Use sleep(3C). Each sleep(3C) call postpones the alarm signal that would have been sent during the requested sleep period to occur one second later. SunOS 5.10 12 Feb 1993 sleep(3UCB)
All times are GMT -4. The time now is 01:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy