From: Luigi Gangitano <luigi@debian.org>
To: parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Issues with seteuid()?
Date: 12 Jan 2003 16:49:29 +0100 [thread overview]
Message-ID: <1042386569.3329.4.camel@luigi> (raw)
[-- Attachment #1: Type: text/plain, Size: 1023 bytes --]
Hi all,
I'm the Debian package maintainer for Squid (HTTP Proxy). I received the
forwarded bug report describing issues in seteuid() on palinux. While
using seteuid(), forked processes terminate with SEGV.
Is it a known problem?
Thanks.
L
Please CC: me, I'm not subscribed to this list.
-----Forwarded Message-----
> 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=no \
> by
> ac_cv_func_setresuid=yes \
>
> 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?
>
> Greetings,
> Joel
>
> PS: Luigi, I also test it on 2.5.1 and it works also for parisc linux (testing
> config). HTH
--
Luigi Gangitano -- <luigi@debian.org> -- <gangitano@lugroma3.org>
GPG: 1024D/924C0C26: 12F8 9C03 89D3 DB4A 9972 C24A F19B A618 924C 0C26
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-01-12 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 15:49 Luigi Gangitano [this message]
2003-01-13 3:06 ` [parisc-linux] Issues with seteuid()? Matthew Wilcox
2003-01-13 3:11 ` Randolph Chung
2003-01-29 17:01 ` Joel Soete
2003-01-30 7:03 ` Randolph Chung
2003-01-30 7:37 ` Joel Soete
2003-01-29 13:58 ` Joel Soete
-- strict thread matches above, loose matches on Subject: below --
2003-01-13 10:19 jsoe0708
[not found] <20030130073214.GJ20940@tausq.org>
[not found] ` <3E35C33F0000094B@ocpmta3.freegates.net>
2003-01-30 7:54 ` Randolph Chung
2003-01-30 8:28 ` Joel Soete
2003-01-30 13:03 ` Joel Soete
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=1042386569.3329.4.camel@luigi \
--to=luigi@debian.org \
--cc=parisc-linux@lists.parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox