similar to: AW: Solved: on Solaris, "couldn't wait for child '...' completion : Nochild processes"

Displaying 20 results from an estimated 500 matches similar to: "AW: Solved: on Solaris, "couldn't wait for child '...' completion : Nochild processes""

2001 Jan 09
3
OpenSSH on Reliant UNIX
Hello, it's me again ! I tried to compile / install OpenSSH on our Reliant UNIX system, OS version 5.45 (and 5.44). The following problems did appear: 1. OpenSSL-0.9.5a will not compile out of the box. The problem on RU 5.45 is, that the compiler does support "long long" but NOT "unsigned long long". The latter just provokes the error message "superfluous
2001 Jan 08
0
AW: X11-Forwarding for Reliant UNIX (formerly SINIX)
Damien Miller [SMTP:djm at mindrot.org] wrote: > On Mon, 8 Jan 2001, Bladt Norbert wrote: [...] >> The result fo my investigation is: >> 3. All standard X-applications try to determine whether >> they are running locally, i.e. if the DISPLAY on >> computer HOSTX is HOSTX:10.0 the X-applications detect >> that this is the local computer and try to open the
2001 Jan 09
0
Result: X11-Forwarding for Reliant UNIX (formerly SINIX)
Hi ! I promised to report the result to the list. Here it is: Damien Miller [SMTP:djm at mindrot.org] wrote yesterday on his keyboard: > On Mon, 8 Jan 2001, Bladt Norbert wrote: [...] >> During the last week I did some investigations why the X11 forwarding >> on Reliant UNIX Versions 5.44 and 5.45 does not work out of the box >> with OpenSSH-2.3.0p1. >> >> The
2001 Jan 09
0
AW: fatal: PRNG initialisation failed
Joe Warren-Meeks [SMTP:joe at hole-in-the.net] wrote: > open("/usr/local/etc/ssh_prng_cmds", O_RDONLY) = 3 open of the command file succeeded. > brk(0x000E6DB8) = 0 "malloc" in user land, i.e. sshd > brk(0x000E8DB8) = 0 "malloc" in user land, i.e. sshd > fstat64(3, 0xFFBEECD8)
2001 Jan 09
0
Difference 2.1.1 and 2.3.0p1 on Reliant UNIX
Hi ! I upgraded one of our Reliant UNIX systems from 2.1.1 to 2.3.0p1. Now, I suddenly can't login any more. The error message is: Attempting authentication for illegal user ... The reason is: Password expiration Although I don't use my password to login, at all. I login via RSAAuthentication and this did work with version 2.1.1. Version 2.3.0p1, obviously, checks the password
2001 Mar 20
3
Rhosts-RSA authentication broken
Hello ! I think a problem was introduced in openssh-2.3.0p1 which is still there in the latest openssh-2.5.2p1. I just noticed it before my vacation and could not send this mail earlier than today. The problem is: You can't use the Rhosts-RSA authentication based on the hosts.equiv file and the host keys. The only possible way to do rhosts-RSA authentication is to allow the usage of the
2000 Jul 04
0
AW: rhostsauthentication fails. (Or why I hate poorly documented software.)
> jeff at ntcor.com [SMTP:jeff at ntcor.com] wrote: > > I have a ssh enabled server and client machine (we'll call them "server" > and "client" respectively...) OK :-) > They both have proper RSA and DSA keys,using protocol version 2 works > fine between them. (so ssh itself and the network is working fine) OK. > However, I want to get something that
2001 Jan 08
1
X11-Forwarding for Reliant UNIX (formerly SINIX)
Hi ! To all: A Happy New Year ! During the last week I did some investigations why the X11 forwarding on Reliant UNIX Versions 5.44 and 5.45 does not work out of the box with OpenSSH-2.3.0p1. The result fo my investigation is: 1. The OpenSSH sshd opens a TCP/IP-port 6000 + display number and listens to it. This is fine and works with Solaris 7, DEC-OSF 4.0D, Linux and FreeBSD-4.2 but not
2000 May 12
1
Patch: OpenSSH 2.1.0 under Solaris 8, Solaris 7 and other systems , too
Hi ! Karsten Thygesen wrote: >>>>> "carl" == carl <carl at bl.echidna.id.au> writes: > carl> Marc, I'm seeing the same problem if I use the inbuilt entropy > carl> generator, but if I use SUNWski's /dev/random, it's fine. > carl> ssh also coredumps if I use the built in entropy generator if I > carl> run it in verbose mode.
2000 May 19
2
Solved: on Solaris, "couldn't wait for child '...' completion: No child processes"
> John Horne [SMTP:J.Horne at plymouth.ac.uk] wrote: > > Emanuel Borsboom <emanuel at heatdeath.org> wrote: >> Trying to install the portable OpenSSH on Solaris 2.6. Compiling from >> openssh-2.1.0.tar.gz using gcc. Compiles and installs fine. sshd >> starts fine. First connection from another system works. Child sshd is >> forked, but the parent dies
2000 May 17
4
Openssh-2.1.0p1 test release
This to announce a test release of 2.1.0p1 before making it widely available. This release includes many fixes to problems reported over the last week. In particular: - spurious error and coredumps caused by the inbuilt entropy gathering - RSAref detection - Compilation fixes for Solaris and others It also contains (completely untested) support for compiling without RSA support. This may be
2017 Oct 20
1
Another issue with Sys.timezone
>>>>> Stephen Berman <stephen.berman at gmx.net> >>>>> on Thu, 19 Oct 2017 17:12:50 +0200 writes: > On Wed, 18 Oct 2017 18:09:41 +0200 Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>>> Martin Maechler <maechler at stat.math.ethz.ch> >>>>>>> on Mon, 16 Oct 2017 19:13:31 +0200
2017 Oct 16
0
Another issue with Sys.timezone
>>>>> Stephen Berman <stephen.berman at gmx.net> >>>>> on Sun, 15 Oct 2017 01:53:12 +0200 writes: > (I reported the test failure mentioned below to R-help but was advised > that this list is the right one to address the issue; in the meantime I > investigated the matter somewhat more closely, including searching > recent R-devel
2017 Oct 14
2
Another issue with Sys.timezone
(I reported the test failure mentioned below to R-help but was advised that this list is the right one to address the issue; in the meantime I investigated the matter somewhat more closely, including searching recent R-devel postings, since I haven't been following this list.) Last May there were two reports here of problems with Sys.timezone, one where the zoneinfo directory is in a
2017 Oct 19
0
Another issue with Sys.timezone
On Wed, 18 Oct 2017 18:09:41 +0200 Martin Maechler <maechler at stat.math.ethz.ch> wrote: >>>>>> Martin Maechler <maechler at stat.math.ethz.ch> >>>>>> on Mon, 16 Oct 2017 19:13:31 +0200 writes: (I also included a reply to part of this response of yours below.) >>>>>> Stephen Berman <stephen.berman at gmx.net>
2000 May 12
1
Patch: OpenSSH 2.1.0 under Solaris 8, Solaris 7 and other sys tems, too
> -----Urspr?ngliche Nachricht----- > Von: Andre Lucas [SMTP:andre.lucas at dial.pipex.com] > Gesendet am: Freitag, 12. Mai 2000 16:37 > An: Bladt Norbert > Cc: 'Karsten Thygesen'; 'openssh-unix-dev at mindrot.org'; > 'carl at bl.echidna.id.au' > Betreff: Re: Patch: OpenSSH 2.1.0 under Solaris 8, Solaris 7 and > other systems, too > > Well
2017 Oct 18
2
Another issue with Sys.timezone
>>>>> Martin Maechler <maechler at stat.math.ethz.ch> >>>>> on Mon, 16 Oct 2017 19:13:31 +0200 writes: >>>>> Stephen Berman <stephen.berman at gmx.net> >>>>> on Sun, 15 Oct 2017 01:53:12 +0200 writes: > > (I reported the test failure mentioned below to R-help but was advised > > that this list is
2012 Oct 17
5
Problem reading vitals from Gigabyte H77-DH3H
Hello everyone, I'm unable to read temperature Gigabyte H77-DH3H motherboard. Is that motherboard supported or am I doing it incorrectly? When trying to access hw.acpi.thermal everything appears to be ok, but it is not, the system always returns 27,8C and 29,8C which fooled me initially - the values never change. Here is output: [chinatsu]:/root# sysctl hw.acpi.thermal
2013 Jul 22
1
Error with sem function df = -6
Hello all, I have an issue where I am generating data and trying to confirm the estimates using a sem. I keep getting an error about the degree of freedom being negative "Error in sem.default(ram, S = S, N = N, raw = raw, data = data, pattern.number = pattern.number, : The model has negative degrees of freedom = -6" Can someone explain this error or tell me what is wrong with my
2000 May 19
0
I present: The Elusive 'fixprogs' script
Hi, Here's the 'fixprogs' perl script that got missed off the 2.1.0p1 distribution. Please put this in your openssh directory, and re-run 'make install'. it doesn't need to be made executable. For those interested, it runs through all the commands in the ssh_prng_cmds file and tests if they work (as opposed to 'configure' merely verifying that the executable