Program docs and dircat problem March 20, 2009
Posted by svenm in Administration.Tags: Dircat
trackback
We have created 3 Dircat program documents on two of our servers. One server is 8.0.1 and the other one is 6.5.1. Both servers run on linux.
The problem with these documents is that they don’t run… Well actually they do but for some reason we get an error indicating that the dircat process is already running. We’ve modified the command line on our first program document several times using -quit, -q, just q, … but it just won’t quit!
So what I’ve done is I’ve created 3 different scheduled agents in a notes database.
The first agent is called 1. Stop Dircat. It runs every day at 3:55 and all it does is the following:
Dim s As New notessession
Dim nnServer As New NotesName(s.CurrentDatabase.Server)
Dim consoleReturn$‘Send the console command
consoleReturn$ = s.SendConsoleCommand( nnServer.Common, “tell dircat quit” )
The second agent is called 2. Rebuild Dircat. It runs every day at 4:05 and all it does is the following:
Dim s As New notessession
Dim nnServer As New NotesName(s.CurrentDatabase.Server)
Dim consoleReturn$‘Send the console command
consoleReturn$ = s.SendConsoleCommand( s.common, “load dircat names.nsf -r” )
The second agent is called 3. Load Dircat. It runs every day at 4:15 and all it does is the following:
Dim s As New notessession
Dim nnServer As New NotesName(s.CurrentDatabase.Server)
Dim consoleReturn$‘Send the console command
consoleReturn$ = s.SendConsoleCommand( nnServer.Common, “load dircat” )
I’ve also set my agent security to 2. Allow Restricted operations.
This seems to do the trick. Before I created these agents I wasn’t aware of the SendConsoleCommand. I can already see a lot of other situations where I can use this function!
Update: here is a print-screen of the server document. This doesn’t seem to do the trick. The catalog is not updated as it should be:
Is there a reason you are trying to do this with program documents rather than the Server Tasks-Directory Cataloger tab on the server document? This will allow you to schedule all of your directory catalog updates.
Well we have enabled this but we started with a program document because the settings on the server document weren’t updating the directory catalog. Unfortunately the Program documents were no success and so we’ve ended up with the agents.
Do not use names.nsf as a dircat name! hopefully that is just there for screen shot benefit. Otherwise woe to you.
The process is fairly straight forward usually. I wonder if there is a Linux switch required, I am not very up on Linux peculiarities.
Dircat doesn’t shut down usually it just runs, but you do not need to run multiple versions, just set it up correctly and they will each populate and follow orders. Follow the admin help file.
Unless you need 3 different ones, why would you set up 3 tasks at all? it can be performance hits.
The screen shot is indeed a fake one because I removed the original nsf.
We run 2 different dircats on 2 different domains where one address book collects users from the other domain.
I never had this problem except for now. But I must admit it’s the first time that I work with Linux servers…