Hi all, I would like to execute script after every update operation on specified subtree. I would like to know whether is there any best practice solution. I''ve found out I can write really simple post-operation plugin but before I start to do that I would like to know whether there is not any better solution I might be overlooking. I need to extract the configuration for ldap non-aware application and recreate it''s config file. Radek
Richard Megginson
2006-Sep-13 16:44 UTC
Re: [Fedora-directory-users] Script after update operation
Radek Hladik wrote:> Hi all, > I would like to execute script after every update operation on > specified subtree. I would like to know whether is there any best > practice solution. I''ve found out I can write really simple > post-operation plugin but before I start to do that I would like to > know whether there is not any better solution I might be overlooking. > I need to extract the configuration for ldap non-aware application > and recreate it''s config file.There are two other simpler ways that might work for you. 1) Use persistent search, possibly in combination with the Retro Changelog plugin. 2) Enable the audit log, and just tail -f audit | your script> > > Radek > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users
Radek Hladik
2006-Sep-13 19:03 UTC
Re: [Fedora-directory-users] Script after update operation
Richard Megginson napsal(a):> Radek Hladik wrote: >> Hi all, >> I would like to execute script after every update operation on >> specified subtree. I would like to know whether is there any best >> practice solution. I''ve found out I can write really simple >> post-operation plugin but before I start to do that I would like to >> know whether there is not any better solution I might be overlooking. >> I need to extract the configuration for ldap non-aware application >> and recreate it''s config file. > There are two other simpler ways that might work for you. > 1) Use persistent search, possibly in combination with the Retro > Changelog plugin. > 2) Enable the audit log, and just tail -f audit | your script >> >> >> Radek >> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users@redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-users > > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-usersWould you be so kind and point me to some more information about persistent searching? I can not find anything about it in FDS documentation, webpages and google returns only results about Novell eDirectory server. Is it FDS or LDAP extension? The solution with tail looks good but what about log rotation? Or would be FDS willing to log audit into named pipe? Radek
Mike Jackson
2006-Sep-13 19:16 UTC
Re: [Fedora-directory-users] Script after update operation
Radek Hladik wrote:> > Would you be so kind and point me to some more information about > persistent searching? I can not find anything about it in FDS > documentation, webpages and google returns only results about Novell > eDirectory server. Is it FDS or LDAP extension? > The solution with tail looks good but what about log rotation? Or would > be FDS willing to log audit into named pipe? > RadekPersistent search is an (expired) internet draft, which several LDAP server vendors implement, including FDS/RHDS. Persistent search is supported by the Net::LDAP API - http://ldap.perl.org. -- http://www.netauth.com - LDAP Directory Consulting
Richard Megginson
2006-Sep-13 20:04 UTC
Re: [Fedora-directory-users] Script after update operation
Radek Hladik wrote:> Richard Megginson napsal(a): >> Radek Hladik wrote: >>> Hi all, >>> I would like to execute script after every update operation on >>> specified subtree. I would like to know whether is there any best >>> practice solution. I''ve found out I can write really simple >>> post-operation plugin but before I start to do that I would like to >>> know whether there is not any better solution I might be overlooking. >>> I need to extract the configuration for ldap non-aware >>> application and recreate it''s config file. >> There are two other simpler ways that might work for you. >> 1) Use persistent search, possibly in combination with the Retro >> Changelog plugin. >> 2) Enable the audit log, and just tail -f audit | your script >>> >>> >>> Radek >>> >>> -- >>> Fedora-directory-users mailing list >>> Fedora-directory-users@redhat.com >>> https://www.redhat.com/mailman/listinfo/fedora-directory-users >> >> ------------------------------------------------------------------------ >> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users@redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-users > > Would you be so kind and point me to some more information about > persistent searching? I can not find anything about it in FDS > documentation, webpages and google returns only results about Novell > eDirectory server. Is it FDS or LDAP extension?cd /opt/fedora-ds/shared/bin ; ./ldapsearch -H The -C option does a persistent search - use especially with the -r option to avoid stdout buffering.> The solution with tail looks good but what about log rotation? Or > would be FDS willing to log audit into named pipe?Yes. You should first disable audit log rotation.> Radek > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users
Ulf Weltman
2006-Sep-13 20:07 UTC
Re: [Fedora-directory-users] Script after update operation
Radek Hladik wrote:> Richard Megginson napsal(a): > >> Radek Hladik wrote: >> >>> Hi all, >>> I would like to execute script after every update operation on >>> specified subtree. I would like to know whether is there any best >>> practice solution. I''ve found out I can write really simple >>> post-operation plugin but before I start to do that I would like to >>> know whether there is not any better solution I might be overlooking. >>> I need to extract the configuration for ldap non-aware >>> application and recreate it''s config file. >> >> There are two other simpler ways that might work for you. >> 1) Use persistent search, possibly in combination with the Retro >> Changelog plugin. >> 2) Enable the audit log, and just tail -f audit | your script >> >>> >>> >>> Radek >>> >>> -- >>> Fedora-directory-users mailing list >>> Fedora-directory-users@redhat.com >>> https://www.redhat.com/mailman/listinfo/fedora-directory-users >> >> >> ------------------------------------------------------------------------ >> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users@redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-users > > > Would you be so kind and point me to some more information about > persistent searching? I can not find anything about it in FDS > documentation, webpages and google returns only results about Novell > eDirectory server. Is it FDS or LDAP extension? > The solution with tail looks good but what about log rotation? Or > would be FDS willing to log audit into named pipe? > RadekAudit log can be written to a named pipe, just replace the real audit file with a fifo. You''ll still need to disable log rotation. Logging to a fifo has been a trick used in the past to capture the last few thousand lines of a high level of error logging with minimized performance impact, using a tool that provided a circular buffer in memory.
Radek Hladik
2006-Sep-13 21:16 UTC
Re: [Fedora-directory-users] Script after update operation
Richard Megginson napsal(a):> Radek Hladik wrote: >> Richard Megginson napsal(a): >>> Radek Hladik wrote: >>>> Hi all, >>>> I would like to execute script after every update operation on >>>> specified subtree. I would like to know whether is there any best >>>> practice solution. I''ve found out I can write really simple >>>> post-operation plugin but before I start to do that I would like to >>>> know whether there is not any better solution I might be overlooking. >>>> I need to extract the configuration for ldap non-aware >>>> application and recreate it''s config file. >>> There are two other simpler ways that might work for you. >>> 1) Use persistent search, possibly in combination with the Retro >>> Changelog plugin. >>> 2) Enable the audit log, and just tail -f audit | your script >>>> >>>> >>>> Radek >>>> >>>> -- >>>> Fedora-directory-users mailing list >>>> Fedora-directory-users@redhat.com >>>> https://www.redhat.com/mailman/listinfo/fedora-directory-users >>> >>> ------------------------------------------------------------------------ >>> >>> -- >>> Fedora-directory-users mailing list >>> Fedora-directory-users@redhat.com >>> https://www.redhat.com/mailman/listinfo/fedora-directory-users >> >> Would you be so kind and point me to some more information about >> persistent searching? I can not find anything about it in FDS >> documentation, webpages and google returns only results about Novell >> eDirectory server. Is it FDS or LDAP extension? > cd /opt/fedora-ds/shared/bin ; ./ldapsearch -H > The -C option does a persistent search - use especially with the -r > option to avoid stdout buffering. >> The solution with tail looks good but what about log rotation? Or >> would be FDS willing to log audit into named pipe? > Yes. You should first disable audit log rotation. >> Radek >> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users@redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-users > > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users@redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-usersThanks for pointing to ldapsearch utility as this not mentioned in documentation. I''ve searched "persistent" in all PDFs including ds71cli without success and I''ve even read through ldapsearch -H but didn''t realize that PS means Persistent Search :) I''ve put together few information about persistent searching and put it into Howto in wiki. Radek