Displaying 20 results from an estimated 4000 matches similar to: "[Bug 273] sshd hangs on shell exit if user spawned child with/bin/nohup"
2002 Aug 07
1
Unrelated (was RE: so-called-hang-on-exit)
Add -n to the ssh command line - see if that fixes it.
Nico
--
> -----Original Message-----
> From: Eric Garff [mailto:egarff at omniture.com]
> Sent: Wednesday, August 07, 2002 11:15 AM
> To: openssh-unix-dev at mindrot.org
> Subject: Re: so-called-hang-on-exit
>
>
> That may be, but it only "hangs" when run from cron, if I run it
> manually it executes
2006 Nov 01
0
No subject
"It is intended to replace rlogin and rsh, and provide secure encrypted
communications between two untrusted hosts over an insecure network."
I can agree that it is "more" than secure RSH, but if it plans to
replace it, shouldn't it have the same functionality?
--
Eric Garff
System Administrator
egarff at omniture.com
801.722.0134
Omniture
http://www.omniture.com
2002 Jun 11
0
[Bug 273] New: sshd hangs on shell exit if user spawned child with /bin/nohup
http://bugzilla.mindrot.org/show_bug.cgi?id=273
Summary: sshd hangs on shell exit if user spawned child with
/bin/nohup
Product: Portable OpenSSH
Version: -current
Platform: UltraSparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo:
2002 Jun 11
0
[Bug 273] sshd hangs on shell exit if user spawned child with /bin/nohup
http://bugzilla.mindrot.org/show_bug.cgi?id=273
------- Additional Comments From kerry.schwab at wnco.com 2002-06-12 06:26 -------
Debug output, with comments:
Get this once i'm in:
>>[some omitted for brevity]
>>debug1: session_new: session 0
>>debug1: Allocating pty.
>>debug1: session_pty_req: session 0 alloc /dev/pts/12
>>debug1: fd 4 setting TCP_NODELAY
2003 Jan 07
0
[Bug 273] sshd hangs on shell exit if user spawned child with /bin/nohup
http://bugzilla.mindrot.org/show_bug.cgi?id=273
djm at mindrot.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
------- Additional Comments From djm at mindrot.org 2003-01-07 18:14
2002 Jul 12
3
[Bug 273] sshd hangs on shell exit if user spawned child with /bin/nohup
http://bugzilla.mindrot.org/show_bug.cgi?id=273
------- Additional Comments From sam at neutrino.phy.uct.ac.za 2002-07-13 01:22 -------
i also have this exact same problem using
OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f
i start a program with "nohup <program> &" and upon returning to my native
machine, the terminal is balnk, frozen with no bash prompt. i
2002 Jul 02
0
Hang when run via crond
Greetings,
I apologize if this has been answered before, but I have tried to do the
obligatory search and haven't found a clear answer.
Running OpenSSH 3.4 (well, pretty much any version) using protocol 2 and
run via crond we see the connection never "close", "end", or whatever
you wish to call it. This is running on a "modified" RedHat 6.2
machine. configure
2002 Aug 07
1
Unrelated (was RE: so-called-hang-on-exit)
"ssh -n ..." means ssh will close stdin and open /dev/null for stdin. It does not mean losing th eoutput of ssh.
Nico
--
> -----Original Message-----
> From: Eric Garff [mailto:egarff at omniture.com]
> Sent: Wednesday, August 07, 2002 12:11 PM
> To: openssh-unix-dev at mindrot.org
> Subject: Re: Unrelated (was RE: so-called-hang-on-exit)
>
>
> Sadly, no such
2003 Jul 08
1
[Bug 334] SSH hangs when run via a cronjob (ssh2)
http://bugzilla.mindrot.org/show_bug.cgi?id=334
egarff at omniture.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |
------- Additional Comments From egarff at omniture.com 2003-07-09 08:00
2002 Jul 03
0
[Bug 334] New: SSH hangs when run via a cronjob (ssh2)
http://bugzilla.mindrot.org/show_bug.cgi?id=334
Summary: SSH hangs when run via a cronjob (ssh2)
Product: Portable OpenSSH
Version: -current
Platform: ix86
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: ssh
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy:
2008 May 12
12
[Bug 1463] New: Running nohup sleep 70 & and then exiting shell, hangs ssh
https://bugzilla.mindrot.org/show_bug.cgi?id=1463
Summary: Running nohup sleep 70 & and then exiting shell, hangs
ssh
Classification: Unclassified
Product: Portable OpenSSH
Version: 5.0p1
Platform: Sparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component:
2013 Jul 02
3
Ctrl+C in R will terminate the child process which is spawned by using "pipe"
Hi, all,
I pressed Ctrl+C in R process, and found that the child process which was
spawned by using "pipe" is terminated due to this.
Are there any way to work around it, so that the child process can run
happily without being terminated? Or can we block the signal for the child
process?
1. I used pipe to spawn one C++ process, which will running in a loop
without exiting immediately.
2007 Aug 07
0
Killing a nohup process?
Hey All, How can I find processes that were started with nohup and kill
them?
thanks all
Also, is this the right list for that kind of question?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.centos.org/pipermail/centos/attachments/20070807/77647bfe/attachment-0001.html>
2013 Apr 15
10
[Bug 2091] New: scp hangs while copying a large file and being executed as a background process ( with nohup )
https://bugzilla.mindrot.org/show_bug.cgi?id=2091
Bug ID: 2091
Summary: scp hangs while copying a large file and being
executed as a background process ( with nohup )
Classification: Unclassified
Product: Portable OpenSSH
Version: 6.1p1
Hardware: Other
OS: AIX
Status: NEW
Severity:
2001 Jul 31
0
Unavailability of wdr.com
Dear Recipient,
It has been noticed that you have been receiving internal e-mails
addressed to you at the @wdr.com internet address. On 31st August
2001, this internet address will no longer be applicable to the bank,
and you will therefore not receive the e-mail. Please ensure that any
people or applications sending e-mails to you using the @wdr.com
address, change to using the @ubsw.com
2000 Nov 20
1
openssh kills the stty values?
Hi all,
I found that on some HP-UX 11 machines running openssh-2.3.0p1 the default values for intr in stty don't work. The problem is that stty shows the correct values but they don' work and I cannot det the values to others. Once I connect via telnet or rlogin I can use the intr-sequence.
Any ideas?
Thanks
Stephan
--
LDS Brandenburg
Dr. Stephan Hendl
fon: +49-(0)331-39 471
fax:
2003 Jan 06
1
Re - segments within a lattice graph
Hi,
The solution to my problem is to use
'lsegments' instead of 'segments' within lattice commands.
(Although I wont forget again,
a comment in the segments help file referring to 'lsegments'
might help others not to make the same mistake in the future.)
My thanks to Renaud Lancelot.
Regards,
John.
John Gavin <john.gavin at ubsw.com>,
Quantitative Risk Models
2002 Dec 23
2
Inheriting environment - sshd server to shell child
The sshd server normally builds the environment variables from scratch
for a shell process it creates. Except when compile for Cygwin, it
simply adds settings to its own set of environment variable settings.
A comment in the code says this special case is made because in
Cygwin, some of sshd's environment is important for child processes
too.
I don't run Cygwin (I run Linux), but on my
2007 Feb 15
2
Multiple Processes Spawned from mongrel_rails start ?
Hello,
I have mongrel 1.0.1, rails 1.2.2 ruby 1.8.5 running on Centos 4.4.
When I execute the mongrel_rails start -d I see that 3 processes are spawned. See below:
[root at ccc aaa]# mongrel_rails start -d
[root at ccc aaa]# ps -def |grep mong
root 2743 1 9 07:14 ? 00:00:01 /usr/bin/ruby /usr/bin/mongrel_rails start -d
root 2744 2743 0 07:14 ? 00:00:00
2010 Nov 03
1
Auto-killing processes spawned by foreach::doMC
Hi all,
Sometimes I'll find myself "ctrl-c"-ing like a madman to kill some
code that's parallelized via foreach/doMC when I realized that I just
set my cpu off to do something boneheaded, and it will keep doing that
thing for a while.
In these situations, since I interrupted its normal execution,
foreach/doMC doesn't "clean up" after itself by killing the