From: jsoe0708@tiscali.be
To: parisc-linux@parisc-linux.org
Cc: "Carlos O'Donell" <carlos@baldric.uwo.ca>,
"John David Anglin" <dave@hiauly1.hia.nrc.ca>,
"Randolph Chung" <randolph@tausq.org>
Subject: [parisc-linux] glibc or kernel problem?
Date: Thu, 9 Jan 2003 12:24:39 +0100 [thread overview]
Message-ID: <3E082C0A00001EC1@ocpmta4.freegates.net> (raw)
In-Reply-To: <3DED9BF500003DF9@ocpmta8.freegates.net>
Hello Carlos, Dave, Randolph, ...
>-- Original Message --
>From: jsoe0708@tiscali.be
>To: parisc-linux@parisc-linux.org
>Subject: [parisc-linux] squid-2.xx dpkg failled to fork on pl (follow up=
)
>Date: Thu, 2 Jan 2003 18:04:01 +0100
>
>
>Hi all,
>
>This small mail to mentionned that I reach to make squid operational on
>a linux-2.4.20-pa17 thanks to the following tips:
>
>in debian rules replace statement
> ac_cv_func_setresuid=3Dno \
>by
> ac_cv_func_setresuid=3Dyes \
>
>so that function leave_suid() [into src/tools.c] will use setresuid() in=
>place of seteuid() before launch fork().
>
>Is it a know problem on palinux?
>
I come back to you with this problem because it just supply a solution fo=
r
this problem and do not explain me the reason.
I do not reach to know if it is a problem with seteuid() (IIRC in glibc)
or a kernel problem.
I already try to get a coredump, but it seems that in this case (fork SEG=
V)
linux (SQUID FAQ) is not able to produce any coredump [what I unfortunalt=
ely
verify during numeruous test].
Is somebody have any better idea to help me to have a better idea of the
actula problem?
Thanks in advance,
Joel
********************************************
Promo Tiscali ADSL: 35 Euros/mois, 1er mois et activation =3D 0 Euro http=
://adsl.tiscali.be
prev parent reply other threads:[~2003-01-09 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-02 17:04 [parisc-linux] squid-2.xx dpkg failled to fork on pl (follow up) jsoe0708
2003-01-09 11:24 ` jsoe0708 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E082C0A00001EC1@ocpmta4.freegates.net \
--to=jsoe0708@tiscali.be \
--cc=carlos@baldric.uwo.ca \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@parisc-linux.org \
--cc=randolph@tausq.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.