search for: sigchild

...'--enable-soap' '--with-gd' '--enable-xml' '--with-xml' '--enable-sysvsem' '--enable-sysvshm' '--enable-sysvmsg' '--with-regex=system' '--with-png' '--with-ttf=/usr/lib' '--with-freetype=/usr/lib' '--enable-sigchild' '--with-openssl' '--with-iconv' My current Config: './configure' '--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-linux-gnu' '--target=x86_64-redhat-linux-gnu' '--program-prefix=' '--prefix=/usr' '--exec-prefix=/usr&...

...se of the unexplained error (code ??) at main.c(line #). In the version I'm running 2.5.2 (obtained from the Free Software Foundation) the line number is 576. It appears the root cause is related to a race condition associated with the termination of child processes. If the signal handler for SIGCHILD is executed, as the result of a child termination, before the wait_process procedure is executed, the status of pid (as passed to wait_process) will not be available and the waitpid call in wait_process will fail with an ECHILD error. If however, wait_process executes first, it will successfully o...

https://bugzilla.mindrot.org/show_bug.cgi?id=1812 Summary: ControlPersist causes defunct/zombie processes Product: Portable OpenSSH Version: 5.6p1 Platform: All URL: http://bugs.debian.org/594687 OS/Version: All Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo:

Hi, In KubeVirt we are right now starting libvirt via a wrapper shell script. I want to remove that wrapper and directly start libvirtd from our golang code. This means that our golang code is PID 1 in the container and we start libvirtd as a fork from there. When I did this, strange things started to happen. Libvirt was still able to start and manage qemu processes, but stopping the qemu

...ections, authenticate users as normal, but their shell appears to die during connection. The only output a user will get after authentication is: Last login: Wed Jun 5 07:12:49 2002 from somehost and it disconnects. Following is partial output from sshd -d -d -d. I'm most interested in the SIGCHILD, but not sure if I'm barking up the wrong tree. Any ideas? Anyone seen this before? Accepted password for baertr from 10.55.40.33 port 33250 ssh2 debug1: Entering interactive session for SSH2. debug1: fd 3 setting O_NONBLOCK debug1: fd 4 setting O_NONBLOCK debug1: server_init_dispatch_20 deb...

...boxes, nor between the Sun-boxes. My config files are standard and the "subsystem"-entry looks just fine. I've included the output (without IP-numbers and user names) on the client and the server side below (the latter using "Loglevel DEBUG"). Everything just dies after the SIGCHILD. What is going on? Two other users have contacted me regarding my earlier, unanswered posts concerning problems with sftp (then for v. 2.3.0p1) because they hade the same problem. Any help would be very appreciated as I've exhausted all options I can think of. Sincerely, Olof Liungman actin...

I have been trying for hours to get the unix password sync going properly with Samba 1.9.18p4 running on FreeBSD 2.2.5 I have compiled Samba with the ALLOW_CHANGE_PASSWORD option enabled. I created the smbpasswd file as ENCRYPTION.txt states, and can set passwords as root. However, when a user tries changing their password, it doesn't work. The error reported is:

Hi, In http://sources.redhat.com/ml/cygwin/2002-09/msg01155.html, I noted that the often-observed hangs of rsync under Cygwin were assuaged by a call to msleep(). After upgrading my Cygwin environment to rsync 2.5.6, I'm seeing these hangs again, not surprisingly given a CVS entry for main.c notes that this kludge was not harmless: Revision 1.162 / (download) - annotate - [select for

...replace all calls to signal(2) with a wrapper around sigaction(2). This wrapper blocks all other signals during the handler preventing races between handlers, and sets SA_RESTART which should reduce the potential for short read/write operations. * sftp(1): fix a race condition in the SIGCHILD handler that could turn in to a kill(-1); bz3084 * sshd(8): fix a case where valid (but extremely large) SSH channel IDs were being incorrectly rejected. bz3098 * ssh(1): when checking host key fingerprints as answers to new hostkey prompts, ignore whitespace surrounding the fingerprin...

...replace all calls to signal(2) with a wrapper around sigaction(2). This wrapper blocks all other signals during the handler preventing races between handlers, and sets SA_RESTART which should reduce the potential for short read/write operations. * sftp(1): fix a race condition in the SIGCHILD handler that could turn in to a kill(-1); bz3084 * sshd(8): fix a case where valid (but extremely large) SSH channel IDs were being incorrectly rejected. bz3098 * ssh(1): when checking host key fingerprints as answers to new hostkey prompts, ignore whitespace surrounding the fingerprin...

...replace all calls to signal(2) with a wrapper around sigaction(2). This wrapper blocks all other signals during the handler preventing races between handlers, and sets SA_RESTART which should reduce the potential for short read/write operations. * sftp(1): fix a race condition in the SIGCHILD handler that could turn in to a kill(-1); bz3084 * sshd(8): fix a case where valid (but extremely large) SSH channel IDs were being incorrectly rejected. bz3098 * ssh(1): when checking host key fingerprints as answers to new hostkey prompts, ignore whitespace surrounding the fingerprin...

...replace all calls to signal(2) with a wrapper around sigaction(2). This wrapper blocks all other signals during the handler preventing races between handlers, and sets SA_RESTART which should reduce the potential for short read/write operations. * sftp(1): fix a race condition in the SIGCHILD handler that could turn in to a kill(-1); bz3084 * sshd(8): fix a case where valid (but extremely large) SSH channel IDs were being incorrectly rejected. bz3098 * ssh(1): when checking host key fingerprints as answers to new hostkey prompts, ignore whitespace surrounding the fingerprin...