All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Sam Varshavchik <mrsam-W1w4QoW4mIDgLSHwZvcCBg@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Maximum number of file descriptors that may be passed via SCM_RIGHTS
Date: Wed, 14 Sep 2011 08:07:31 +0200	[thread overview]
Message-ID: <CAKgNAkjs2MfpNdT3CmBW4stdaTWoP=RoFRd8Cm6jkUPVCn8YCg@mail.gmail.com> (raw)
In-Reply-To: <cone.1306367829.726700.9970.500-eRFusrvvrKWtZOM0fQ182pBYcbvojoGw@public.gmane.org>

Hello Sam,

On Thu, May 26, 2011 at 1:57 AM, Sam Varshavchik <mrsam-W1w4QoW4mIDgLSHwZvcCBg@public.gmane.org> wrote:
> Anyone knows if the maximum number of file descriptors that can be passed
> via SCM_RIGHTS is documented anywhere?
>
> Up to at least 2.6.35, I could stuff as many as 255 file descriptors. Which
> sort of made sense.
>
> I updated to Fedora 15, which is based on 2.6.38, and the maximum number of
> file descriptors I can stuff into a message seems to be 253. With 254,
> strace tells me that the kernel refuses with EINVAL.

No info on this sorry. Let me know if you determine(d) the details.

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Author of "The Linux Programming Interface"; http://man7.org/tlpi/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-09-14  6:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-25 23:57 Maximum number of file descriptors that may be passed via SCM_RIGHTS Sam Varshavchik
     [not found] ` <cone.1306367829.726700.9970.500-eRFusrvvrKWtZOM0fQ182pBYcbvojoGw@public.gmane.org>
2011-09-14  6:07   ` Michael Kerrisk [this message]

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='CAKgNAkjs2MfpNdT3CmBW4stdaTWoP=RoFRd8Cm6jkUPVCn8YCg@mail.gmail.com' \
    --to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mrsam-W1w4QoW4mIDgLSHwZvcCBg@public.gmane.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 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.