04-02-2009
Quote:
Originally Posted by
rhfrommn
I don't trust the salary numbers in that review posted a few messages up. The starting is way too low, the 5 and 10 year may be too high. Depends on where you are working to a great extent, but they aren't accurate for my area (Minneapolis, MN). Finding jobs is fairly easy. Recruiters do call you fairly often once you're established and well-known. I've been laid off 3 times and switched jobs on my own 3 times in 10 years, and never been unemployed more than 8 days. But don't expect a 20% raise every time or to be making six figures by year 5. And totally ignore the guy talking about being an IPO millionaire. That guy is a comedian or an idiot . . . I'm guessing this is fairly old and they are referring to the late 90's tech bubble when things were out of control. Or maybe those comments came from people in silicon valley where you can make $150,000 and still be poor because the cost of living is so high.
Most places I've worked are pretty flexible about hours. They know Unix admins work nights and weekends pretty frequently so usually they aren't very strict about being there 9 to 5 every day. You will definitely be putting in your hours, just not the same hours as everybody else.
Vacations have never been a problem except for one job where I was the only Unix admin. Even there I could take days off but I had to prepare by making sure all necessary work during those days was done ahead of time and I had a backup to cover while I was gone (usually a DBA or programmer). I do not take my pager or laptop on vacation, but in an emergency it is possible they'd call me and that would be ok with me if it truly was important.
Thanks for the answer about the accuracy about the information.
Okay, so most people here seem to be putting the starting salary around $50 - $75k a year. What would you say would be the salary after 5 yrs or 10yrs? I thought the thing about making millions sounded a bit odd. That's why I was asking around here about the accuracy of the info. I know I read on a forum a few months ago some guy said he and other system administrators he knew were making about $75 an hour after working about 10 yrs. Where I read this I think the same person said to expect expect about $40 - $50 per/hr starting salary and that you can add about $3 an hour per extra years experience in the job. Does this info sound about right? Sorry for all the questions
Thanks for all the help though... I really appreciate it!
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have been working with UNIX (HP-UX) now for a couple of years. Have become quite capable in shell scripting and general UNIX use. The local university offers a certification course in UNIX administration which I am considering taking. However, the certification is geared toward UNIX in general... (13 Replies)
Discussion started by: google
13 Replies
2. UNIX for Advanced & Expert Users
Hi,
Can somebody give me some information on System V & Berkley's Unix formats.
Any link will be helpful.
thanks (6 Replies)
Discussion started by: vibhor_agarwali
6 Replies
3. Solaris
I'm planning to take System Administration certification in SUN Solaris. Can some one suggest me if there are any links are URLs to find sample question papers.
Pharos (2 Replies)
Discussion started by: pharos467
2 Replies
4. Shell Programming and Scripting
I do not know UNIX shell scripting so as an alternative which language would you think is better for daily System Administration tasks. Perl or PHP? I know a little about both. (5 Replies)
Discussion started by: blackopus
5 Replies
5. UNIX for Dummies Questions & Answers
How does unix system administration, unix programming, unix network programming differ?
Please help. (0 Replies)
Discussion started by: thulasidharan2k
0 Replies
6. UNIX for Dummies Questions & Answers
What are the career options in unix apart from unix system administration? (2 Replies)
Discussion started by: thulasidharan2k
2 Replies
7. Solaris
Sorry I'm kind of desperate here :wall:, there's a security audit coming next week :( and I can't seem to find solutions for the questions below :confused:.
1) I need to limit usage on account during non-working hours.
There's no /etc/security/time.conf file in my system should I create it?
... (0 Replies)
Discussion started by: ShouTenraku
0 Replies
8. Shell Programming and Scripting
Hi guys,
I am currently working as a system administration engineer, administering telecom applications on linux/unix platforms.
I want to learn new things and improve the ones that i have and for this i though to really work on some project or something but i lack of ideas.
I want to be... (2 Replies)
Discussion started by: capitanui
2 Replies
9. What is on Your Mind?
Hi all,
I wonder if you guys could give me some advice on this. I have messed around with Linux for the last few years, and I'm at the point where I would like to become a system administrator - as a career.
I already have a bachelor's degree, but it is in the humanities (art history) so... (2 Replies)
Discussion started by: ScottLew
2 Replies
at(1) General Commands Manual at(1)
Name
at, batch - execute commands at a later time
Syntax
at time [day] [file]
at -r job...
at -l [job...]
batch [file]
Description
The and commands use a copy of the named file (standard input default) as input to or at a later time. A command to the current directory
is inserted at the beginning, followed by assignments to all environment variables. When the script is run, it uses the user and group ID
of the creator of the copy file.
The command allows the user to specify when the commands should be executed, while jobs queued with execute when the load level of the sys-
tem permits.
The environment variables, current directory, and are retained when the commands are executed. However, open files, traps, and priority
are lost.
Users are permitted to use the and commands if their name appears in the file If that file does not exist, the file is checked to determine
if the user should be denied access to and If neither file exists, only the superuser is allowed to submit a job. If only the file exists
and is empty, global usage is permitted. The files consist of one user name per line.
The time is 1 to 4 digits. It can, but does not have to be, followed by A, P, N or M which stand for AM, PM, noon or midnight, respec-
tively. The A, P, N, and M suffixes are case-insensitive. One and two digit numbers are interpreted as hours, three and four digits to be
hours and minutes. If three digits are specified, the first digit is interpreted to be an hour in the range 0-9, and the second and third
digits as minutes. If no letters follow the digits, a 24 hour clock time is presumed.
In addition to 1-4 digits, and suffixes A, P, M, N, you can also specify:
at hh:mm
at h:mm
at ham
at hpm
at noon
at midnight
The optional day is either a month name followed by a day number or by a day of the week. If the word week follows, the or command is
invoked in seven days. Both commands also recognize standard abbreviations for the days of the week and months of the year. The following
are examples of legitimate commands:
at 8am jan 24
at 1530 fr week
The programs are executed by periodic execution of the command from The granularity of depends upon how often atrun is executed. The com-
mand examines the file every minute. The file determines when is executed. The default is every 15 minutes on the 1/4 hour. Editing makes
run more or less frequently.
Standard output or error output is lost unless it is redirected.
The and commands write the job number to standard error.
Options
-r Removes jobs previously scheduled by or The number is the number reported at invocation by or Only the superuser is
allowed to remove another user's jobs.
-l Lists all job numbers for all jobs submitted by the user issuing the command. Even if the user is "root", only numbers
for jobs submitted by "root" are displayed. To see the numbers of all jobs submitted, enter the following command:
% ls -l /usr/spool/at
Restrictions
Due to the granularity of the execution of there may be bugs in scheduling jobs almost exactly 24 hours into the future.
Diagnostics
Complains about various syntax errors and times that are out of range.
Files
/usr/lib/atrun executor run by cron(8)
in /usr/spool/at:
yy.ddd.hhhh.* activity for year yy, day dd, hour hhhh.
lasttimedone last hhhh
past activities in progress
/usr/spool/at/at.allowlist of allowed users
/usr/spool/at/at.denylist of denied users
/usr/spool/at spool directory
/usr/lib/cron XOPEN compatibility
See Also
crontab(5), cron(8)
at(1)