On Wed, 7 Aug 2024 at 07:11, Vít Ondruch <vondr...@redhat.com> wrote:
> With new RPM, I hit the limit in two packages: > > https://koschei.fedoraproject.org/package/rubygem-abrt > > https://koschei.fedoraproject.org/package/rubygem-pg > > > I have read: > > > https://unix.stackexchange.com/questions/367008/why-is-socket-path-length-limited-to-a-hundred-chars > > > https://stackoverflow.com/questions/34829600/why-is-the-maximal-path-length-allowed-for-unix-sockets-on-linux-108 > > > But I still wonder why we should live with such limitation in 21st century. > > I would guess because a lot of existing code expects that limitation and is coded to use string functions which check and limit it to that. I guess you would need to basically create a new 'node' type and library calls that programs could switch to talk to these long socket names. [I expect that if we were to look at things that we would find that node names also need to be ASCII and UTF-8 names would also blow up a lot of programs] -- Stephen Smoogen, Red Hat Automotive Let us be kind to one another, for most of us are fighting a hard battle. -- Ian MacClaren
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
