I was wondering if there is a universal "trigger" system that I could use in 389 to for example let me know when a group gets a new member, or loses a member.
The admin guide
has only 9 entries for the word trigger. The USN plugin looked the most similar to what I want to do.
My aim is to be able to monitor for group modifications and email someone appropriate when the group membership changes. I was hoping this is something I can achieve without to much or any external programming as I would like it to be contained logically within 389.
I would appreciate any guidance on how to go about doing this and what other people have done. Do I need to write my own plugin?
In order to protect our email recipients, Betfair Group use SkyScan from
MessageLabs to scan all Incoming and Outgoing mail for viruses.
> Hi all,
> I compiled, built and installed the 389 DS 18.104.22.168 release.
> I tried to configure a mm scenario (by using my customized
administration application, which works with any 1.1.x release).
Have you successfully used it with any 1.2.x release?
> When I initialize the agreement, nothing happens and I do not see any
logs in errors, although I changed the error log level to 8192.
> My application creates the cn=changelog5, cn=config entry as well as
the cn=replica entry and the agreement cn=<agreement>,cn=replica entry
underneath the cn=<suffix>,cn=mapping tree, cn=config entry.
> Did the administration of replication (and agreements) change?
No - can you post excerpts from your access logs showing the operations
that add these entries, along with the results of those operations?
There is nothing in the error log showing any problems?