05-07-2013
I want to become a Linux admin..
Hi ,
I have skill set in unix/shell scripting. But I would like to become a linux admin..So could you please help on this..
1) what are the things need to be learn,
2) any reference should be appreciable.
3) or any website..
THanks,
Mani
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have just been handed two new Suse 7.2 Linux systems to Administer.
We are wanting to setup monitoring of applications, file system space, etc. Are there standard log directories that an experienced Admin would put scripts, log files, documentation, etc. or just put it under the /root Home... (1 Reply)
Discussion started by: darthur
1 Replies
2. UNIX for Dummies Questions & Answers
Hi
I am working on LINUX shell scripting. I have root privileges and I know some basic root/admin commands like user creation, modification and so on. Till last week i was able to create users but now i am not able to create users or groups. When I give the command i got an error as ... (6 Replies)
Discussion started by: naina
6 Replies
3. Linux
Im a solaris admin, not too familair with linux, can anyone give me 5-10 questions I should ask a Linux admin Im going to interview for a job. The job requires an experiencend Linux admin, who can do backups, system builds, create file systems, monitor, etc... in a production environment. Any help... (3 Replies)
Discussion started by: csaunders
3 Replies
4. UNIX for Dummies Questions & Answers
I'm working on further developing my Unix skills and I'm just curious what some of the experienced admins out there would consider to be 10 essential commands every admin should know. (12 Replies)
Discussion started by: Arkitech
12 Replies
5. Linux
Hi,
Please give some important admin command document . which is helpful in my role.
THanks,
Mani (8 Replies)
Discussion started by: Mani_apr08
8 Replies
6. UNIX for Dummies Questions & Answers
Hey guys, I've been doing some study guides and practice exams for some certs, had some friends give me some things to do in preperation as well. I have compiled a few of the questions I was unable to figure out:wall:, I was hoping to get some help here. I am running Fedora16. If you need any... (2 Replies)
Discussion started by: jahburmski
2 Replies
7. What is on Your Mind?
I am planning to choose my career as Unix/Linux Admin or a DBA. But I have come to know from forums and few admins like the job will be 24/7. I have few questions on that.
Can we get "DAY" shifts in any one of the admin Job ?
Can't we have shift timings in any company ?
Eventhough the... (7 Replies)
Discussion started by: Jacktts
7 Replies
8. Linux
Hello guys,
First I apologize for asking non technical question but I am goging to move to the USA and I have 8 year experience as a senior linux admin, I am administering storage subsystems as well.
Can you please tell me how much is an average salary for Linux admins?
Thanks in advance. (4 Replies)
Discussion started by: Vit0_Corleone
4 Replies
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), kill(2), signal(7)
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>.
Linux March 12, 1999 SKILL(1)