Do you want your other PC going to sleep?
If not disable the sleep mode, what OS is running on this other PC we may be able to assist in setting this up.
If you would still like your other PC to sleep consider using wake-on-lan to wake your other PC up first before trying to access it with ssh. I'm thinking of something like this:
Note change 00:1D:99:99:AC:99 to the MAC address of the otherPC network card
wol may not be available natively on your system you can download it from the SourceForge wol project
I wrote a ksh script for Helpdesk. I need to know how to disable ctrl-c,ctrl-z,ctrl-d..... so that helpdesk would not be able to get to system prompt :confused: (6 Replies)
Hi, I want to use the "at" command in a loop to start different processes every hour or so, but I don't know how to script a Ctrl-D so I can escape from the "at" after the last command I want to run and then go to the next command in the loop.
Example:
i=1
while
do
j=$((i*60))
at... (2 Replies)
how to trap the ctrl c in unix shell script
my script is running in while loop it should not be terminate with ctrl c.
if i press ctrl c while running script it shloud ignore the same.
please healp..........
thanks in advance (2 Replies)
H! I have written script where it need to invoke the perl script in background, then write the pid in temp file then bring back the job to foreground. whenever the Ctrl-C or Ctrl-Z is pressed in the script has to exit and prompt should be dispalyed. but this script causing exit from shell session... (2 Replies)
Hi,
while executing shell script, in the middle of the process, if we kill the shell script( ctrl+z or ctrl+c), script will be killed and the files which using for the script will be in the folder.
How to handle those scenarios. Is there any possibilities, if user breaks the script, I need to... (3 Replies)
The below script has Perl script in it where it gives the usage details.
filer.sh
echo
echo -en "Enter filer : "
read filer
echo "test.pl -f $filer -F L"
Output
=========
The following hosts are online and available:
Name Total Allocated Used ... (2 Replies)
Hi friends,
I am trying to add a newline char ('\n') between the query and the commit statement in the following shell script.
#! /bin/sh
echo "select * from tab; commit;" > data.sql
I have tried typing in "Ctrl-V + Ctrl-J" combination which has inserted ^@ (NUL) character but the commit... (1 Reply)
Hi..!
I'm stuck with my automation of starting a process and keeping it running even after the current ssh session has exited..
So i'm trying to use command 'screen'. which is doing exactly what i wanted, But the problem is automation of the same.
i will have to press Ctrl+a and Ctrl+d for... (2 Replies)
Hi All,
I am using the script for creating local queue and passing the arguments while running the script as below
n=0
while
do
e=`expr $n + 3`
echo 'DEFINE QL('$e') MAXDEPTH('$6') MAXMSGL('$7') DEFPSIST('$8') '$9'' | /apps/mqm_opt/bin/runmqsc $2
n=`expr $n + 1`
done
Running the... (5 Replies)
Discussion started by: Anusha M
5 Replies
LEARN ABOUT OSF1
sleep
sleep(9r)sleep(9r)NAME
sleep - General: Puts a calling process to sleep
SYNOPSIS
void sleep(
caddr_t *channel,
long pri );
ARGUMENTS
Specifies a unique address associated with the calling kernel thread to be put to sleep. Specifies whether the sleep request is interrupt-
ible. Setting this argument to the PCATCH flag causes the process to sleep in an interruptible state (that is, the kernel thread can take
asynchronous signals). Not setting the PCATCH flag causes the process to sleep in an uninterruptible state (that is, the kernel thread can-
not take asynchronous signals).
DESCRIPTION
The sleep routine puts a calling process to sleep on the address specified by the channel argument. Some common addresses are the lbolt
argument, a buf structure, and a proc structure. This address should be unique to prevent unexpected wake/sleep cycles, which can occur if
different processes are sleeping on the same address accidentally. If you set the PCATCH flag in the pri argument, the sleep routine puts
signals on the queue and does not wake up the sleeping process.
The sleep and wakeup routines block and then wake up a process. Generally, device drivers call these routines to wait for the transfer to
complete an interrupt from the device. That is, the write routine of the device driver sleeps on the address of a known location, and the
device's Interrupt Service Interface (ISI) wakes the process when the device interrupts. It is the responsibility of the wakened process to
check if the condition for which it was sleeping has been removed.
NOTES
The operating system provides two ways to put a process to sleep: interruptible and uninterruptible. The sleep routine performs an uninter-
ruptible sleep operation if you do not set the PCATCH flag and an interruptible sleep operation if you set the PCATCH flag. This means
that device drivers cannot call sleep at interrupt context because at interrupt context there is no calling process to be put to sleep.
Thus, a device driver's Interrupt Service Interface (ISI) and those routines called from within the ISI must not call the sleep routine.
On this operating system, you cannot use pri to set the scheduling priority of the calling process.
RETURN VALUES
None
FILES SEE ALSO
Routines: wakeup(9r)sleep(9r)