Welcome to Cool Solutions Community

We all should know that the BASH history is persistent, being stored in a file. Let's then make sure we optimize what we store.

For a while now I have wanted to see how many controls eDirectory really could handle, even if they were not supported. It should be mentioned loudly and clearly that as of eDirectory 8.8.5 some of these controls work but THEY ARE NOT SUPPORTED so if they do not work properly submit a bug or an enhancement but don't expect a quick response. Also for some of these there are definite limitations with how they work. I'll try to cover those as I go.

How fast can logins happen from a single client? How can I generate events for auditing for testing purposes? How much load can a single client put on eDirectory? Find out all that and more with one quick script: ldapbind.pl

Thursday, July 16, 2009 - Already an M+Archive user or looking for more info? Get up close and technical with our M+Archive Product Management team and be the first to find out how M+Archive 2009.1 introduces new features to mitigate email risk and ensure system interoperability. Find out more.

We couldn't wait any longer to begin this series and unanimously decided to make the purpose of this first episode two fold. We certainly had to announce the beginning of the series and then we felt we just had to start with a brief introduction to the workflow.

I was looking for a way to monitor the health of my NetWare volume mirrors in our host monitoring solution and was surprised to discover that such a seemingly simple task ended up being such a challenge. Here's a solution.

Last week I was asked if there was a way to start an application at the command line and later come back to it from somewhere else. Normally in Linux/Unix (*nix) it is possible to 'background' a process and then return to it later on but that's only if you are still in the same session where the process was sent to the background. This is useful to have something run while you do other things but reconnecting to this session cannot be done with just the shell. Thankfully 'screen' is on Linux systems by default (all of them I've used anyway) and as a result, Linux Just Does That.

As I continued working through the process of deploying a new set of drivers, I found even more errors than I had covered in the first three articles, so here comes part 4 of a continuing series.

All your favorite forms, one great new look and feel.

If you thought the Teaming 1 instructions were helpful, just take a look at these. We've updated the instruction to fit the new features of Teaming 2