similar to: [Test Problem] RSync 3.2.3 - Commit 15bc7ded

On 6 April 2018 at 01:36, Randall S. Becker <rsbecker at nexbridge.com> wrote: [...] > Sorry to report that I'm having difficulty building on NonStop (built from a > git clone at 2c71ca1). Configure is failing, run as: > > configure --prefix=/usr/local --without-openssl-header-check > ... > checking for sys/un.h... yes > checking compiler and flags for sanity... no

On February 9, 2016 7:28 PM, Darren Tucker wrote: > To: Randall S. Becker <rsbecker at nexbridge.com> > Cc: OpenSSH Devel List <openssh-unix-dev at mindrot.org> > Subject: Re: Test Failure OpenSSH 7.1 P2 on HPE NSE for key-commands > > On Wed, Feb 10, 2016 at 10:35 AM, Randall S. Becker > <rsbecker at nexbridge.com> wrote: > > Thread split from my

G'Day, I am requesting help in resolving an issue on the HPE NonStop platform in OpenSSH 7.1 P2 in the regression suite for all dd-size above 32k. Previous tests are all passing, but in the for-loop inside regress/transfer.sh, when s is 64k, the command: dd if=$DATA obs=${s} 2> /dev/null | \ ${SSH} -q -$p -F $OBJ/ssh_proxy somehost "cat >

On Mon, Jan 15, 2018 at 6:20 AM, Randall S. Becker <rsbecker at nexbridge.com> wrote: > Incompatibility introduced at 3.1.3pre1. These are not present at master, > which compiles cleanly. > The master branch and 3.1.3pre1 were pretty much the same until just a moment ago (except that the tar files get some generated files that aren't present in git, such as the autoconf

On February 8, 2016 3:30 PM, Darren Tucker wrote: > To: Randall S. Becker <rsbecker at nexbridge.com> > Cc: OpenSSH Devel List <openssh-unix-dev at mindrot.org> > Subject: Re: [Bug] Regression problem in transfer.sh for OpenSSH 7.1 P2 on > HPE NSE above dd-size 32k > > On Tue, Feb 9, 2016 at 6:36 AM, Randall S. Becker > <rsbecker at nexbridge.com> wrote:

On 13 April 2018 at 08:29, Josh Soref <jsoref at gmail.com> wrote: > Randall S. Becker <rsbecker at nexbridge.com> wrote: >> >> >> -REGRESSTMP = "$(PWD)/regress" >> +REGRESSTMP = `pwd` >> >> tests interop-tests t-exec unit: regress-prep regress-binaries $(TARGETS) > > > It looks like the problem is that pwd is in uppercase, not

On January 22, 2019 10:45, I wrote: > On January 21, 2019 19:00, Darren Tucker wrote: > > On Tue, 22 Jan 2019 at 12:01, Randall S. Becker > > <rsbecker at nexbridge.com> > > wrote: > > > > > Hi All, > > > > > > I finally got around to trying to test the 7.7p1 release on the HPE > > > NonStop Platform. 7.6p1 worked just fine - no

On Thu, Apr 12, 2018 at 6:29 PM, Josh Soref <jsoref at gmail.com> wrote: > Randall S. Becker <rsbecker at nexbridge.com> wrote: > >> >> -REGRESSTMP = "$(PWD)/regress" >> +REGRESSTMP = `pwd` >> >> tests interop-tests t-exec unit: regress-prep regress-binaries $(TARGETS) >> > > It looks like the problem is that pwd is in

https://bugzilla.samba.org/show_bug.cgi?id=13224 Bug ID: 13224 Summary: New file handling causes compile issues for NonStop port. Product: rsync Version: 3.1.3 Hardware: Other OS: Other Status: NEW Severity: normal Priority: P5 Component: core Assignee:

https://bugzilla.mindrot.org/show_bug.cgi?id=3205 Bug ID: 3205 Summary: Support HPE NonStop Server Port Product: Portable OpenSSH Version: 8.3p1 Hardware: Other OS: Other Status: NEW Severity: enhancement Priority: P5 Component: Build system Assignee: unassigned-bugs at

Hi All, Just reporting in on how testing has gone. After reducing obs to 32k max and banners to a max of 10000, plus some minor platform changes - root is not 0, for example, all normal tests have passed except for: multiplex - hangs at the end of this output. We had a similar issue that single reads of data were not working in dd but that does not seem to be the case in this test suite. test

On February 9, 2016 9:30 PM, Darren Tucker wrote: > To: Randall S. Becker <rsbecker at nexbridge.com> > Cc: OpenSSH Devel List <openssh-unix-dev at mindrot.org> > Subject: Re: Test Failure OpenSSH 7.1 P2 on HPE NSE for integrity > [...] > This one looks odd. The ssh session itself looks OK: it authenticates then > sends a printf shell command (basically, just a way

Hi All, I finally got around to trying to test the 7.7p1 release on the HPE NonStop Platform. 7.6p1 worked just fine - no issues at all. In 7.7p1, when the agent test ran, the following happened (prior tests worked perfectly): run test agent.sh ... Couldn't open logfile /home/git/openssh-portable/regress/ssh.log: Permission denied agent fwd failed (exit code 1) failed simple agent test

On Fri, Feb 12, 2016 at 9:25 AM, Randall S. Becker <rsbecker at nexbridge.com> wrote: > On February 10, 2016 10:23 AM, I wrote: >> On February 9, 2016 9:30 PM, Darren Tucker wrote: >> [...] >> > This one looks odd. The ssh session itself looks OK: it authenticates >> > then sends a printf shell command (basically, just a way of >> > guaranteeing a

On 13/04/18 07:59, Josh Soref wrote: > Randall S. Becker <rsbecker at nexbridge.com> wrote: > >> -REGRESSTMP = "$(PWD)/regress" >> +REGRESSTMP = `pwd` >> >> ? tests interop-tests t-exec unit: regress-prep regress-binaries >> $(TARGETS) >> > It looks like the problem is that pwd is in uppercase, not so much the > distinction between

On Mon, 8 May 2023 at 06:13, <rsbecker at nexbridge.com> wrote: [...] > Is this not already covered using the --without-openssl-header-check > configuration option? No. That configure option will disable the consistency check between the headers and library versions at compile time, ie the API. It was added when some vendors (from memory, Apple) started shipping libcrypto updates

On Sun, Sep 20, 2020 at 03:13:28PM -0400, Randall S. Becker wrote: > On September 20, 2020 2:02 AM, Damien Miller wrote: > > OpenSSH 8.4p1 is almost ready for release, so we would appreciate testing > > on as many platforms and systems as possible. This is a bugfix release. > > I will be testing this shortly on HPE NonStop platforms. > > Side question: We now have

July 1, 2024 at 2:47 PM, rsbecker at nexbridge.com wrote: > Would you be able to document that "thisHost" may be ambiguous, depending on > the DNS and host resolver configuration? gethostname() is not entirely > predictable if the localhost has multiple values. Hm? On linux/glibc, gethostname just uses uname(2). It does not use dns or the name service switch.

On Monday, July 1, 2024 6:37 PM, Ronan Pigott wrote: >July 1, 2024 at 2:47 PM, rsbecker at nexbridge.com wrote: > >> Would you be able to document that "thisHost" may be ambiguous, >> depending on the DNS and host resolver configuration? gethostname() is >> not entirely predictable if the localhost has multiple values. > >Hm? On linux/glibc, gethostname just

July 1, 2024 at 3:55 PM, rsbecker at nexbridge.com wrote: > That is correct for linux/glibc. Other platforms do not necessarily use > uname(2). Glibc is not available everywhere and gcc is not available > everywhere. Okay, well, I suppose I can mention that in the existing documentation for %l in the man page. I can submit that in a follow up patch ? this is not the first introduction