On Thu, 5 Jun 2003, Ben Johns wrote: > The manager will basically become redundant, so the chances are that the > user-manager side of things will be disabled.
Really? You haven't mentioned anything about a user interface - you only mentioned the repository, i.e. "a centralised user directory". What user interface to the LDAP repository were you planning to use? Does it do all the validation that the server-manager currently does? > It should be simple enough (once the update from LDAP script has been > written) to also update the configuration file via the same database. It should be, if you can work out when it has changed. > The polling/change notification is what kept me up last night =) Something > I still have to sit down and nut out I guess. As discussed, it's not such a simple problem. OTOH, you might consider keeping the server-manager, and extending it to store more configuration and user data, and extend "signal-event" so that it can notify other nodes in the network when interesting changes have just been made. As Les has suggested, you could also use LDAP as the primary repository of the configuration and account information, but I think you'll find that's a lot of work for not a lot of return. -- Charlie Brady [EMAIL PROTECTED] Lead Product Developer Network Server Solutions Group Mitel Networks Corporation http://www.mitel.com/smallbusiness Phone: +1 (613) 592 5660 or 592 2122 Fax: +1 (613) 592 1175 -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Searchable archive at http://www.mail-archive.com/devinfo%40lists.e-smith.org
