Mailinglist Archive: opensuse-bugs (7182 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=353120

User mmarek@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=353120#c15





--- Comment #15 from Michal Marek <mmarek@xxxxxxxxxx>  2008-01-23 03:19:08 MST 
---
(In reply to comment #14 from Richard Bos)
> Okay, so than we need to decide on which one to use.  Browsing there 
> respective
> manual pages:
> http://dev.mysql.com/doc/refman/5.1/en/mysqld-multi.html
> http://dev.mysql.com/doc/refman/5.1/en/instance-manager-configuration-files.html
>
> I seem to prefer the mysqld-multi.html.  It feels somehow more familair, than
> the manager one.  Is it okay to choose / use mysqld-multi?

OK, let's go for mysqld-multi then.


> > BTW, ./rcmysql2 stop seems to only shutdown the first instance.
>
> That's correct and on purpose.  I don't want to waste writing the stop (and
> the status) part of the code without knowing whether the start is okay or
> not.

I see, no problem.


> Is it possible to revert to a certain revision in the buildserver?  I don't
> remember if something like "osc co -r rXX" is possible.  But than again how
> would one know the what has changed, without real log messages...

Yes, the buildservice stores all revisions of the package sources and
recent osc has some support for it (e.g. osc co -rXX is possible).
It's also possible to attach a log message to a commit (osc ci -m ...),
but usually a note in the *.changes file is sufficient (and better IMO,
because it's visible in the package changelog).


I added you (your login is 'rbos', right?) to
server:database:mysql51/mysql, feel free to apply your changes there.
And don't worry about accidentally breaking this package. I'll watch
the changes and test/correct/argue as needed ;)


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.