These are my links for 28 mar 2014 through 29 mar 2014:
LDAP org chart | bitcube.co.uk – For centralised authentication and authorisation, LDAP is the de-facto standard. Whether in its pure form on Unix or in Active Directory guise on Windows, everyone uses it. What many people don't realise is that you can store all sorts of useful (and not so useful) information in LDAP. One field which can be useful is the "manager" attribute. One of our customers use that and so we've written a small script to graph it using the excellent Graphviz tool. It will probably need customising for specific cases, however we hope that people find it useful nonetheless. If you want to alter the output, do have a look at the record format documentation.
Puppet errors explained | bitcube.co.uk – Puppet is a wonderful system automation tool, however the learning curve can be a little steep. We've collected some of the errors messages and "strange" behaviour you may come across together with explanations to help overcome these hurdles and boost adoption of this fabulous tool. If you have any useful errors and explanations, please do send them in and we'll update this article.
DNS Load Balancing and Using Multiple Load Balancers in the Cloud – [...] Load balancing in general is a complicated process, but there's some secret sauce in managing DNS along with multiple load balancers in the cloud. It requires that you draw from a few different sets of networking and “cloudy” concepts. In this second article in my best practices series (my first post covered how to use credentials within RightScale for storing sensitive or frequently used values), I'll explain how to set up load balancers to build a fault-tolerant, highly available web application in the cloud. Here's what you’ll need: Multiple A records for a host name in the DNS service of your choice Multiple load balancers to protect against failure [...]
gdnsd – gdnsd is an Authoritative-only DNS server which does geographic (or other sorts of) balancing, redirection, weighting, and service-state-conscious failover at the DNS layer. gdnsd is written in C using libev and pthreads with a focus on high performance, low latency service. It does not offer any form of caching or recursive service, and notably does not support DNSSEC. There's a strong focus on making the code efficient, lean, and resilient. The code has a decent regression testsuite with full branch coverage on the core packet parsing and generation code, and some scripted QA tools for e.g. valgrind validation, clang-analyzer, etc. The geographically-aware features also support the emerging EDNS Client Subnet draft for receiving more-precise network location information from intermediate shared caches.
These are my links for 3 mar 2014 through 4 mar 2014:
Centos yum 404 repository errors | Natural Order Development – [...] Basically yum ran through every single mirror and got nothing but 404 errors. I thought something might have gotten broken with yum or maybe the entire Internet changed overnight to a new repository layout (not likely but it has happened before). Well a simple Google for yum 404 led to some message threads that basically said yum's caches were out of data [...]
Avoiding reboot: Resetting USB on a Linux machine – Every now and then, some USB device misbehaves badly enough to knock out the entire interface, to the extent that the system doesn’t detect any new USB devices. Or work so well with the existing ones, for that matter. The solution for me until now was to reboot the computer. But hey, I don’t like rebooting Linux!
Filtering Apache logs / conditional Logging – This can be very troublesome when trying to access certain web pages. The only way to get through is to make use of conditional logging (it is not the only way to control the contents of the logs) To do this, simply define an environment variable ,according to certain criteria, then request that the server does not write the file type within log when this variable exists
TestSSLServer – TestSSLServer is a simple command-line tool which contacts a SSL/TLS server (name and port are given as parameters) and obtains some information from it: Supported versions (among SSL 2.0, SSL 3.0, TLS 1.0, TLS 1.1 and TLS 1.2). Support of Deflate compression (TLS-level compression, not HTTP-level gzip/deflate compression, which this tool does not consider). Supported cipher suites, for each protocol version. Server certificate hash and name.
These are my links for 24 ott 2013 through 13 nov 2013: