n, Sep 10, 2012 at 9:43 AM, Polytropon wrote:
> On Mon, 10 Sep 2012 08:56:29 -0400, Pierre-Luc Drouin wrote:
> > On Tue, Sep 4, 2012 at 10:14 AM, Pierre-Luc Drouin >wrote:
> >
> > > Hi,
> > >
> > > so I have been having problems using portsnap lately. I
On Mon, 10 Sep 2012 08:56:29 -0400, Pierre-Luc Drouin wrote:
> On Tue, Sep 4, 2012 at 10:14 AM, Pierre-Luc Drouin wrote:
>
> > Hi,
> >
> > so I have been having problems using portsnap lately. I always get a "Bad
> > file descriptor" message when t
On Tue, Sep 4, 2012 at 10:14 AM, Pierre-Luc Drouin wrote:
> Hi,
>
> so I have been having problems using portsnap lately. I always get a "Bad
> file descriptor" message when trying using it on one of my i386 machine:
>
> Looking up portsnap5.freebsd.org mirrors... non
[ Pierre-Luc Drouin wrote on Tue 4.Sep'12 at 10:14:18 -0400 ]
> Hi,
>
> so I have been having problems using portsnap lately. I always get a "Bad
> file descriptor" message when trying using it on one of my i386 machine:
>
> Looking up portsnap5.freebsd.org
Hi,
so I have been having problems using portsnap lately. I always get a "Bad
file descriptor" message when trying using it on one of my i386 machine:
Looking up portsnap5.freebsd.org mirrors... none found.
Fetching snapshot tag from portsnap5.freebsd.org... done.
Fetching snapsho
The worker
> threads deal with client requests after the new client connection is
> pushed to queue.
>
> The logged error is :
> select() failed (Bad file descriptor) getdtablesize = 65536
>
> Sysctls at the moment are:
> kern.maxfiles: 65536
> kern.maxfiles
to queue.
The logged error is :
select() failed (Bad file descriptor) getdtablesize = 65536
Sysctls at the moment are:
kern.maxfiles: 65536
kern.maxfilesperproc: 65536
void client_accept(int listen_socket)
{
...
while ( loop )
{
FD_ZERO(&socket_set);
FD_SET(listen_so
On Friday 08 May 2009 23:23:32 Gary Gatten wrote:
> I just compiled and installed nTop 3.3.10 and now I'm getting this
> error. Had an older version running before this with no problem. I'm
> on 6.0 RELEASE. I'm still googling, any quick fixes would be GREATLY
> appreciated!
Shot in the dark: m
I just compiled and installed nTop 3.3.10 and now I'm getting this
error. Had an older version running before this with no problem. I'm
on 6.0 RELEASE. I'm still googling, any quick fixes would be GREATLY
appreciated! I've been debugging and compiling all day and want to
leave with this $hhh
On Tuesday 10 June 2008 07:37:56 anhnmncb wrote:
> Hi, list,
> Recently, I encounter a very annoying issue, when I try to
> mount an ext2fs filesystem in laptop disk, after mounted it without
> any errors, I can't access it, ls /mnt/da0s3 says "bad file
>
Hi, list,
Recently, I encounter a very annoying issue, when I try to
mount an ext2fs filesystem in laptop disk, after mounted it without any
errors, I can't access it, ls /mnt/da0s3 says "bad file
descriptor". In that disk, also has msdos and u
---
>
> Jun 8 13:17:04 stunnel: warning: can't get client address: Bad file
> descriptor
> Jun 8 13:17:34 last message repeated 530400 times
> Jun 8 13:18:00 last message repeated 488687 times
>
> snip ---
>
>
> here is the stunnel.log -
tart. Why is that happening? She the stunel logs below.
any clues?
snip ---
Jun 8 13:17:04 stunnel: warning: can't get client address: Bad file
descriptor
Jun 8 13:17:34 last message repeated 530400 times
Jun 8 13:18:00 last message repeated 488687 times
snip ---
-
Just upgraded stunnel and getting the following error message in the
/var/log/messages file. any clues?
snip ---
Jun 8 13:17:04 stunnel: warning: can't get client address: Bad file
descriptor
Jun 8 13:17:34 last message repeated 530400 times
Jun 8 13:18:00 last message rep
I installed linux_base-fc4 from Ports. When I use /compat/linux/bin/cp with
option -p, an error occurred.
For example, I type:
$ /compat/linux/bin/cp -p a b
This message is shown:
/compat/linux/bin/cp: preserving times for `b': Bad file descriptor
Does anyone know this?
T
Hi,
I get the following messages sometimes if i try to restart sshd:
#etc/rc.d/sshd restart
eval: Pipe call failed: Bad file descriptor
eval: Pipe call failed: Bad file descriptor
[...]
#/etc/rc.d/sshd restart
/etc/rc.subr: Pipe call failed: Too many open files in system
I am running 5.4
r open)
I have tried emailing other user accounts, and that works fine. I have tried
emailing root again, and I get exactly the same errors.
So, I checked /var/mail - here's the interesting thing.
# ls
root
# ls -a
. .. root
# ls -la
.
..
i.e. root's file does not show.
# touch r
Feb 10 08:07:45 xx syslogd: select: Bad file descriptor
FreeBSD 4.9-RELEASE-p1 i386
run as in a ttys wrapper script:
/usr/sbin/syslogd -4 -A -cc -n -s -d -f /etc/syslog.conf
the output of script/command is not redirected to /var/log but i
suspect it happens when newsyslog runs.
Has
I've just installed the ntop port, on a 4.8-STABLE system that has
two NICs. When I run ntop, it always gives me this error:
**ERROR** Reading packets on device 1(sis0): 'read: Bad file descriptor'
In this case sis0 is the second NIC listed. If I swap the order in the
-i option,
Hi,
1) First get the inode no of the file
ls -li #pico29506#
2) find . -inum -delete
Regards
SSR
From: Jaime <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: bad file descriptor
Date: Tue, 17 Jun 2003 09:06:10 -0400 (EDT)
Can anyone explain this? It looks like I can't del
In the last episode (Jun 17), Jaime said:
> On Tue, 17 Jun 2003, heikki soerum wrote:
> > > zeus# rm "#pico29506#"
> > > rm: #pico29506#: Bad file descriptor
> > > zeus# whoami
> > > root
> >
> > # is usually an special character, I us
On Tue, 17 Jun 2003, heikki soerum wrote:
> > zeus# rm "#pico29506#"
> > rm: #pico29506#: Bad file descriptor
> > zeus# whoami
> > root
>
> # is usually an special character, I usually delete such files with
> Midnight Commander (mc shell), another poss
ofileOctober 2002
Newsletter.doc public_html
.aspell.english.pws .qmail.backup.from.cyrusOctober 2002
Newsletter.doc.
.cshrc .rhosts acker
zeus# rm "#pico29506#"
rm: #pico29506#: Bad file descriptor
zeus# whoami
er 2002 Newsletter.doc.
> .cshrc .rhosts acker
> zeus# rm "#pico29506#"
> rm: #pico29506#: Bad file descriptor
> zeus# whoami
> root
# is usually an special character, I usually delete such files with
Midnight Commander (mc shell), another possi
2002
Newsletter.doc public_html
.aspell.english.pws .qmail.backup.from.cyrusOctober 2002
Newsletter.doc.
.cshrc .rhosts acker
zeus# rm "#pico29506#"
rm: #pico29506#: Bad file descriptor
ze
On Fri, 2002-11-01 at 11:48, Tuc wrote:
> Hi,
>
> Having a problem that we can't figure out. 2 different people
> installed machines, one is working fine, the other gives :
>
> Oct 31 00:07:34 lodur1 sendmail[47337]: File descriptors missing on startup: std
Hi,
Having a problem that we can't figure out. 2 different people
installed machines, one is working fine, the other gives :
Oct 31 00:07:34 lodur1 sendmail[47337]: File descriptors missing on startup: std
in, stderr; Bad file descriptor
constantlyCan't figu
On Friday, Sep 27, 2002, at 23:03 Australia/Brisbane, Dan Langille
wrote:
> I keep seeing this in /var/log/maillog but do not know the cause:
>
>sendmail[42390]: File descriptors missing on startup: stderr; Bad
> file descriptor
>
> I'm on FreeBSD 4.
On 27 Sep 2002 at 17:31, Matthew Seaman wrote:
> On Fri, Sep 27, 2002 at 09:03:28AM -0400, Dan Langille wrote:
> > I keep seeing this in /var/log/maillog but do not know the cause:
> >
> >sendmail[42390]: File descriptors missing on startup: stderr; Bad
> >
On Fri, Sep 27, 2002 at 09:03:28AM -0400, Dan Langille wrote:
> I keep seeing this in /var/log/maillog but do not know the cause:
>
>sendmail[42390]: File descriptors missing on startup: stderr; Bad
> file descriptor
>
> I'm on FreeBSD 4.6-STABLE #0:
I keep seeing this in /var/log/maillog but do not know the cause:
sendmail[42390]: File descriptors missing on startup: stderr; Bad
file descriptor
I'm on FreeBSD 4.6-STABLE #0: Thu Sep 26 09:02:16 EDT 2002 with
sendmail 8.12.5
Any ideas on cause/fix?
Thanks.
--
31 matches
Mail list logo
