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
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
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
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
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
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
Can someone tell me why pkill won't work on firefox anymore? (11 Replies)
Discussion started by: cokedude
11 Replies
7. Slackware
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
(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
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
LEARN ABOUT POSIX
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)