From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 7364] New: monit doesn't start with glibc 2.19 because geteuid() fails
Date: Wed, 3 Sep 2014 17:09:44 +0000 (UTC) [thread overview]
Message-ID: <bug-7364-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=7364
Summary: monit doesn't start with glibc 2.19 because geteuid()
fails
Product: buildroot
Version: 2014.08
Platform: PC
OS/Version: Linux
Status: NEW
Severity: minor
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: syntheticpp at gmx.net
CC: buildroot at uclibc.org
Estimated Hours: 0.0
monit exits in src/env.c:
struct passwd *pw;
/* Get password struct */
if ( ! (pw= getpwuid(geteuid())) ) {
LogError("%s: You don't exist. Go away.\n", prog);
exit(1);
}
Only happens with glibc and eglibc 2.19 (tested with GCC 4.9.1), 2.18 is fine.
GCC warns while linking:
y.tab.c:(.text+0x379c): warning: Using 'getpwuid' in statically linked
applications requires at runtime the shared libraries from the glibc version
used for linking
Somehow libnss related?
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2014-09-03 17:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-03 17:09 bugzilla at busybox.net [this message]
2014-09-03 18:02 ` [Buildroot] [Bug 7364] monit doesn't start with glibc 2.19 because geteuid() fails bugzilla at busybox.net
2014-09-03 18:57 ` bugzilla at busybox.net
2014-09-04 12:22 ` bugzilla at busybox.net
2014-09-04 12:27 ` bugzilla at busybox.net
2014-09-04 15:52 ` bugzilla at busybox.net
2014-09-05 8:43 ` bugzilla at busybox.net
2014-09-05 8:44 ` bugzilla at busybox.net
2014-09-05 10:26 ` bugzilla at busybox.net
2014-09-05 10:27 ` [Buildroot] [Bug 7364] monit builds a static application, even though BR2_PREFER_STATIC_LIB is not set, and with glibc bugzilla at busybox.net
2014-09-05 10:30 ` bugzilla at busybox.net
2014-09-05 11:18 ` bugzilla at busybox.net
2014-09-05 12:38 ` bugzilla at busybox.net
2014-09-06 21:48 ` bugzilla at busybox.net
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=bug-7364-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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.