[AC-Admins] Trash talking servers / admins

[Harik A'ttar]

Inaki Tekalal wrote:
> Now as far as the trolls comment goes. Thats really directed at Harik mostly. I don't think ill of any of the other names you mentioned. The only two people I knew for sure had root were Harik and Simba. Simba, I don't really see you as a troll per say. Harik is a troll. This isn't meant as an insult but a statement of fact. He thrives on arguing and mockery. And I'm not sure I'd really want him to change. Sometimes its good to have someone around who's good at that ;>

Hey awesome I knew I was the troll in the OP.    About the 'root
access' on lion, though:

Last login: Tue Nov 13 22:34:26 2007 from 152.27.101.97.cfl.res.rr.com

The login before that isn't in the current logs, and I can't even find
when I last logged into the services host.

However, I'm more offended at the 'garbage' comment then anything -
especially considering how often other servers have bad switch
ports/move datacenters/etc.   Lion's uplink is delivered over a
switched ethernet WAN, which makes for an extremely stable loop
delivery.  The last 3 outages have been a massive link upgrade right
after Christmas, and two short and minor upstream router reboots.
Simba is working on adding in another high-capacity redundant link in
place of the current backup T1 to sprint.  That WILL require an IP
change of lion, although we will be running on both new and old for
some time.

Services may still have a minor memory leak which causes new
registrations to fail - however a services restart only shows up to
users if they are nicked out of a group when the restart happens - if
you're in group and +r, it considers you already identified.

I also laugh that you included glider in your uber network core:
"No response from .*, closing link"
squirrel.anthrochat.net: 17
husky.anthrochat.net: 32
otter.anthrochat.net: 66
glider.anthrochat.net: 1506
snowleopard.anthrochat.net: 1575
cheetah.anthrochat.net: 1822

This is a lion-centric view of all splits since December 10, 2003, and
I didn't bother trying to isolate when lion was down.  But you're
basically tied for 'second least available server'.

Please note that this includes linked servers reporting to global that
they cannot reach the server in question, not just lion reporting
unreachables.