similar to: [Bug 52] ssh hangs on exit

While browsing through bash's hugh manpage, I noticed that it has a 'huponexit' option which will send SIGHUP to all interactive processes when the shell exits. I have tested this and it does resolve the hanging at logout without causing race conditions. I now have a "shopt -s huponexit" in my /etc/bashrc and it works beautifully. -d -- | ``We've all heard that a

Hi, The following discussion was posted to comp.security.ssh however, it seems that my problems may be a bug in SSH. Could someone please indicate whether there is a bug fix, or perhaps whether I should go back a version or so. In summary: - Win98 machine (client) - OpenSSH as packaged with Cygwin tools 1.1.8 (openssh-2.5.2p2-3) - Connecting to a Sun running Solaris. ssh: SSH Secure Shell

Hello Darren, The major problem we are running into is that the shell (both sh and ksh) does not kill its child processes when there is no pty. The SSH patch mentioned previously at http://bugzilla.mindrot.org/show_bug.cgi?id=396 is not sufficient to kill the forced command completely.It will only kill the shell script, but not any child processes the shell script runs. The shell assumes the

Hi, I am using Redhat 7.3 which comes with openssh 3.1p1. I am running an antivirus software called vexira on this server. It starts of 2 daemon processes in the background. Whenever I stop/start these daemons in an ssh session, it hangs. I added "shopt -s huponexit" (without the quotes) in /etc/bashrc, but the hangs still occur. Any advice on this would be appreciated Regards, Yusuf

Ok, so I think I have a complete explanation for the difference between the *BSD behaviour and the Linux/Solaris behaviour. Well, almost complete :) Pull out your trusty copies of "The Design and Implementation of the 4.4BSD Operating System" as well as "Unix Internals: The New Frontiers". Specifically, pages 111-112 and 344 of the former and page 108 of the latter. It comes

I'm trying to get OpenSSH 2.5.2p2 to run on HP-UX 9.05. I've had some decent results, but I'm also seeing some problems. I'm using the EGD (I configured with --with-prngd-socket=/tmp/entropy). * Compiling required some changes, which I've attached. Two of the changes are "hackish", and not at all suited to inclusion in the source tree, but they might point

FWIW, now that privsep is mandatory I have no objection to including signal support in sshd. On Wed, 25 Jul 2018, Yonathan Bleyfuesz wrote: > Hi all, > > I would like to propose some ideas to revivify this subject. > > -First, we could add support on the client to send signal thanks to the escape characters. > (code :

I am running OpenSSH 2.9p1 on SunOS 5.7 w/4-24-2001 patch cluster. Like many other users I am seeing the hanging session on logout with background processes. This is a huge problem for me as I centrally manage 50+ machines with rdist across ssh. Instead of just complaining about the problem I thought I would put my CS degree to use and try to track down the problem myself. For starters,

Hi, For this issue I had initial discussion thread before, more detail, please see : http://lists.xensource.com/archives/html/xen-devel/2010-04/msg01140.html. I write a new patch for this issue, which modified qemu code. So Ian, could you take a look this patch,too. thanks, James (Song Wei) Signed-off-by: James ( Song Wei ) <jsong@novell.com> diff -r efa1b905d893

As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor. This patch addresses the most basic stuff (mostly what is required for virtio-ccw), and does take care of QDIO or any devices. An interesting side effect is that virtio structures are now going to get allocated in 31 bit addressable storage. Signed-off-by: Halil Pasic <pasic at

From: Halil Pasic <pasic at linux.ibm.com> As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor. It handles neither QDIO in the common code, nor any device type specific stuff (like channel programs constructed by the DASD driver). An interesting side effect is that virtio structures are now going to get allocated in 31 bit

From: Halil Pasic <pasic at linux.ibm.com> As virtio-ccw devices are channel devices, we need to use the dma area for any communication with the hypervisor. It handles neither QDIO in the common code, nor any device type specific stuff (like channel programs constructed by the DASD driver). An interesting side effect is that virtio structures are now going to get allocated in 31 bit

As virtio-ccw devices are channel devices, we need to use the dma area within the common I/O layer for any communication with the hypervisor. Note that we do not need to use that area for control blocks directly referenced by instructions, e.g. the orb. It handles neither QDIO in the common code, nor any device type specific stuff (like channel programs constructed by the DASD driver). An

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

CentOS Errata and Bugfix Advisory 2012:1193 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1193.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: e2349a6fe1df5df8f3666fc7813161e180e7e09f4664c285c295a7f8bf872bb7 pdksh-5.2.14-37.el5_8.1.i386.rpm x86_64:

Initial problem: When running 'make test' the hands.test fails as indicated in problem #3711 and includes the line rsync error: unexplained error (code 63) at main.c(537) The code # changes each time the test is run. Using HP C-ANSI-C B.11.11.02. configure line: CFLAGS="-O" ./configure --prefix=/opt/local In tracking this down, this is what I found: In main.c a

We observe a difference between a Windows 7 client and Windows 2003/XP client when accessing directories that should be accessible via the UNIX accounts primary group GID. Windows client refuses access. Ignoring for now why the two different client behaviours (either some subtle difference in the requests or the way the Samba reply is dealt with) the question is what should be the correct

Hi, Ssh -f forks itself in the background. Very usefull if you would like to e.g. tunnel munin over ssh. Now it's tricky to terminate one process if you have multiple running. It seems that ssh currently (looked at 5.1p1) has no write-pid-to-file functionality So I implemented a patch which do so. Tested it a little and it seems to work. Hopefully it is of any use in my form or inspires the

CentOS Errata and Bugfix Advisory 2011:1394 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1394.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 3cb8683a5a6420df062776f51d8d6e6c pdksh-5.2.14-37.el5.i386.rpm Source: d2f81caabc750fb469dc347c6e050b87 pdksh-5.2.14-37.el5.src.rpm -- Johnny Hughes CentOS

CentOS Errata and Bugfix Advisory 2011:1394 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1394.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: a593bc8aad177aece733e362e743f554 pdksh-5.2.14-37.el5.x86_64.rpm Source: d2f81caabc750fb469dc347c6e050b87 pdksh-5.2.14-37.el5.src.rpm -- Johnny Hughes