public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jnair at ensim dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/3353] New: ttyname's new strict dependency on /proc breaks chrooted applications Date: Thu, 12 Oct 2006 11:38:00 -0000 [thread overview] Message-ID: <20061012113826.3353.jnair@ensim.com> (raw) I am a FC6(test3) user. glibc version comes with the distro is 2.4.90-29. My application runs sshd daemon and logons users to their respective chrooted homes. Now /proc is not purposely made available in the chrooted env. sshd's login process (chrooted) calls ttyname. It fails as it does not find /proc mounted. This used to work with glibc-2.4-4 (on FC5) and before. Now this strict dependency breaks my application. Even simple command like `tty` fails in if /proc is not mounted. -- Summary: ttyname's new strict dependency on /proc breaks chrooted applications Product: glibc Version: 2.4 Status: NEW Severity: critical Priority: P1 Component: libc AssignedTo: drepper at redhat dot com ReportedBy: jnair at ensim dot com CC: glibc-bugs at sources dot redhat dot com,shekhar dot tiwatne at ensim dot com http://sourceware.org/bugzilla/show_bug.cgi?id=3353 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2006-10-12 11:38 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-12 11:38 jnair at ensim dot com [this message] 2006-10-12 20:57 ` [Bug libc/3353] " drepper at redhat dot com 2006-10-12 21:04 ` jakub at redhat dot com 2006-10-13 5:30 ` jnair at ensim dot com
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=20061012113826.3353.jnair@ensim.com \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).