On 1/3/08, William Siegrist <wsiegrist@apple.com> wrote:
The use of the hostname for MySQL's error log is coded into mysql
itself:
http://dev.mysql.com/doc/refman/5.0/en/error-log.html
Even if you had <original_host>.err left over on the other "cloned"
hosts, it shouldnt be a problem, since a <new_host>.err will be made
and used. And that same link shows the line to put in etc/my.cnf to
make it standard anyway.
FWIW, Mac OS Forge uses 1 installation of MacPorts for many XServes,
and we dont have problems. I'd really be interested to know which
ports are hostname-dependent.
With apologies, I didn't at the time (when I was installing some of my ports with the verbos option) make a note -- it was more of an afterthought, but in the verbose output of one my 180+ ports I made the past few days, I did see the hostname show up in the verbose output which made me wonder if this could be a problem such as if some ports were made which would depend on in some way the hostname. It may be that there is no problem at all. I'm glad to learn that Mac OS Forge has successfully cloned and implemented MacPorts systems for use with multiple machines.
Thanks,
T.M.
-Bill
On Jan 3, 2008, at 8:21 PM, Ryan Schmidt wrote:
> On Jan 3, 2008, at 22:13, paul beard wrote:
>
>> On Jan 3, 2008 6:22 PM, Ryan Schmidt wrote:
>>
>>> I wasn't aware that any ports tied themselves to the build system's
>>> hostname. That would be problematic as well if we started to
>>> distribute binaries of ports. Then again, I'm only familiar with a
>>> small minority of our ports collection.
>>>
>>> With which ports have you observed this problem?
>>
>> Aren't you the maintainer of the mysql port?
>
> Yes I am.
>
>> [/opt/local/var/db/mysql5]# ls
>> .turd_mysql5 ibdata1 test
>> ib_logfile0 localhost.err
>> white.paulbeard.org.err
>> ib_logfile1 mysql
>>
>> There may well be others but this one came to mind immediately.
>
> MySQL writes logfiles whose names contain the hostname, yes. The
> hostname is not, however, to the best of my knowledge, encoded into
> any files installed by the MySQL ports. There should be no problem
> installing MySQL on one system and running it on another. The two
> systems will merely use separate logfiles by default -- which is in
> fact probably a good thing, isn't it? If it isn't, there's probably
> a way to have MySQL write to a logfile of a name of your choosing.
> Consult the MySQL documentation.
>
>
> _______________________________________________
> macports-users mailing list
> macports-users@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-users
----
William Siegrist
Software Support Engineer
Mac OS Forge
http://macosforge.org/
wsiegrist@apple.com
408 862 7337
_______________________________________________
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo/macports-users