Sponsored Content
The Lounge What is on Your Mind? They won't need so many sys admins anymore Post 302956921 by sparcguy on Monday 5th of October 2015 09:51:12 AM
Old 10-05-2015
I've already gone back to work in HP 3 times previously before already once contract expired I left then later rejoined then resigned and rejoined again.

But in HP once you get laid off it means that position is considered redundant and can no longer be filled by anybody.

Also furthermore this time they have relocated the support overseas to low cost centers.

I think the industry is changing even shrinking with the advent of cloud computing, in time systems are going to get more efficient and cheaper and that will put pressure on operating costs, budgets, salaries they don't need so many sys admins or engineers to run around in-country anymore some places I hear they just have a pool of less than 10 people overseas datacenter can manage several thousand virtual servers on cloud.


Sure I think there are many sys admin jobs around still if I wanted to continue or maybe I should bite the bullet now and break out to try something else.


The only jobs in IT today I see that will be hard to farmed out are:

local desktop support - low pay
it security
audit and compliance
 

9 More Discussions You Might Find Interesting

1. Solaris

Any sys admins from uk?

Hello Guys, im new to this forum. Im from UK and ive recently completed my SCSA I & II and also got trained in Veritas Suite (Veritas Volume Manager and Veritas Clusters, Veritas NetBackup), SAN Configuration. I was trying to get a break as a junior sun solaris admin. I am applying for the jobs... (1 Reply)
Discussion started by: megadeth
1 Replies

2. UNIX for Dummies Questions & Answers

Can't login as SU anymore - SU: NO SHELL

the root shell has been changed in the file /etc/passwd, basically pointing to an incorrect directory. So now every time we login as 'su' I get the message 'su: no shell' so we can't login as superuser. Is there an easy way to rectify this? please use step by step instructions/commands - I... (4 Replies)
Discussion started by: homechoice
4 Replies

3. AIX

won't mount /usr...won't boot fully

Hello: NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies

4. Solaris

Sun Fire won't boot anymore

Hi all - I have an issue with our (way old) single processor SunFire 280R, running Solaris 9.0.4. It won't boot even after multiple power cycles. There was a power outage last week end in the computer room, so this might have to do. In normal boot mode, the screen shows a single line : ... (5 Replies)
Discussion started by: bostella
5 Replies

5. UNIX for Dummies Questions & Answers

Can't SSH as root anymore!

I've screwed something up in my sshd_config apparently, because I can't ssh with root anymore. I had disabled root login for security reasons, but then my ssh credentials with full administrative privelges stopped working. So then I reenabled root login (and reset ssh), but root now isn't... (3 Replies)
Discussion started by: cquarry
3 Replies

6. UNIX for Advanced & Expert Users

pkill won't work on firefox anymore

Can someone tell me why pkill won't work on firefox anymore? (11 Replies)
Discussion started by: cokedude
11 Replies

7. Slackware

Anyone Using Slackware Anymore?

We used to use Slackware, but then moved all our servers to Ubuntu Linux. Does anyone use Slackware anymore? (8 Replies)
Discussion started by: Neo
8 Replies

8. Programming

Interactive Python 3.5+ sys.stdout.write() AND sys.stderr.write() bug?

(Apologies for any typos.) OSX 10.12.3 AND Windows 10. This is for the serious Python experts on at least 3.5.x and above... In script format sys.stdout.write() AND sys.stderr.write() seems to work correctly. Have I found a serious bug in the interactive sys.stdout.write() AND... (2 Replies)
Discussion started by: wisecracker
2 Replies

9. UNIX for Beginners Questions & Answers

Bash script won't run because hardware won't produce display

Can anyone offer any advice on how to modify the script below to work on a new system we have, that has no graphics capability? We admin the system through a serial RAS device. I've tried running the below script through the RAS and through an ssh -X session. It failed with something like "GTK... (3 Replies)
Discussion started by: yelirt5
3 Replies
LUSER(8)						      System Manager's Manual							  LUSER(8)

NAME
luser - process to control the clueless individuals who (mis)use computer systems, peripheral devices and system administrators. Word play on "loser" and "user". SYNOPSIS
luser [-d] [-g<level>] [-s] <lusername> DESCRIPTION
luser is the primary tool a system administrator uses to manage end-user requests. This powerful tool can actually cause the specified user to perform actions as specified by the flags. With no flags, luser deletes every running process owned by the specified <lusername>. OPTIONS
-d Disk reclamation mode. Remove all files in the home directory of <lusername>. -g<level> Grovel mode. Causes the specified luser to make an act of contrition to the sysadmin for past sins. The <level> indicates the sever- ity of the contrition: LEVEL 0 User makes a sincere apology and promises to never do it again. 1 User buys sysadmin a large quantity of sysadmin's favorite beverage. 2 User signs over ownership of his/her car to sysadmin. 3 User resigns from the company after writing a long letter of apology detailing his/her failings. 4 User commits ritual suicide by sucking on a power strip and grounding himself to a conduit. NOTES
Sysadmins are encouraged to use the -s option as a way to smarten up the world's user base. Use the -g option at level 4 outside the con- fines of the machine room. The more lusers that witness the act, the better. SEE ALSO
sysadmin(1) BUGS
Occasionally, the luser may survive the effects of luser -g4. In that event, a second invocation of the command will usually prove to be fatal. HISTORY
Written by Eric L. Pederson <eric@bofh.org.uk>. 25 September 1995 LUSER(8)
All times are GMT -4. The time now is 11:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy