Re: [REQADM-Users-L] caching userinfo - disable-able?

[Matthew W. <mw...@tt...>]

thought I had it... now I don't.

This is the way I think userinfo is working, maybe I'm wrong.

REQADM gets a request from someone that doesn't exist in "usertable" or
"cdis" or the dbase

REQADM asks the LDAP server about this person, LDAP returns a RUID

REQADM asks userinfod about this RUID, RUID returns the person's info

REQADM takes this info and stuffs it into the dbase

SO, if I want to change someone's information, I need to add that person
to the cdis file and make sure their modification date is later than
when the user was fist stuffed into the dbase.  Then after the nightly
cron script is run, that user's info will be update.

yes?  no?

-mtw

On Mon, Nov 01, 2004 at 02:12:21PM -0800, Matthew White (mw...@tt...) wrote:
> okay... this make sense now.
> 
> Taking bits out of the userinfo daemon and generating a cdis info file
> out of our LDAP database should be trivial.
> 
> Thanks for your work on this Steve. Reqadm is a really great program
> despite the somewhat byzantine back end.  I'm looking forward to the
> SQL-ized version!
> 
> -mtw
> 
> On Mon, Nov 01, 2004 at 02:06:27PM -0800, Steve Willoughby (st...@ic...) wrote:
> > On Mon, 1 Nov 2004, Matthew White wrote:
> > > okay, so after looking at the script and re-reading the documentation,
> > > having a userinfo daemon doesn't buy you much in terms of dynamic data.
> > > Seems to me I still need to populate the cdis file.  Is that correct?
> > 
> > The only real advantage to having the userinfo daemon is to dynamically
> > pull the info for a user who isn't in the REQADM database at all.  In
> > the environment where REQADM was born, it was typical for there to be
> > a set of many tens of thousands of potential users, but only about 2000
> > active common users, which REQADM really needed to track.  So when the odd
> > extra user showed up with a request ticket, REQADM would query the userinfo
> > service to get their profile on the fly and proceed.  It really isn't for
> > dynamic updates to existing users.
> > 
> > Which is one reason we're going away from that whole model now.  But in
> > the mean time, there's really no way to update user info for existing
> > people short of running reqadm-update-db (which you shouldn't do while
> > the daemon's running... see the reqadm-nightly script for how it puts
> > the reqadm server to sleep while running reqadm-update-db).
> > 
> > --steve
> > 
> 
> -- 
> Matthew White
> District Systems Administrator
> Tigard/Tualatin School District
> 503.431.4128
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by:
> Sybase ASE Linux Express Edition - download now for FREE
> LinuxWorld Reader's Choice Award Winner for best database on Linux.
> http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
> _______________________________________________
> Reqadm-users-l mailing list
> Req...@li...
> https://lists.sourceforge.net/lists/listinfo/reqadm-users-l

-- 
Matthew White
District Systems Administrator
Tigard/Tualatin School District
503.431.4128