Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 14 Feb 1998 13:31:59 -0600 (CST)
From:      Dannyman <dannyman@sasquatch.dannyland.org>
To:        FreeBSD-gnats-submit@FreeBSD.ORG
Cc:        dannyman@sasquatch.dannyland.org
Subject:   bin/5747: ld.so error message
Message-ID:  <199802141931.NAA09135@sasquatch.dannyland.org>

next in thread | raw e-mail | index | archive | help

>Number:         5747
>Category:       bin
>Synopsis:       ld.so error message
>Confidential:   yes
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Feb 14 16:10:01 PST 1998
>Last-Modified:
>Originator:     Dannyman
>Organization:
>Release:        FreeBSD 2.2.5-STABLE i386
>Environment:
>Description:

While a user was running a script for sending a large number of email
messages to his customers, the system ran across limits on the number of
files it could hold open;

Feb 13 18:23:11 sasquatch syslogd: /dev/console: Too many open files in
system: 
Too many open files in system
Feb 13 18:23:11 sasquatch syslogd: /var/run/utmp: Too many open files in
system
Feb 13 18:23:11 sasquatch syslogd: /var/run/utmp: Too many open files in
system
Feb 13 18:23:11 sasquatch /kernel: file: table is full
Feb 13 18:23:11 sasquatch syslogd: /var/run/utmp: Too many open files in
system
Feb 13 18:23:11 sasquatch last message repeated 3 times
Feb 13 18:23:11 sasquatch /kernel: file: table is full
Feb 13 18:23:11 sasquatch last message repeated 8 times

As a result, the user's script returned an error when opening a pipe to
sendmail;
ld.so failed: Can't find shared library "libutil.so.2.2"

After receiving a message from this user, I investigated the trouble and
figured out that it wasn't that libutil wasn't found, but more likely that it
could not be opened.

>How-To-Repeat:
>Fix:
	
I'm not sure how ld's algorithm pans out, but it may be more helpful if it
could return a more accurate error message under any condition where the
shared library is present, but can not be opened. Any competent sysadmin
should be able to second-guess such an error though by consulting
/var/log/messages, so I wouldn't worry too much. :)

You guys are great!

dannyman
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199802141931.NAA09135>