closing the report; please feel free to reopen and reassign it to the
appropriate pgsql package.
** Changed in: glibc (Ubuntu)
Assignee: (unassigned) => Matthias Klose
Status: Needs Info => Rejected
--
libc6 core-dumped
https://launchpad.net/bugs/76437
--
ubuntu-bugs mailing list
u
On 19/12/06, didier <[EMAIL PROTECTED]> wrote:
> > but, I friend checked this in debian with libc6 2.3 and he h
> I don't remember if POSIX defined a default line discipline but you shouldn't
> expect one.
>
ok
> > I was using psql. So, in the C code I wrote I'm doing anything with
> >signals,
> but, I friend checked this in debian with libc6 2.3 and he h
I don't remember if POSIX defined a default line discipline but you shouldn't
expect one.
> I was using psql. So, in the C code I wrote I'm doing anything with
>signals, do you say I have to write some extra lines when I want to
> ig
On 19/12/06, didier <[EMAIL PROTECTED]> wrote:
> Hi, thanks for your bug but I don't believe it's a glibc one. If the
> default line discipline for /dev/tty maps SIGQUIT signal to CTRL+\ it's
> the correct behavior.
>
but, I friend checked this in debian with libc6 2.3 and he hasn't
got the same
Hi, thanks for your bug but I don't believe it's a glibc one. If the
default line discipline for /dev/tty maps SIGQUIT signal to CTRL+\ it's
the correct behavior.
What postgresql tool do you use? If it's an interactive tool it should
catch or ignore these signals and this bug belong to it.
** C
