LDAP: Attributes and Keeping Them Simple
A consensus exists among many writers about jargon. Throw a bunch of undefined words at a reader and he or she will soon fall asleep. In fact, put one term in a paragraph that the reader doesn't understand and a page or two later sleep will start to creep and the reader will lose interest.
So, in spite of the what many technical writers practice, I thought I might give you a break. You don't need to know everything about LDAP directory components or the construction of an address book to begin understanding the technology behind directories.
To a person who wants to find the name and email address of someone, he or she wants to do a simple search to find it. Does that person need to know how the information got into the directory? Do they need to understand how the directory came into being? Think about that.
In Gerald Carter's book, "LDAP Administration", he addresses attributes in a way I find intimidating. Here's a little quote for you:
Attributes types and the associated syntax rules are similar to variables and data type declarations found in many programming languages. The comparison is not that big a stretch.
OK then. How about another way of discussing it. Attributes hold information you need in a directory. For example, they might contain someone's name, address, telephone numbers, employee numbers, the department in which he or she work, his or her job title, etc.
Many other attributes exist in directories and LDAP administrators organize those attributes using something we will discuss in the next installment.
So, get ready for the next bit of jargon called objectClasses. You should find that subject pretty interesting if I can manage to write about it without putting you into an altered state.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Stunnel Security for Oracle
- SourceClear Open
- SUSE LLC's SUSE Manager
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- My +1 Sword of Productivity
- Managing Linux Using Puppet
- Tech Tip: Really Simple HTTP Server with Python
- Non-Linux FOSS: Caffeine!
- Google's SwiftShader Released
- Doing for User Space What We Did for Kernel Space
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide