Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] Silence compilation warnings about setuid, setgid
- X-seq: zsh-workers 42998
- From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: Re: [PATCH] Silence compilation warnings about setuid, setgid
- Date: Wed, 13 Jun 2018 16:16:00 +0100
- Cms-type: 201P
- Dkim-filter: OpenDKIM Filter v2.11.0 mailout2.w1.samsung.com 20180613151609euoutp02600d38a1d897096f7dfe53f82dfe76fe~3wSZg1aMb1849418494euoutp02T
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1528902969; bh=/QVGPpygYBNMRSsL3XHFD4hZ86y6DVAObBkBkneCST0=; h=Date:From:To:Subject:In-Reply-To:References:From; b=GDI3pgzs9Yp9jn3wXdXI+NysmYOfwIl5aaywpdI9hWy0PHA9csc8qppmxv5kAYKac MijKIj/CMBN8xrJUHzzKAK02K81LJ1UVqQWlraEaFkulClTwZU7zGPZQyHw/jH/WXP Rs1FEFmsynqzpcanujcqZIS17YQ9T4a8CFzosJms=
- In-reply-to: <CAH+w=7Z5hNeLpoUkGDMnuk3PRF3BX7+z=EdHQHTVtj1pgasrAA@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- Organization: SCSC
- References: <CAKc7PVBWHsOhpC7mZcL4DA0ih=3yJF-HYe+We=r0q1oXA_s38g@mail.gmail.com> <CGME20180613115039epcas5p3f7e70bdce12919686a5dec9895782138@epcas5p3.samsung.com> <CAF6rxgmVA5KtcRoaVZi5P=6OtQdLPzHJowbBm+eyp0Zjea19Sg@mail.gmail.com> <20180613131021eucas1p263704fa9832375e6a49cf7f2077606dc~3ukj6hhqT1702017020eucas1p2W@eucas1p2.samsung.com> <CAH+w=7Z5hNeLpoUkGDMnuk3PRF3BX7+z=EdHQHTVtj1pgasrAA@mail.gmail.com>
On Wed, 13 Jun 2018 08:08:27 -0700
Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> IIRC there are some cases in which setgid/setuid fail silently, i.e.,
> without changing anything but without setting errno. The second calls
> are to double-check that the first one was not rogue in that way.
>
> This may have been isolated to a 1990s-era OS that is no longer at
> issue. Either way there's no particular reason to save and report
> errno from the first call.
Thanks, I'll change to a cast to void.
pws
Messages sorted by:
Reverse Date,
Date,
Thread,
Author