Grouper Users - Open Discussion List

[Sebastien Gagne <>]

For full syncs (bulkSync) I would use the configuration in grouper-loader.properties : 

changeLog.psp.fullSync.quartzCron = 0 0 12,19 * * ?

Running a bulkSync can take much time (here it's about 10-15 minutes with minor changes)

As far as I know you could run with the -interval options, but in that case you won't know exactly when the sync runs, but it might also be useful if what you want is a periodic sync. There's also the overhead of having a second GSH running, but that's minor I guess. Running everything in the Grouper Daemon also checks if the FullSync is running before doing changelog sync; I don't think it does if you run it in two different process.

As for starting the Daemon, it's basically "bin/gsh -loader &"

here we made a start/stop script which stores the PID in a file to kill it when we need to stop it, but this is icing, last time I asked most people were simply executing the previous command and forgetting about it.

---
Sébastien Gagné, M.Ing., ing. jr
Analyste en informatique - Université de Montréal

On Thu, Mar 28, 2013 at 12:14 PM, Bryan E. Wooten <> wrote:

I see that I can start the Grouper Loader with ./gsh –loader. I have configured the grouper-loader.properties to run the PSP changelog consumer every so often:

changeLog.consumer.psp.quartzCron = 0 * * * * ?.

 

This has the same effect as running “loaderRunOneJob” at the gsh prompt. That is all good.

 

Then I find that I can get a similar effect by running  bin/gsh.sh -psp -bulkSync -interval 60, although that syncs everything not just what is in the change log.

 

I could also do this bin/gsh.sh -psp –sync stem:group -interval 60.

 

All of these start daemon processes. Why should I use one over the other? I also discovered that I can enter this:

./gsh –loader –psp –bulkSync –interval 60

 

Lastly can I run the psp commands from the gsh command prompt?

 

Any guidance on best practices for starting up these daemons will be appreciated.

 

Thanks,

 

Bryan