So, in other words... User Error.
I guess it makes sense why mysql would get grumpy if both mysqldump and
mysql were both attempting to read from stdin, /dev/tty or whatever at the
same time. I had [incorrectly] assumed that mysqldump would request input
first, then mysql would after mysqldump cl
Jason Sipula writes:
> This fixed bash. So it does appear MySQL is disabling echo.Strange that it
> does not re-enable it after it's finished running. I'll take this up with
> the mysql folks.
Most likely the second instance found the terminal already set to -echo
after the first instance has st
On 12 Jul 2013 01:29, "Chris Down" wrote:
> What does this have to do with bash? This is almost certainly an issue
with your terminal it MySQL client. What about this would constitute a bash
bug?
s/\bit\b/or/
On 12 Jul 2013 01:25, "Jason Sipula" wrote:
>
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gn
ed off
> > try typing
> > stty +echo
> > when you you say you don't see any output.
> > And if its turned off it was probably turned off my mysql.
> > *Gesendet:* Donnerstag, 11. Juli 2013 um 19:53 Uhr
> > *Von:* "Jason Sipula"
> > *An:* Ke
g, 11. Juli 2013 um 19:53 Uhr
> *Von:* "Jason Sipula"
> *An:* Kein Empfänger
> *Cc:* bug-bash@gnu.org
> *Betreff:* Re: Chained command prints password in Clear Text and
breaks
> BASH Session until logout
> I probably should have filed two different repor
You learn something new every day!
After your explanations, this situation makes perfect sense to me now. I
was attempting to quickly clone a database to basically rename it since
mysql removed the rename command a while ago (it was dangerous apparently).
It's pretty awesome that you guys took th
On Thu, Jul 11, 2013 at 10:53:11AM -0700, Jason Sipula wrote:
> The second issue is once the command terminates, bash session does not
> behave normally at all. Nothing typed into the terminal over SSH or
> directly on the console displays, however it does receive the keys. Also,
> if you repeatedl
:* bug-bash@gnu.org
> *Betreff:* Re: Chained command prints password in Clear Text and breaks
> BASH Session until logout
> I probably should have filed two different reports for this. Sorry for any
> confusion guys.
>
> The password makes sense to me why it allows clear text...
>
3 Uhr
Von: "Jason Sipula"
An: Kein Empfänger
Cc: bug-bash@gnu.org
Betreff: Re: Chained command prints password in Clear Text and breaks
BASH Session until logout
I probably should have filed two different reports for this. Sorry for
any
confusion guys.
The passw
On Thu, Jul 11, 2013 at 10:47:12AM -0700, Jason Sipula wrote:
> I still think this is a bash issue. After the command terminates, you must
> restart your bash session to return to normal functionality. Nothing typed
> into the terminal displays but it does receive it.
If the terminal has been mess
I probably should have filed two different reports for this. Sorry for any
confusion guys.
The password makes sense to me why it allows clear text...
The second issue is once the command terminates, bash session does not
behave normally at all. Nothing typed into the terminal over SSH or
directly
On Wed, Jul 10, 2013 at 02:54:17PM -0700, Jason Sipula wrote:
> ~]# mysqldump -u someuser -p somedb | mysql -u someuser -p -D someotherdb
This isn't a bash issue. Mysql is prompting for a password, either
on standard input or by directly opening /dev/tty. In either case,
the issue is with mysql.
13 matches
Mail list logo
