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

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

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