Re: Master MySQL server rdist db to public MySQL servers

2002-09-09 Thread Mark Hennessy
PROTECTED] > Subject: Re: Master MySQL server rdist db to public MySQL servers > > On Fri, Sep 06, 2002 at 04:25:42PM -0400, Mark Hennessy wrote: > > > > Is there any way to just force the MySQL server to reload from the > > table data on disk? The recipient server

Re: Master MySQL server rdist db to public MySQL servers

2002-09-07 Thread Jeremy Zawodny
On Fri, Sep 06, 2002 at 04:29:24PM -0400, Mark Hennessy wrote: > > I don't want to use replication as IIRC it would require that the > sending MySQL server be listening externally. Why not setup an SSH tunnel, since you're planning to use SSH anyway. Then you can use MySQL's native replication.

Re: Master MySQL server rdist db to public MySQL servers

2002-09-07 Thread Jeremy Zawodny
On Fri, Sep 06, 2002 at 04:25:42PM -0400, Mark Hennessy wrote: > > Is there any way to just force the MySQL server to reload from the > table data on disk? The recipient servers are read-only, and the > sending server has a relatively infrequent rate of change, but just > enough that it's importa

Re: Master MySQL server rdist db to public MySQL servers

2002-09-06 Thread Gerald Clark
gt; >>Cc: [EMAIL PROTECTED] >>Subject: Re: Master MySQL server rdist db to public MySQL servers >> >>Just shut down all the servers before copying the files. >> >>Check out live replication. >>It may be a better solution. >> >>Mark Hennessy wrote

RE: Master MySQL server rdist db to public MySQL servers

2002-09-06 Thread Mark Hennessy
rom: Jeremy Tinley <[EMAIL PROTECTED]> > To: 'Mark Hennessy' <[EMAIL PROTECTED]> > Subject: RE: Master MySQL server rdist db to public MySQL servers > > Use replication then. It's the best way of ensuring you have the most > current data. > > -J > >

RE: Master MySQL server rdist db to public MySQL servers

2002-09-06 Thread Mark Hennessy
age- > From: Mark Hennessy [mailto:[EMAIL PROTECTED]] > Sent: Friday, September 06, 2002 3:05 PM > To: Gerald Clark > Cc: [EMAIL PROTECTED] > Subject: Re: Master MySQL server rdist db to public MySQL servers > > Shutting down the servers is not an option unfortunately, i

Re: Master MySQL server rdist db to public MySQL servers

2002-09-06 Thread Mark Hennessy
Clark wrote: > Date: Fri, 06 Sep 2002 15:15:30 -0500 > From: Gerald Clark <[EMAIL PROTECTED]> > To: Mark Hennessy <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: Master MySQL server rdist db to public MySQL servers > > Just shut down all the servers be

Re: Master MySQL server rdist db to public MySQL servers

2002-09-06 Thread Gerald Clark
Just shut down all the servers before copying the files. Check out live replication. It may be a better solution. Mark Hennessy wrote: >I have a Master MySQL server which does not listen publicly, and it >distributes a database to my publicly accessible MySQL servers via >rdist/ssh every 15 min

Master MySQL server rdist db to public MySQL servers

2002-09-06 Thread Mark Hennessy
I have a Master MySQL server which does not listen publicly, and it distributes a database to my publicly accessible MySQL servers via rdist/ssh every 15 mins or so by copying the table files. Is there any flushing that has to be done for the newly rdist'd files to be used by the public MySQL ser