04-06-2009
Quote:
Originally Posted by
zxmaus
Going into engineering without having practiced the OS is not a good idea - you should definitely have reached senior level (5+ years in your OS) knowledge before thinking about.
This comment is spot on. In most cases system engineering is a role which does not even entertain the possibility of entry level positions. It is expected that a person has the practical experience to back up design decisions and the standing and influence to make and drive changes.
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
roles(1) User Commands roles(1)
NAME
roles - print roles granted to a user
SYNOPSIS
roles [ user ...]
DESCRIPTION
The command roles prints on standard output the roles that you or the optionally-specified user have been granted. Roles are special
accounts that correspond to a functional responsibility rather than to an actual person (referred to as a normal user).
Each user may have zero or more roles. Roles have most of the attributes of normal users and are identified like normal users in passwd(4)
and shadow(4). Each role must have an entry in the user_attr(4) file that identifies it as a role. Roles can have their own authorizations
and profiles. See auths(1) and profiles(1).
Roles are not allowed to log into a system as a primary user. Instead, a user must log in as him-- or herself and assume the role. The
actions of a role are attributable to the normal user. When auditing is enabled, the audited events of the role contain the audit ID of the
original user who assumed the role.
A role may not assume itself or any other role. Roles are not hierarchical. However, rights profiles (see prof_attr(4)) are hierarchical
and can be used to achieve the same effect as hierarchical roles.
Roles must have valid passwords and one of the shells that interprets profiles: either pfcsh, pfksh, or pfsh. See pfexec(1).
Role assumption may be performed using su(1M), rlogin(1), or some other service that supports the PAM_RUSER variable. Successful assumption
requires knowledge of the role's password and membership in the role. Role assignments are specified in user_attr(4).
EXAMPLES
Example 1: Sample output
The output of the roles command has the following form:
example% roles tester01 tester02
tester01 : admin
tester02 : secadmin, root
example%
EXIT STATUS
The following exit values are returned:
0 Successful completion.
1 An error occurred.
FILES
/etc/user_attr
/etc/security/auth_attr
/etc/security/prof_attr
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
auths(1), pfexec(1), profiles(1), rlogin(1), su(1M), getauusernam(3BSM), auth_attr(4), passwd(4), prof_attr(4), shadow(4), user_attr(4),
attributes(5)
SunOS 5.10 14 Feb 2001 roles(1)