Sponsored Content
The Lounge What is on Your Mind? IT jobs/careers without formal qualifications. Post 302526747 by Corona688 on Wednesday 1st of June 2011 11:32:47 AM
Old 06-01-2011
It really depends on the work environment. I think I did fairly well without extensive qualifications but then, I'm in a small rural business, where technically capable server personnel are pretty rare; they didn't really have much infrastructure before I built it, which gave me a chance to prove myself by finding and solving needs...
This User Gave Thanks to Corona688 For This Post:
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UNIX Admin Careers

I wish to transition from Mainframe to Open Systems Storage Administration. How much training would I need in order to meet requirements for an AIX Administrator position? (3 Replies)
Discussion started by: ednan171
3 Replies

2. Shell Programming and Scripting

background jobs exit status and limit the number of jobs to run

i need to execute 5 jobs at a time in background and need to get the exit status of all the jobs i wrote small script below , i'm not sure this is right way to do it.any ideas please help. $cat run_job.ksh #!/usr/bin/ksh #################################### typeset -u SCHEMA_NAME=$1 ... (1 Reply)
Discussion started by: GrepMe
1 Replies

3. UNIX for Dummies Questions & Answers

Information about Unix careers

Hi, I'm looking to go into a career related to either Unix, or web development(or something alike). I want to get a Bachelor Of Computer Science degree(I'm planning to). I don't know which kind of jobs might be a good choice for me though. Like I said, I'd like something to do with either Unix or... (2 Replies)
Discussion started by: undecided
2 Replies

4. Solaris

Cron jobs and at jobs

There are two jobs in Solaris , Cron and at jobs.. I know how to disable or enable cron jobs. How can I enable at jobs and disable it. Kindly help. Rj (2 Replies)
Discussion started by: jegaraman
2 Replies

5. Shell Programming and Scripting

waiting on jobs in bash, allowing limited parallel jobs at one time, and then for all to finish

Hello, I am running GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu). I have a specific question pertaining to waiting on jobs run in sub-shells, based on the max number of parallel processes I want to allow, and then wait... (1 Reply)
Discussion started by: srao
1 Replies

6. Shell Programming and Scripting

Shell script to run multiple jobs and it's dependent jobs

I have multiple jobs and each job dependent on other job. Each Job generates a log and If job completed successfully log file end's with JOB ENDED SUCCESSFULLY message and if it failed then it will end with JOB ENDED with FAILURE. I need an help how to start. Attaching the JOB dependency... (3 Replies)
Discussion started by: santoshkumarkal
3 Replies
sys_attrs_cam(5)						File Formats Manual						  sys_attrs_cam(5)

NAME
sys_attrs_cam, sys_attrs_cam_disk, sys_attrs_cam_tape - SCSI CAM I/O subsystem attributes DESCRIPTION
This reference page lists and describes attributes for the following kernel subsystems associated with the SCSI CAM I/O system: cam cam_adapter-id cam_disk cam_tape An asterisk (*) precedes the name of an attribute that is modifiable at run time. However, the ability to modify the value at run-time may be a software requirement. Read the attribute description carefully to determine whether run-time configuration should ever be done manu- ally. Refer to the sys_attrs(5) reference page for an introduction to the topic of kernel subsystem attributes. cam and Adapter-Specific Cam Subsystem Attributes Values of attributes for the CAM (cam) subsystem and adapter-specific (cam_adapter-id) CAM subsystems should never be modified. cam_disk Subsystem Attributes Attributes for the cam_disk subsystem should be changed internally or under the direction of support personnel. Most of these attributes have a global effect across all disk devices. If the affected devices are of the same type, a global change may be appropriate. However, global changes applied to devices with different requirements is likely to adversely affect some of the devices. The Hardware Manager application allows you to apply device-specific adjustments and it is recommended that you use this interface. Number of seconds that the subsystem waits in the presence of repeated device busy signals before performing a bus device reset operation on the device. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. This attribute has effect only in a TruCluster environment. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. This attribute has effect only in a TruCluster environment. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. This attribute has effect only in a TruCluster environment. Do not modify the default setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. A value that indicates how long to wait after the start of constant "no connection" errors for the disk device before starting recovery procedure. The default value indicates that all bits are set to 1. This specifies that disk driver defaults for this wait interval are applied. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. A set- ting change is global; that is, it overrides the default wait interval for all disk drivers and is likely to cause unpredictable behavior in some devices. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. Disk drive initialization state, which is set by the subsystem. This attribute is query only. A query-only identifier that is set by the subsystem. A query-only identifier that is set by the subsystem. Do not modify the setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. Default value: 2 (spinups) Number of seconds that device polling reveals a drive is inactive before spinning down the disk. Default value: 30 (seconds) Minimum value: 5 Maximum value: 65,535 cam_tape Subsystem Attributes Do not modify the default setting for this attribute unless instructed to do so by support personnel or by patch kit documentation. Default value: 0 A value queried by the tape device driver to determine its initialization state. You cannot modify this variable. The driver changes the value from 0 (when the system starts to boot) to 1 (during the boot operation). A value that specifies the system behavior when a write-locked tape is opened with the O_RDWR or O_WRONLY flag. The default and rec- ommended behavior (1) is to return failure on the open operation. The alternate behavior (0) is to allow the open operation but return failure on an attempt to write to the tape. Default value: 1 It is recommended that you do not change the default. The 0 value is intended only for customers whose applications ran on DIGITAL UNIX versions earlier than Version 4.0B and depend on the open behavior in effect for those earlier versions. SEE ALSO
sys_attrs(5) sys_attrs_cam(5)
All times are GMT -4. The time now is 04:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy