Sponsored Content
Full Discussion: Prize of being an Admin
The Lounge War Stories Prize of being an Admin Post 302642935 by ananthap on Friday 18th of May 2012 08:26:49 AM
Old 05-18-2012
With AIX-LPAR and all, your's must be a very big and so procedure oriented organisation. So you really have two approaches. One described earlier. ie. Do but dont tell anyone, take care etc.

The other : talk about it to end users, see how you can repeat it again for their benefit. ie. see to it that you become the end users' goto person for problem resolution. Then with your favourite user, try to wangle a seat in a meeting with the authorised vendor and so on. spread your wings man (or woman).

For your information, a recent article I read says that in future more and more IT persons will be away from core IT departments and get embedded in end user departments as co-ordinators, implementors and so on. As and when this happens in your organisation (ie downsizing, out sourcing) you can make the jump.

OK
 

6 More Discussions You Might Find Interesting

1. Solaris

fresh admin

hi everybody i'm just recreuted as UNIX system admin... please tell me from where do i have to begin... best regards (8 Replies)
Discussion started by: hmaiida
8 Replies

2. Solaris

Tape Admin

Tape: Need tape library help please. Need to configure a remote admin card in the L100. Anything helpful.....thxs (2 Replies)
Discussion started by: uwinix77
2 Replies

3. Post Here to Contact Site Administrators and Moderators

note for admin

i left a message for admin in the wrong thread.. it is in the what is on your mind thread since i can't move it or delete it.. i thought I would mention that I meant it to be in this thread.. sorry about the mistake.. thanx for your patience moxxx68 (3 Replies)
Discussion started by: moxxx68
3 Replies

4. What is on Your Mind?

Windows Admin switching to *nix Admin

I'm currently a Windows admin and have wanted to jump ship to the *nix side for a while now. I've been studying both through an lpic level 1 manual as I have time (focusing on debian), and a solaris 10 cert book. The problem is I only have a handful of hours a week to study, and my current job... (3 Replies)
Discussion started by: bobwilson
3 Replies

5. War Stories

Prize of being an Admin - Part 2

I was reading this thread of admin_xor Prize of being an Admin and thought will share this experience of mine which is kind of opposite to what he did - I didn't tell anybody what happened :D We were porting one of the subsystem from Solaris to Linux. As part of that we developed many wrapper... (23 Replies)
Discussion started by: ahamed101
23 Replies

6. What is on Your Mind?

Regarding Admin life either as DBA or UNIX Linux admin

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
ACCESS_LIST(5)						   Sun Grid Engine File Formats 					    ACCESS_LIST(5)

NAME
access_list - Sun Grid Engine access list file format DESCRIPTION
Access lists are used in Sun Grid Engine to define access permissions of users to queues (see queue_conf(5)) or parallel environments (see sge_pe(5)). A list of currently configured access lists can be displayed via the qconf(1) -sul option. The contents of each enlisted access list can shown via the -su switch. The output follows the access_list format description. New access lists can be created and exist- ing can be modified via the -au and -du options to qconf(1). Departments are a special form of access list that additionally allow assignment of functional shares and override tickets. Note, Sun Grid Engine allows backslashes () be used to escape newline ( ewline) characters. The backslash and the newline are replaced with a space (" ") character before any interpretation. FORMAT
The following list of access_list parameters specifies the access_list content: name The name of the access list as defined for userset_name in sge_types(1). type The type of the access list, currently one of ACL, or DEPT or a combination of both in a comma separated list. Depending on this parame- ter the access list can be used as access list only or as a department. oticket The amount of override tickets currently assigned to the department. fshare The current functional share of the department. entries The entries parameter contains the comma separated list of those UNIX users (see user_name in sge_types(1)) or those primary UNIX groups that are assigned to the access list or the department. Only a user's primary UNIX group is used; secondary groups are ignored. Only sym- bolic names are allowed. A group is differentiated from a user name by prefixing the group name with a '@' sign. Pure access lists allow enlisting any user or group in any access list. When using departments, each user or group enlisted may only be enlisted in one department, in order to ensure a unique assignment of jobs to departments. To jobs whose users do not match with any of the users or groups enlisted under entries the defaultdepartment is assigned, if existing. SEE ALSO
sge_intro(1), sge_types(1), qconf(1), sge_pe(5), queue_conf(5). COPYRIGHT
See sge_intro(1) for a full statement of rights and permissions. SGE 6.2u5 $Date$ ACCESS_LIST(5)
All times are GMT -4. The time now is 03:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy