RE: reread config

Title: RE: reread config

Yes, that should go along with the reread.  It should read the files and act like the copies in memory are all that exist until the next reread is requested.

 

Ernie

 

-----Original Message-----
From: Chris Fowler [mailto:ChrisF@computone.com]
Sent: Monday, April 30, 2001 1:32 PM
To: 'Ernie Oporto'
Subject: RE: reread config

It seems that for some reason, conserver holds open the config file.  I would prefer that it be closed after reading.

Chris

-----Original Message-----
From: Ernie Oporto [mailto:Ernie.Oporto@viragelogic.com]
Sent: Monday, April 30, 2001 10:18 AM
To: users@conserver.com
Subject: RE: reread config

My recommendation for avoiding the shifting of consoles in the middle of
being used is to have conserver refuse to add them for a config reread if it
detects that a change in the .cf file happens in between existing consoles.

If the changes happen so that they can be tagged "on the end" of the list of
consoles without shifting everything around or disconnecting anything, that
would be better than no dynamic ability or a cold restart which makes the
changes take effect, but disconnects all.

Ernie

> -----Original Message-----
> From: users-admin@conserver.com [mailto:users-admin@conserver.com]On
> Behalf Of Bryan Stansell
> Sent: Thursday, April 26, 2001 8:40 PM
> To: users@conserver.com
> Subject: Re: reread config
>
>
> Quoting Doug Hughes <doug@gblx.net>:
> > well, I don't really have time to do a significant amont of work on it
> > right now, and it seems like that is what would be required. However,
> > I
> > will noodle on it for a while. Back burner on slow simmer.
> > conserver consomme.
>
> Cool.  That's what I've been doing for a few years now...it's
> such a nasty
> problem to fix "right" that it seems to never go anywhere.  My
> final answer was
> to rewrite the whole thing so it could do stuff like reread the
> config file.
> Well, hopefully you're burner is on a little higher than mine (or more
> effecient or something).
>
> > The thing I really don't want is something that will drop all existing
> > connections. We've got all the consoles hanging off cisco async
> > boards requiring securid authentication, so dropping and restarting
> > all those connections would require a significant amount of manual
> > intervention. So, it's an interesting problem. I haven't really looked
> > at it in great depth. I was wondering if there might be a way to
> > lookup
> > entries as the cf is parsed, and only delete ones that weren't found
> > and deallocate or add new ones that were found.
>
> Ditto...I really want it to be dynamic and transparent to everything.
>
> Bryan
> _______________________________________________
> users mailing list
> users@conserver.com
> https://www.conserver.com/mailman/listinfo/users
>

_______________________________________________
users mailing list
users@conserver.com
https://www.conserver.com/mailman/listinfo/users