similar to: More * weirdness

Hi all, could someone tell me what this does mean "bad file descriptor" when trying to start asterisk. It goes till the CLI command and then die with this message. Below an strace output from asterisk -vvvvvvvvvc It's on debian Sarge kernel 2.6.7 with packages from debian VoIP team. The server was running fine till now with this version. Thanks

From: Bradley Smith <brad at brad-smith.co.uk> This patch is from http://git.brad-smith.co.uk/?p=avr32/klibc.git;a=summary It squashes together and includes those commits: * Fix ld flags such that shared builds actually run. * Fix setjmp. * Fix sigaction/sigrestorer. * Tidy everything up. * Fix lseek mess. Cc: H?vard_Skinnemoen <hskinnemoen at gmail.com> Cc: Hans-Christian Egtvedt

Following example from usr/include/arch/i386/klibc/archsignal.h: The in-kernel headers for arm still have libc5 crap in them. Reconsider using <asm/signal.h> when/if it gets cleaned up; for now, duplicate the definitions here. Signed-off-by: Jon Ringle <jon at ringle.org> --- usr/include/arch/arm/klibc/archsignal.h | 112 ++++++++++++++++++++++++++++++- 1 files changed, 110

I''m working on the problem I''m having with the generator hanging on the server when the client side dies. This only happens when I''m connecting through stunnel. This is the strace output I''m getting, but I''m not sure how to interpret the output. Can anyone help? write(4, "2005/10/03 13:58:12 [16992] recv"..., 137) = 137 select(8, [7], [3],

The parts of klibc specific to the i386 architecture. Signed-off-by: H. Peter Anvin <hpa at zytor.com> --- commit bd0599e5290ca1a16bb7a68f7c362d395c612eb3 tree 8f33afdd02a14c22e7a3984da2bad13184e3f729 parent 84f6a72f42cf41e32daa59871a0b5424572093e4 author H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun 2006 16:58:21 -0700 committer H. Peter Anvin <hpa at zytor.com> Sun, 25 Jun

Hi all, i have the following configuration: RHAS 2.1 2.4.9-e.40enterprise #1 SMP (2 node cluster). ocfs-support-1.1.2-1 ocfs-tools-1.1.2-1 ocfs-2.4.9-e-enterprise-1.0.12-1 i followed the users guide to install and configure ocfs. During definition and formatting of ocfs-partitions the ocfstool crashed. Now restarting ocfstool fails with the following error: ocfstool Abnormal termination!

Commit-ID: 82da8480ac0d5df8dfcb051c1acd2099463f68d4 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=82da8480ac0d5df8dfcb051c1acd2099463f68d4 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 30 Apr 2020 13:31:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 17:33:29 +0100 [klibc] alpha: Set sa_restorer for

Commit-ID: 7f84d11885cf3e9298d53a2714800a8ac9c4dd74 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=7f84d11885cf3e9298d53a2714800a8ac9c4dd74 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 30 Apr 2020 13:31:32 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 20 Aug 2020 23:22:58 +0100 [klibc] alpha: Set sa_restorer for

Hello, we have two UPSes - one Galaxy and one from Socomec, both monitored by the NUT server. The NUT server runs the version 2.7.2. We have roughly 3500 clients running upsmon, reading the status of both UPSes. They run mainly the version 2.6.4 and some 2.7.2. We observed the following on both client versions, regardless whether we run upsmon in the daemon or debug mode: Running upsc socomec

Commit-ID: 570ed1e207cbe38ed487c722f8ac7db68e664a94 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=570ed1e207cbe38ed487c722f8ac7db68e664a94 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Sun, 23 Aug 2020 15:18:19 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 27 Aug 2020 15:00:33 +0100 [klibc] alpha: Pass restorer to

Commit-ID: ccc5c14c44f3fa76f61b8aae947cf3b853a6c833 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=ccc5c14c44f3fa76f61b8aae947cf3b853a6c833 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 25 Aug 2020 00:43:33 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 27 Aug 2020 15:00:33 +0100 [klibc] signal: Note another

Hi Dovecot peeps, I'm enjoying running /usr/lib/dovecot/imap directly as a PREAUTH IMAP pipe. I find that it outputs log messages whose severity is INFO to stdout. I'm running it as follows: /usr/lib/dovecot/imap -c /tmp/dovecot.conf and I see the following messages output to stdout: * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY

Hi, I don''t know whether this is a ruby, puppet, or facter bug. The whole issue is one of the "really weird" ones. I first noticed the problem when working with puppet on a train, without any internet connection. In such situation, two problems appear: 1) Mildly annoying, frequent 2-second pauses followed by: Timed out seeking value for ipaddress I think this is

Thank you Tzafrir. I had been using different users in earlier attempts to make this work. Decided to try everything where root is the only user, simply to verify it's working. For problem 2, where asterisk is writing to the log but doesn't seem to receive the SIP packets even though tcpdump indicates they are making it to the box on 5060, I am starting asterisk while logged in as root.

Hi, I have a problem with rsyncing large data sets (consisting bunch of small files) over ssh. rsync 2.6.6 on both sides. Linux 2.6.10 on receiving side, 2.6.12.6 on sending side. This strace is from rsyncing over 2Mbit link but I can repeat it over 100Mbps lan, too (while testing on lan 2.6.11.3 was on sending and 2.6.12.6 on receiving side). I wonder what can be problem here? Some

Commit-ID: 77c7ccc993d605eb7f6bef511017d28c1bb2d7e7 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=77c7ccc993d605eb7f6bef511017d28c1bb2d7e7 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Fri, 28 Aug 2020 19:21:47 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 28 Aug 2020 19:52:24 +0100 [klibc] signal: Move

Commit-ID: 2a2a0b6b79c2470f529daabd5c193f58fe188337 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=2a2a0b6b79c2470f529daabd5c193f58fe188337 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Tue, 25 Aug 2020 01:05:28 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 27 Aug 2020 15:00:33 +0100 [klibc] signal: Add sysconfig

Commit-ID: ed8a58947232eab57ce42219f07ca451dcfdd214 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=ed8a58947232eab57ce42219f07ca451dcfdd214 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 30 Apr 2020 03:38:34 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 25 Jul 2020 17:33:29 +0100 [klibc] s390: Set sa_restorer for

Commit-ID: 89d59ccf2d6ffede32c32b26eda57c24ec33b275 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=89d59ccf2d6ffede32c32b26eda57c24ec33b275 Author: Ben Hutchings <ben at decadent.org.uk> AuthorDate: Thu, 30 Apr 2020 03:38:34 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Thu, 20 Aug 2020 23:21:25 +0100 [klibc] s390: Set sa_restorer for

hello, I get some error messages when using BackupPC with rsyncd-style backup: - on the backup server : BackupPC 2.1.2, using its own rsync perl module - on the box being backed up : rsync 2.6.6 , runing as a daemon (rsyncd) the area to be backed up is rather big : ~120 Gb the rsyncd daemon is configured with a big timeout = 7200 a) this is what I get on the backup server