CURRENT branch and older OSes

The Doctor doctor at doctor.nl2k.ab.ca
Wed Nov 19 14:11:59 UTC 2008


On Wed, Nov 19, 2008 at 05:46:09AM -0700, The Doctor wrote:
> Hello, I just recalled something.
> 
> Bind identifiyg a problem in BSD?OS and fd.
> 
> In fact we had to lower a limit.
> 
> I wonder if this is the problem that is being sceen in potential 2.5 relesases.

Also noticed a pdman error.

Is this perl 5.8.8 friendly?

And for gmake test

./runtests TESTS

Running all tests listed in TESTS.  If any tests fail, run the failing
test program by hand to see more details.  The test program will have the
same name as the test set but with ".t" appended.

authprogs/ckpasswd......ok
authprogs/domain........ok
authprogs/ident.........MISSED 1-4 (exit status 1)
clients/getlist.........ok
innd/artparse...........FAILED 145, 150, 155, 160, 245, 250, 255, 260, 265, 270,
 275, 280
innd/chan...............ok
lib/asprintf............FAILED 7-8, 10-11
lib/buffer..............FAILED 79-85, 87-89
lib/concat..............ok
lib/conffile............ok
lib/confparse...........ok
lib/date................ok
lib/dispatch............ok
lib/getaddrinfo.........FAILED 72
lib/getnameinfo.........ok
lib/hash................ok
lib/hashtab.............ok
lib/hex.................ok
lib/hstrerror...........ok
lib/inet_aton...........ok
lib/inet_ntoa...........ok
lib/inet_ntop...........ok
lib/innconf.............ok
lib/list................ok
lib/md5.................ok
lib/memcmp..............ok
lib/messages............ok
lib/mkstemp.............ok
lib/network.............MISSED 1-117 (exit status 1)
lib/pread...............ok
lib/pwrite..............ok
lib/qio.................ok
lib/setenv..............ok
lib/snprintf............MISSED 6-513 (killed by signal 11)
lib/strerror............ok
lib/strlcat.............ok
lib/strlcpy.............ok
lib/tst.................ok
lib/uwildmat............ok
lib/vector..............ok
lib/wire................ok
lib/xmalloc.............FAILED 14-15, 22, 29, 36
lib/xwrite..............ok
nnrpd/auth-ext..........ok
overview/api............ok (skipped 6 tests)
overview/buffindexed....ok
overview/overchan.......ok
overview/tradindexed....ok
overview/xref...........ok
storage/archive.........ok
storage/makehistory.....ok
storage/sm..............FAILED 17-18
util/convdate...........ok
util/innbind............ok (skipped 10 tests)
util/inndf..............ok
util/innupgrade.........ok

Failed Set                 Fail/Total (%) Skip Stat  Failing Tests
-------------------------- -------------- ---- ----  ------------------------
authprogs/ident               4/4    100%    0    1  1-4
innd/artparse                12/360    3%    0    0  145, 150, 155, 160, ...
lib/asprintf                  4/12    33%    0    0  7-8, 10-11
lib/buffer                   10/89    11%    0    0  79-85, 87-89
lib/getaddrinfo               1/75     1%    0    0  72
lib/network                 117/117  100%    0    1  1-117
lib/snprintf                508/513   99%    0   --  6-513
lib/xmalloc                   5/36    14%    0    0  14-15, 22, 29, 36
storage/sm                    2/23     9%    0    0  17-18

Failed 663/2879 tests, 76.97% okay, 16 tests skipped.
Files=56,  Tests=2879,  32.52 seconds (0.74 usr + 2.44 sys = 3.18 CPU)
gmake[1]: *** [test] Error 1
gmake[1]: Leaving directory `/usr/source/inn-CURRENT-20081119/tests'
gmake: *** [test] Error 2                                             


FYI man man 2 bind gives me

BIND(2)                     BSD Programmer's Manual                    BIND(2)

NAME
     bind - bind a name to a socket

SYNOPSIS
     #include <sys/types.h>
     #include <sys/socket.h>

     int
     bind(int s, const struct sockaddr *name, socklen_t namelen);

DESCRIPTION
     Bind() assigns a name (address) to an unnamed socket.  When a socket is
     created with socket(2) it exists in a name space (address family) but has
     no name assigned.  Bind() requests that name be assigned to the socket.
     The namelen parameter specifies the size of name.

NOTES
     Binding a name in the LOCAL domain creates a socket in the file system
     that must be deleted by the caller when it is no longer needed (using
     unlink(2)).

     The rules used in name binding vary between communication domains.  Con-
     sult the manual entries in section 4 for detailed information.

RETURN VALUES
     If the bind is successful, a 0 value is returned.  A return value of -1
     indicates an error, which is further specified in the global errno.

ERRORS
     The bind() call will fail if:

     [EBADF]      S is not a valid descriptor.

     [ENOTSOCK]   S is not a socket.

     [EADDRNOTAVAIL]
                  The specified address is not available from the local ma-
                  chine.

     [EADDRINUSE]
                  The specified address is already in use.

     [EINVAL]     The socket is already bound to an address.

     [EACCES]     The requested address is protected, and the current user has
                  inadequate permission to access it.

     [EFAULT]     The name parameter is not in a valid part of the user ad-
                  dress space.

     The following errors are specific to binding names in the LOCAL domain. 
     indicates an error, which is further specified in the global errno.

ERRORS
     The bind() call will fail if:

     [EBADF]      S is not a valid descriptor.

     [ENOTSOCK]   S is not a socket.

     [EADDRNOTAVAIL]
                  The specified address is not available from the local ma-
                  chine.

     [EADDRINUSE]
                  The specified address is already in use.

     [EINVAL]     The socket is already bound to an address.

     [EACCES]     The requested address is protected, and the current user has
                  inadequate permission to access it.

     [EFAULT]     The name parameter is not in a valid part of the user ad-
                  dress space.

     The following errors are specific to binding names in the LOCAL domain.

     [ENOTDIR]    A component of the path prefix is not a directory.

     [EINVAL]     The pathname contains a character with the high-order bit
                  set.

     [ENAMETOOLONG]
                  A component of a pathname exceeded 255 characters, or an en-
                  tire path name exceeded 1023 characters.

     [ENOENT]     A prefix component of the path name does not exist.

     [ELOOP]      Too many symbolic links were encountered in translating the
                  pathname.

     [EIO]        An I/O error occurred while making the directory entry or
                  allocating the inode.

     [EROFS]      The name would reside on a read-only file system.

     [EISDIR]     An empty pathname was specified.

SEE ALSO
     connect(2),  listen(2),  socket(2),  getsockname(2)

HISTORY
     The bind function call appeared in 4.2BSD.

4.2 Berkeley Distribution        June 4, 1993 

Hope this helps.

-- 
Member - Liberal International	
This is doctor at nl2k.ab.ca	Ici doctor at nl2k.ab.ca
God, Queen and country! Beware Anti-Christ rising! 
Merry Christmas 2008  NOT 2o8 and Happy New Year 2009  NOT 2o9

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.




More information about the inn-workers mailing list