Meaning you can have unlimited visitors and unlimited downloadable content from your site(s) at no additional cost. Enjoy consistent, blazing fast data with no limits. You can also secure Dedicated Transit speed to ensure your server gets the required speed 24/7/365. The fair use policy governs individuals who abuse this service, so you can be sure you’ll always have a fast, quality service.
When I asked the presenters about this, they grinned. “We’ve forgotten how to count small,” one of them said. In the end, my team’s proposal approximated the final example config presented by Google, so that was good. The math all worked out, but it still made my jaw drop. Final sol’n, BTW, used 101 machines. It took a long time to wrap my head around how everyone was thinking about this, but writing down the moving parts made it all a lot clearer. Sunday I spent the entire day at the Google SRE tutorial, which was very, very cool; a big part of it was an exercise to architect a system that would read and join logfiles.
Overwhelming response: Meh, they’ll never notice. OTOH, using more than one management tool is going to cause admin confusion or state flapping, and you don’t want to do that. I’ve thought about doing that, but assumed I’d be stealing precious CPU cycles from the science. There were a lot of people who ran configuration management (Cf3, Puppet, etc) on their compute nodes, which surprised me.
First up was a paper by Brent Kang et al. Third-hand, but: allegedly, as of last year, phishing is making more money than drug smuggling. OTOH, maybe that’s an indication of success of FOAF, since. After that came technical papers on spam. A cite would be really nice for that, but he didn’t have one. On Privilege Messaging (FIXME: Add link). Interesting to think of how that might indicate a failure of friend-of-a-friend. He also mentioned a recent paper (again, need cite) showing that spam coming from Gmail accounts (not forged, but real accounts) had rised from 1% at the start to 10%.
Many cool quotes, including: “TCP/IP runs over everything, including you if you’re not paying attention. Wednesday was opening day: the stats (1000+ attendees) and the awards (the Powershell devs got one for “bringing the power of automated system administration to Windows, where it previously largely unsupported”). ” Discussed the recent ITU talks a lot, and what exactly he’s worried about there. He went over a lot of things, but made it clear he was asking questions, not proposing answers. Then the keynote from Vint Cerf, co-designer of TCP and yeah. Grab the audio/watch the video.
A record that determines how the Apache software processes a specific type of file. By default, Apache only handles certain file types. You can configure Apache handlers for other file types with cPanel. For more information, read Apache’s handler documentation.
It’s frustrating for the sysadmins; you hope management knows what they’re doing. They know that vendors hate long burn-in periods, because there’s a bunch of expensive shiny that you haven’t been paid for yet getting banged around. User pressure is one part; they want it now. So management will use this as a bargaining chip in the bidding process: we’ll cut down burn-in if you’ll give us something else. But the other part is management.
Which meant that she was the sysadmin, too. During the break I talked to a woman who was attending the conference for free, in return for volunteering at the USENIX desk. She has computer experience but no sysadmin experience, so she came here to learn. I sold her on joining LOPSA by talking about how much the mailing lists had helped me. She ran her own business, and with the economy tanking she’d had to lay off everyone but herself.
His focus was on getting things done with Cfengine 3: start small and expand the scope as you learn more. And then it was tutorial time: Cfengine 3 all day. I’d really been looking forward to this, and it was pretty darn good. (Note to myself: fill out the tutorial evaluation form. ) Mark Burgess his own bad self was the instructor.
Funny stories aside (and they were funny; I recommend listening to the talk), the point was the danger of assuming too much from initial observations — we schedule X, so we must produce X; it looks like a wall, so it must be impervious. Data is observations, numbers with context — not hearsay, or conclusions, or numbers without context. Again, listen to the talk; it’s worth your time.
He covered a lot of material, starting with how filesystems worked and ending with deep juju using debugfs. The afternoon was “Recovering from Linux Hard Drive Disasters” with Ted T’so, and this was pretty amazing. If you ever get the chance to take this course, I highly recommend it.
Partly for the experience, partly because they weren’t happy with the way the vendor was doing it (“learning as they went along” was how they described it). They told me about assembling most of it from scratch. I urged them to think about presenting at LISA, and was surprised that they hadn’t heard of the conference or considered writing up their efforts.