Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Information about Unix System Administration Post 302303039 by pludi on Wednesday 1st of April 2009 05:03:07 PM
Old 04-01-2009
How many night shifts you're going to have depends IMO on your own ability and your company. Example: at our company we don't do any real night shifts, but only on-call (always three people), since we don't have a single point of failure. If an application has to be updated, only one of three servers for that job is (planned) down at the same time, so upgrades can be done during business hours.

As for the ability part: if you're really really good you can set up your systems in a way that they can handle anything but the most severe cases by themselves, even if it just means limping until normal office hours.

But in the end the decision is pretty simple: the deviation of your work hours from the usual is directly proportional to the deviation of complexity of your problems from the usual (read: the more complex the problems the higher the probability that they happen when you're not in the office)
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

System Administration

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

Need information about System V & Berkley Syntax for Unix

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

System Administration Certification

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

Alternative Scripting Language for UNIX/Linux System Administration

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?

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?

What are the career options in unix apart from unix system administration? (2 Replies)
Discussion started by: thulasidharan2k
2 Replies

7. Solaris

Various System Administration Questions

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

Learning project ideas - shell, python, UNIX tools, system administration

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?

How to start in System Administration?

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
FINGER(1)						    BSD General Commands Manual 						 FINGER(1)

NAME
finger -- user information lookup program SYNOPSIS
finger [-46glmpshoT] [user ...] [user@host ...] DESCRIPTION
The finger utility displays information about the system users. Options are: -4 Forces finger to use IPv4 addresses only. -6 Forces finger to use IPv6 addresses only. -s Display the user's login name, real name, terminal name and write status (as a ``*'' before the terminal name if write permission is denied), idle time, login time, and either office location and office phone number, or the remote host. If -o is given, the office location and office phone number is printed (the default). If -h is given, the remote host is printed instead. Idle time is in minutes if it is a single integer, hours and minutes if a ``:'' is present, or days if a ``d'' is present. If it is an ``*'', the login time indicates the time of last login. Login time is displayed as the day name if less than 6 days, else month, day; hours and minutes, unless more than six months ago, in which case the year is displayed rather than the hours and minutes. Unknown devices as well as nonexistent idle and login times are displayed as single asterisks. -h When used in conjunction with the -s option, the name of the remote host is displayed instead of the office location and office phone. -o When used in conjunction with the -s option, the office location and office phone information is displayed instead of the name of the remote host. -g This option restricts the gecos output to only the users' real name. It also has the side-effect of restricting the output of the remote host when used in conjunction with the -h option. -l Produce a multi-line format displaying all of the information described for the -s option as well as the user's home directory, home phone number, login shell, mail status, and the contents of the files .forward, .plan, .project and .pubkey from the user's home directory. If idle time is at least a minute and less than a day, it is presented in the form ``hh:mm''. Idle times greater than a day are pre- sented as ``d day[s]hh:mm''. Phone numbers specified as eleven digits are printed as ``+N-NNN-NNN-NNNN''. Numbers specified as ten or seven digits are printed as the appropriate subset of that string. Numbers specified as five digits are printed as ``xN-NNNN''. Numbers specified as four dig- its are printed as ``xNNNN''. If write permission is denied to the device, the phrase ``(messages off)'' is appended to the line containing the device name. One entry per user is displayed with the -l option; if a user is logged on multiple times, terminal information is repeated once per login. Mail status is shown as ``No Mail.'' if there is no mail at all, ``Mail last read DDD MMM ## HH:MM YYYY (TZ)'' if the person has looked at their mailbox since new mail arriving, or ``New mail received ...'', ``Unread since ...'' if they have new mail. -p Prevent the -l option of finger from displaying the contents of the .forward, .plan, .project and .pubkey files. -m Prevent matching of user names. User is usually a login name; however, matching will also be done on the users' real names, unless the -m option is supplied. All name matching performed by finger is case insensitive. -T Disable the piggybacking of data on the initial connection request. This option is needed to finger hosts with a broken TCP imple- mentation. If no options are specified, finger defaults to the -l style output if operands are provided, otherwise to the -s style. Note that some fields may be missing, in either format, if information is not available for them. If no arguments are specified, finger will print an entry for each user currently logged into the system. The finger utility may be used to look up users on a remote machine. The format is to specify a user as ``user@host'', or ``@host'', where the default output format for the former is the -l style, and the default output format for the latter is the -s style. The -l option is the only option that may be passed to a remote machine. If the file .nofinger exists in the user's home directory, finger behaves as if the user in question does not exist. The optional finger.conf(5) configuration file can be used to specify aliases. Since finger is invoked by fingerd(8), aliases will work for both local and network queries. ENVIRONMENT
The finger utility utilizes the following environment variable, if it exists: FINGER This variable may be set with favored options to finger. FILES
/etc/finger.conf alias definition data base /var/log/lastlog last login data base SEE ALSO
chpass(1), w(1), who(1), finger.conf(5), fingerd(8) D. Zimmerman, The Finger User Information Protocol, RFC 1288, December, 1991. HISTORY
The finger command appeared in 3.0BSD. BUGS
The current FINGER protocol RFC requires that the client keep the connection fully open until the server closes. This prevents the use of the optimal three-packet T/TCP exchange. (Servers which depend on this requirement are bogus but have nonetheless been observed in the Internet at large.) BSD
July 22, 2002 BSD
All times are GMT -4. The time now is 01:23 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy