Sponsored Content
Full Discussion: Managing Geeks
The Lounge What is on Your Mind? Managing Geeks Post 302380868 by Corona688 on Wednesday 16th of December 2009 11:45:04 AM
Old 12-16-2009
I can't say I agree with that wholeheartedly, but I do agree with this:
Quote:
Most IT pros support an organization that is not involved with IT. The primary task of any IT group is to teach people how to work. That's may sound authoritarian, but it's not. IT's job at the most fundamental level is to build, maintain and improve frameworks within which to accomplish tasks. You may not view a Web server as a framework to accomplish tasks, but it does automate the processes of advertising, sales, informing and entertaining, all of which would otherwise be done in other ways. IT groups literally teach and reteach the world how to work. That's the job.

When you understand the mission of IT, it isn't hard to see why co-workers and supervisors are judged severely according to their abilities to contribute to that process. If someone has to constantly be taught Computers 101 every time a new problem presents itself, he can't contribute in the most fundamental way. It is one thing to deal with that from a co-worker, but quite another if the people who represent IT to the organization at large aren't cognizant of how the technology works, can't communicate it in the manner the IT group needs it communicated, can't maintain consistency, take credit for the work of the group members, etc. This creates a huge morale problem for the group. Executives expect expert advice from the top IT person, but they have no way of knowing when they aren't getting it. Therein lies the problem.
As a minor example I'm often instructed to put folks into the senior staff group so they can access files senior staff has stored for them. But it is not necessary to give junior interns read-write access to the most deeply secured files on our intranet. If senior staff would just store less-restricted files in less-restricted folders(again, laid out to their specifications, and heavily documented down to immutable "read me" files in all base folders) this would be unnecessary. I'm continually put on the spot and must seem like a stuffy, paranoid jackbooted enforcer, but when I explain the extent of the damage that could be done by accident with needlessly broad access, my manger's always forced to agree.

It's of course not always like this. I'm happy to say they're gradually getting the idea. Still I clearly understand the sentiment... For IT's systems to operate correctly, and no matter how closely we try and model them to the users' needs, the acknowledgment and cooperation of both users and management is needed whether any of us like it or not.
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

managing users

I need to setup several accounts on a solaris system. (passwd,shadow,group) My question is : How can I create a group which can access a machine, but only in certain directories? (4 Replies)
Discussion started by: SmartJuniorUnix
4 Replies

2. UNIX for Advanced & Expert Users

best solution for managing many nameservers

Hello, i was searching around for good solution for managing many nameservers to add the records on the slave servers and update them and if possible some web-based manegment for non-experianced customers. anyone has an idea where can i find such solution? (1 Reply)
Discussion started by: Bashar
1 Replies

3. UNIX for Advanced & Expert Users

Managing nodes???

Does anyone know something about this? I have no idea what it means and how to do it. but if anyone can give me and explanation and also point me to a website, i'd really appreciate it (5 Replies)
Discussion started by: TRUEST
5 Replies

4. Programming

error in managing linklist

I have used link list in my program to operate on set of values the operations that i am doing : add , delete from link list when i am deleting the intermidiate or last value it is not giving any error but when i am deleting the 1 st value then program hangs can anyone suggest me the reason (3 Replies)
Discussion started by: bhakti_2025
3 Replies

5. Solaris

Managing FileSystems on Solaris

Hello. I have got Solaris 10 8/07 on x86 installed successfully using CDs. While I had inserted 1st CD - I created 2 new filesystems also. But now after entering into Solaris - How do I manipulate sizes or created/delete filesystems by going to terminal? Thank you! (15 Replies)
Discussion started by: panchpan
15 Replies

6. Solaris

Problems managing user

I installed Solaris 10 in an old Dell computer given to me. The filesystem is ZFS (Default). The problem is that after logging in as root (first login) I wanted to add a user : n2jkw. I added the user at /export/home/n2jkw BTW, /export/home is where the 150G extra Hard Drive is mounted to.... (20 Replies)
Discussion started by: n2jkw
20 Replies

7. UNIX for Dummies Questions & Answers

expr help - managing strings

Hi guys, I need to use regular expressions in linux and I'm not quite experience in that field, maybe someone could give me some help with it. Basically, I need to take a text like this. A234321=http://www.google..... a normal URL But, I need to take the string starting at... (0 Replies)
Discussion started by: ocramas
0 Replies

8. Programming

Managing and using PTSes

Hello. I need to simulate a few serial links (doing a simulation of an application for a robot) and found socat which, at least with minicom, is working flawlessly. I would really like to make pts static: ie same numbers between reboots, and automatic (not me opening terminals and leaving... (2 Replies)
Discussion started by: erupter
2 Replies
MH-ALIAS(5)                                                          [nmh-1.5]                                                         MH-ALIAS(5)

NAME
mh-alias - alias file for nmh message system SYNOPSIS
any nmh command DESCRIPTION
This describes both nmh personal alias files and the global alias file for nmh mail delivery, the file /etc/nmh/MailAliases It does not describe aliases files used by the message transport system. Each line of the alias file has the format: alias : address-group or alias ; address-group or < alias-file or ; comment where: address-group := address-list | < file | = UNIX-group | + UNIX-group | * address-list := address | address-list, address Continuation lines in alias files end with `' followed by the newline character. "Alias-file" and "file" are UNIX file names. UNIX-group is a group name (or number) from /etc/group. An address is a "simple" Inter- net-style address. Througout this file, case is ignored, except for file names. If the line starts with a `<', then the file named after the `<' is read for more alias definitions. The reading is done recursively, so a `<' may occur in the beginning of an alias file with the expected results. If the address-group starts with a `<', then the file named after the `<' is read and its contents are added to the address-list for the alias. If the address-group starts with an `=', then the file /etc/group is consulted for the UNIX-group named after the `='. Each login name occurring as a member of the group is added to the address-list for the alias. In contrast, if the address-group starts with a `+', then the file /etc/group is consulted to determine the group-id of the UNIX-group named after the `+'. Each login name occurring in the /etc/passwd file whose group-id is indicated by this group is added to the address-list for the alias. If the address-group is simply `*', then the file /etc/passwd is consulted and all login names with a userid greater than some magic number (usually 200) are added to the address-list for the alias. In match, a trailing "*" on an alias will match just about anything appropriate. (See example below.) An approximation of the way aliases are resolved at posting time is (it's not really done this way): 1) Build a list of all addresses from the message to be delivered, eliminating duplicate addresses. 2) If this draft originated on the local host, then for those addresses in the message that have no host specified, perform alias resolu- tion. 3) For each line in the alias file, compare "alias" against all of the existing addresses. If a match, remove the matched "alias" from the address list, and add each new address in the address-group to the address list if it is not already on the list. The alias itself is not usually output, rather the address-group that the alias maps to is output instead. If "alias" is terminated with a `;' instead of a `:', then both the "alias" and the address are output in the correct format. (This makes replies possible since nmh aliases and personal aliases are unknown to the mail transport system.) Since the alias file is read line by line, forward references work, but backward references are not recognized, thus, there is no recur- sion. Example Alias File: </etc/nmh/BBoardAliases sgroup: fred, fear, freida b-people: Blind List: bill, betty; fred: frated@UCI UNIX-committee: <unix.aliases staff: =staff wheels: +wheel everyone: * news.*: news The first line says that more aliases should immediately be read from the file /etc/nmh/BBoardAliases. Following this, "fred" is defined as an alias for "frated@UCI", and "sgroup" is defined as an alias for the three names "frated@UCI", "fear", and "freida". The alias "b-people" is a blind list which includes the addresses "bill" and "betty"; the message will be delieved to those addresses, but the message header will show only "Blind List: ;" (not the addresses). Next, the definition of "UNIX-committee" is given by reading the file unix.aliases in the users nmh directory, "staff" is defined as all users who are listed as members of the group "staff" in the /etc/group file, and "wheels" is defined as all users whose group-id in /etc/passwd is equivalent to the "wheel" group. Finally, "everyone" is defined as all users with a user-id in /etc/passwd greater than 200, and all aliases of the form "news.<anything>" are defined to be "news". The key thing to understand about aliasing in nmh is that aliases in nmh alias files are expanded into the headers of messages posted. This aliasing occurs first, at posting time, without the knowledge of the message transport system. In contrast, once the message trans- port system is given a message to deliver to a list of addresses, for each address that appears to be local, a system-wide alias file is consulted. These aliases are NOT expanded into the headers of messages delivered. HELPFUL HINTS
To use aliasing in nmh quickly, do the following: 1) In your .mh_profile, choose a name for your alias file, say "aliases", and add the line: Aliasfile: aliases 2) Create the file "aliases" in your nmh directory. 3) Start adding aliases to your "aliases" file as appropriate. FILES
/etc/nmh/MailAliases global nmh alias file PROFILE COMPONENTS
Aliasfile: For a default alias file SEE ALSO
ali(1), send(1), whom(1), group(5), passwd(5), conflict(8), post(8) CONTEXT
None BUGS
Although the forward-referencing semantics of mh-alias files prevent recursion, the "< alias-file" command may defeat this. Since the num- ber of file descriptors is finite (and very limited), such infinite recursion will terminate with a meaningless diagnostic when all the fds are used up. Forward references do not work correctly inside blind lists. MH.6.8 11 June 2012 MH-ALIAS(5)
All times are GMT -4. The time now is 08:09 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy