hi
i´m making a program, and i would like to know how can i know what key was pressed. i'm using Sun5.7 and C.
is there a keypress/keypressed function in C?
how can i know recognize the keys (enter, tab, shift, etc.)?
can i recognize two keys ? (shift+A, ctrl+C, etc)
any idea.. thanks (4 Replies)
I want my program(ksh) to execute further only if the return key is pressed.
Please help.
i have already tried "\n", "\r", "^M" .
Thanks in advance (2 Replies)
hi folks,
i am using sun solaris, when i press escape key in putty/netterm screen will blink for a second, plese let me know where this setting is done by my admin, what i feel is my admin must have set some control key for this so that screen will refresh each time i press escape key. please let... (1 Reply)
Hi,
When I run script on Sun Solaris (sassetup), it prompts to "Press Enter To Continue".
Now I want to automate this, ie put sassetup in a script file. So, when I run this file, it should be executed automatically without waiting for anyone to press Enter Key.
I have tried the following... (1 Reply)
Hello everyone.
I'm trying to create a script that waits a given amount of time unless a given key is pressed. I found a very useful thread here
https://www.unix.com/shell-programming-scripting/59605-trap-key-press-script.html
however, I cannot figure out a way of avoiding the keypress if the... (2 Replies)
Hi all,
I need to know how to test a pressed key is arrowup or arrowdown and etc..
I found that the "echo" won't print anything if i enter the arrowup in the below code:
read
echo "you pressed $REPLY"
Then i find a way to achieve my goal.
1 #! /bin/bash
2
3 ARROWUP='\;then... (4 Replies)
Hi,
I have to get into BIOS and disable onbaord NICS for an IBM server, can someone please help me out.
I tried hitting F1 when reboot to get into BIOS, but it seems like a setup screen and I dont see any option to disable NICS?
Thanks
Sam (0 Replies)
I have a popup window that appears on every boot up.
I would like to have it dismissed automatically each time instead of having to hit the enter key.
I thought I could write a script that would execute on startup.
I tried this
xdotool key return
andy@7_~/Downloads$ xdotool key ... (7 Replies)
Discussion started by: drew77
7 Replies
LEARN ABOUT SUSE
snice
SKILL(1) Linux User's Manual SKILL(1)NAME
skill, snice - send a signal or report process status
SYNOPSIS
skill [signal to send] [options] process selection criteria
snice [new priority] [options] process selection criteria
DESCRIPTION
These tools are probably obsolete and unportable. The command syntax is poorly defined. Consider using the killall, pkill, and pgrep com-
mands instead.
The default signal for skill is TERM. Use -l or -L to list available signals. Particularly useful signals include HUP, INT, KILL, STOP,
CONT, and 0. Alternate signals may be specified in three ways: -9 -SIGKILL -KILL.
The default priority for snice is +4. (snice +4 ...) Priority numbers range from +20 (slowest) to -20 (fastest). Negative priority num-
bers are restricted to administrative users.
GENERAL OPTIONS -f fast mode This is not currently useful.
-i interactive use You will be asked to approve each
action.
-v verbose output Display information about selected
processes.
-w warnings enabled This is not currently useful.
-n no action This only displays the process ID.
-V show version Displays version of program.
PROCESS SELECTION OPTIONS
Selection criteria can be: terminal, user, pid, command. The options below may be used to ensure correct interpretation. Do not blame
Albert for this interesting interface.
-t The next argument is a terminal (tty or pty).
-u The next argument is a username.
-p The next argument is a process ID number.
-c The next argument is a command name.
SIGNALS
The signals listed below may be available for use with skill. When known, numbers and default behavior are shown.
Name Num Action Description
() ()
0 0 n/a exit code indicates if a signal may be sent
ALRM 14 exit
HUP 1 exit
INT 2 exit
KILL 9 exit this signal may not be blocked
PIPE 13 exit
POLL exit
PROF exit
TERM 15 exit
USR1 exit
USR2 exit
VTALRM exit
STKFLT exit may not be implemented
PWR ignore may exit on some systems
WINCH ignore
CHLD ignore
URG ignore
TSTP stop may interact with the shell
TTIN stop may interact with the shell
TTOU stop may interact with the shell
STOP stop this signal may not be blocked
CONT restart continue if stopped, otherwise ignore
ABRT 6 core
FPE 8 core
ILL 4 core
QUIT 3 core
SEGV 11 core
TRAP 5 core
SYS core may not be implemented
EMT core may not be implemented
BUS core core dump may fail
XCPU core core dump may fail
XFSZ core core dump may fail
EXAMPLES
Command Description
snice seti crack +7 Slow down seti and crack
skill -KILL -v /dev/pts/* Kill users on new-style PTY devices
skill -STOP viro lm davem Stop 3 users
snice -17 root bash Give priority to root's shell
SEE ALSO killall(1)pkill(1)kill(1)renice(1)nice(1)signal(7)kill(2)STANDARDS
No standards apply.
AUTHOR
Albert Cahalan <albert@users.sf.net> wrote skill and snice in 1999 as a replacement for a non-free version, and is the current maintainer
of the procps collection. Please send bug reports to <procps-feedback@lists.sf.net>.
()