>Maybe it's time to start sharing the OPS number with everyone, they'll >change it after a while, but they'll get the idea after a few changes.
This probably wouldn't solve your problem because the OPS group isn't some higher up tech support (even though they are really treated that way), they are the server level support with networking issues tacked on. They spend their time monitoring church systems in addition to the BYU ones, and already have enough problems with people with think that because they can install Linux that they know infinitely better how the BYU system should be run. Maybe after spending a few months doing the actual setup and administration of the network, you would realize that they (OPS group/network engineers) don't have the time to speak with you unless you actually have a problem that they could change. I'm willing to bet that most of the time you have probably spoke with them nothing has changed, but they have explained why they can't change it to begin with. By the way the OPS group is expected to take a shotgun approach to knowledge about the system and to try NOT to pass things on unless the absolutely have to (and then not over the phone). There are some people that have spent 3 or 4 years working there and still don't have everything down. They don't have the time to completely learn one thing (like most of you apparently do) and are given enough grief by the engineers when they don't know something. (And they already spend at least an extra hour or two a week in a lecture learning something new/what has changed). ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
