Am Donnerstag, den 04.05.2006, 01:22 +0200 schrieb Christian Hammers:
> 
> On 2006-05-04 Daniel Leidert wrote:
> > Am Donnerstag, den 04.05.2006, 00:55 +0200 schrieb Christian Hammers:
> > > tags 365433 - unreproducible moreinfo
> > > thanks
> > > 
> > > On 2006-05-04 Daniel Leidert wrote:
> > > > # cat /usr/share/mysql/mysql_fix_privilege_tables.sql | /usr/bin/mysql
> > > > --verbose --no-defaults --force --user=root --host=localhost
> > > > --database=mysql /usr/bin/mysql: unknown option '--no-defaults'
> > > 
> > > Ah, yes, --no-defaults must be the very first parameter so putting
> > > the --verbose after it fixes the problem!
> > 
> > It fixes the "unknown option" issue. But using the --no-defaults option
> > still results in the issue I described, that every start & restart of
> > mysqld produces this error. Without the --no-defaults option, everything
> > works and I guess, the password for root is read from ~root/.my.cnf. So
> > can I "deactivate" the usage of the --no-defaults option? Or did I miss
> > something (I read /usr/share/doc/mysql-server-5.0 without getting an
> > answer to this question).
> 
> The line in mysql_fix_privilege_tables is, as far as I figured out until
> now: cmd="$bindir/mysql --no-defaults --force --user=$user --host=$host"
> so user and password should be debian-sys-maint

No. This seems to be the problem: For me --user=root

You can see it in my boot.log I sent you at the beginning:

Got a failure from command:
cat /usr/share/mysql/mysql_fix_privilege_tables.sql | /usr/bin/mysql
--no-defaults --force --user=root --host=localhost --database=mysql
                      ^^^^^^^^^^^

> and the random string
> and heaven knows where the --verbose is coming from...

I added '--verbose' to get an info, why the command failed (as suggested
by the scrip itself) - I just added it in the wrong place.

> But I surely figure it out until I go to bed :)

Seems you are German too (.de TLD)? So it's time to go to bed :)

Greeting from Dresden,
Daniel



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to