public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jw203198 at hotmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/1936] Improvement to rcmd Date: Mon, 28 Nov 2005 11:00:00 -0000 [thread overview] Message-ID: <20051128110014.14736.qmail@sourceware.org> (raw) In-Reply-To: <20051128105844.1936.jw203198@hotmail.com> ------- Additional Comments From jw203198 at hotmail dot com 2005-11-28 11:00 ------- Created an attachment (id=768) --> (http://sourceware.org/bugzilla/attachment.cgi?id=768&action=view) Patch to randomize initial rcmd port by process id. Please ignore the waffling comments in the patch. Just me thinking with my two typing fingers. -- http://sourceware.org/bugzilla/show_bug.cgi?id=1936 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2005-11-28 11:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-11-28 10:58 [Bug libc/1936] New: " jw203198 at hotmail dot com 2005-11-28 11:00 ` jw203198 at hotmail dot com [this message] [not found] <20051128105844.1936.sourceware@zacglen.com.au> 2006-04-23 18:26 ` [Bug libc/1936] " drepper at redhat dot com 2006-04-23 23:22 ` sourceware at zacglen dot com dot au
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=20051128110014.14736.qmail@sourceware.org \ --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).