The request was to "Please, post a minimal, working example so we can play with it". What you posted is neither minimal (we shouldn't need get_config or a config file) nor working (get_config is missing. A sample config file is missing. IP_SOCKET is not defined. UNIX_SOCKET is not defined.)

The following works (can_read doesn't return) for me. Does it do the same for you? If so, your problem has nothing to do with the socket or select. 

use strict;
use warnings;

use IO::Socket;
use IO::Select;

my $sel = IO::Select->new();

my $address = "mysock";
unlink($address);
my $sock = IO::Socket::UNIX->new(
   Type   => SOCK_STREAM,
   Listen => 5,
   Local  => $address
) or die("Unable to create socket $!\n");
chmod 777, $address;
$sel->add($sock);

while(my @ready = $sel->can_read) {
   warn;
}

[download]

In reply to Re^3: Problems with IO::Select by ikegami
in thread Problems with IO::Select by dirtdart

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.