(no subject)
Mar. 10th, 2006 12:40 am![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
ihateemo.livejournal.com posting in ![[community profile]](https://www.dreamwidth.org/img/silk/identity/community.png){kind=small}
techrecoveryI don't know if it's the same at where any of you work, but there is a constant turf battle going on at my place of work. You'd think that having a bunch of Unix admin geeks working in one office and a bunch of Cisco network geeks in another would lead to some kind of well-oiled machine with geeks working hand in hand to make things work.
Well, you'd be wrong. My place of work is more like something out of The Warriors, with the two gangs consistently tearing strips off each other (verbally and textually D:).
Let's say the admins have a developer box running in the server room. Now, let's say that it's running slow. Do you:
a) Make sure that nobody is performing any tasks that would increase load on the box to the point where you're going to see lag
or
b) Declare loudly in public IRC that the problem is clearly network related and fix your shit, goddammit.
It's a never ending battle.
Edit: Uhhh, when I say public IRC I mean on our own public channel on an internal server - basically, the channel that ALL employees are part of (including top brass...CTO, CEO, etc. etc.). Then there are seperate channels for different things...
Not "public" public. :)
Aside: I tried to post this as a response to a comment - but I kept getting an error! LJ SYSADMINS FIX THY SHIT PLZ
Well, you'd be wrong. My place of work is more like something out of The Warriors, with the two gangs consistently tearing strips off each other (verbally and textually D:).
Let's say the admins have a developer box running in the server room. Now, let's say that it's running slow. Do you:
a) Make sure that nobody is performing any tasks that would increase load on the box to the point where you're going to see lag
or
b) Declare loudly in public IRC that the problem is clearly network related and fix your shit, goddammit.
It's a never ending battle.
Edit: Uhhh, when I say public IRC I mean on our own public channel on an internal server - basically, the channel that ALL employees are part of (including top brass...CTO, CEO, etc. etc.). Then there are seperate channels for different things...
Not "public" public. :)
Aside: I tried to post this as a response to a comment - but I kept getting an error! LJ SYSADMINS FIX THY SHIT PLZ
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
no subject
Date: 2006-03-10 06:53 am (UTC)no subject
Date: 2006-03-10 07:49 am (UTC)no subject
Date: 2006-03-10 08:10 am (UTC)no subject
Date: 2006-03-10 09:46 am (UTC)no subject
Date: 2006-03-10 06:01 pm (UTC)1. Unlike most rational organizations, here the Systems folks run the DHCP servers.
2. We need a new syslog box for logging from network devices, and my boss is talking about having them run THAT, too.
3. When we get pulled into a multi-team firefighting call, we either
(a) stand around waiting for somebody to come up with a symptom that's actually network-related, or
(b) plug in a sniffer and tell them which of their machines is misbehaving.