similar to: 2.5.1pre3 - Bugs in configure script / config.h.in breaks build.

I am trying to debug the RSYNC client and server by single stepping through them. The server seems to ok up to the point where it is waiting for the client connection. On the client side, I am having trouble finding the right options so that it will connect up to the local server with out fork() a copy of itself or trying to exec the rsh command. This is on RSYNC 2.5.5 on OpenVMS Alpha. If

Hello, rsync.h is always including the syslog.h file, even though it is only used when the LOG_DAEMON macro is defined. Could someone change it to be as follows: #ifdef LOG_DAEMON #include <syslog.h> #endif OpenVMS currently does not have a syslog facility, so it does not have a syslog.h. Thank you, -John wb8tyw@qsl.net Personal Opinion Only

> Qualities > > 1. Be reasonably portable: at least in principle, it should be > possible to port to Windows, OS X, and various Unixes without major > changes. In general, I would like to see OpenVMS in that list. > Principles > > 1. Clean design rather than micro-optimization. A clean design allows optimization to be done by the compiler, and tight optimization

Refer to this: https://legacyos.org/vsi-introduces-new-samba-release/ I noticed that VSI, the new owners of VMS, have created a package for Samba4 under OpenVMS. I also notice the samba-vms list appears to be abandoned (for years). So, I apologize for posting here on the general list, but it seemed fruitless trying the dedicated list. I am under the impression that the GPL v3 compels all

I am still chasing this down, but in doing the build for OpenVMS, I have discovered that one of the popt modules is using HAVE_ALLOCA_H to determine if the alloca function is on a platform. That is not a good assumption. Compaq C does have an alloca() built in (slightly different symbol name, I assume because of symbol naming rules in the C standard.) Because alloca is a non-standard

The following popt files need patches in order to compile using Compaq C on OpenVMS. These patches should also be needed on a Tru64 or LINUX on ALPHA using Compaq C. Except for the alloca issue, these should work on any ANSI compliant compiler. Operating System: OpenVMS ALPHA V7.3 Compiler: Compaq C T6.5 Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE) SYSTEM.H is doing tests on

Hi, openssh_cvs as of today, SCO Open Server 3.0, socklen_t this typedef doesn't exist on SCO OSR 3, and "configure" properly detects this, leading to /* #undef HAVE_SOCKLEN_T */ in config.h. Problem: I can't find any place where this is actually being used? I'd expect something like #ifndef HAVE_SOCKLEN_T typdef int socklen_t; #endif ("int" is what the

This affects the XMMS plugin. configure.in has this test: AC_CHECK_TYPES(socklen_t, [], []) And src/plugin_xmms/http.c is the only consumer: #ifndef HAVE_SOCKLEN_T typedef unsigned int socklen_t; #endif Together this looks bogus to me. The configure check looks for socklen_t in the default headers. If it isn't found there, socklen_t will be typedef'ed. However, at least on

I do not know how many others are in this case, but I must use either floppies or tapes to transport the Samba product after I download it. Floppies are more convenient than tape because the tape medium is TK50 on OpenVMS and it is very slow. Is is possible to produce the production release in a two archive set so that it can be more easily sneaker-netted? Thank you, John Malmberg

I just installed Samba for VMS (1.9.17p4) on a DecServer 1000A running VMS 7.1 The University Network is primarily NT Server 4.0 SP5. My experience is with Netware and NT, not with VMS, but I have the luck of supporting the system..... My main question is about Encrypted Passwords.....Does this release of Samba support them, or do I have to modify the clients who want access to our Alpha to

On Thu, 2020-06-11 at 17:02 -0600, Swift Griggs via samba wrote: > Refer to this: > https://legacyos.org/vsi-introduces-new-samba-release/ > > I noticed that VSI, the new owners of VMS, have created a package > for > Samba4 under OpenVMS. I also notice the samba-vms list appears to be > abandoned (for years). So, I apologize for posting here on the > general > list,

On Fri, 12 Jun 2020, Andrew Bartlett via samba wrote: > I can't find any evidence in the source code for new patches to have > Samba build on VMS Okay, well, at least I didn't just overlook something. > it certainly wasn't something we actively targeted when we moved from > autoconf to WAF with Samba 4.1. I'd be shocked if you did. Python 3.x isn't available on

The Open Group Single Unix standard shows that the data types int64 and uint64 are defined in the inttypes.h header file. Rsync is not including this file, nor is there a feature test for this header file in the configure phase, but rsync is using these data types. -John wb8tyw@qsl.net Personal Opinion Only

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 openssh-1.2.1pre23 is available on: http://violet.ibs.com.au/openssh/files/ Highlights of this release: - - A cleanup of the PAM code (it now lives in auth-pam.[ch]). This also fixes a bug where sshd was ignoring a "PermitRootLogin without-password" directive. - - David Randkin's SOCKS support using the Dante libraries. I have not

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 openssh-1.2.1pre23 is available on: http://violet.ibs.com.au/openssh/files/ Highlights of this release: - - A cleanup of the PAM code (it now lives in auth-pam.[ch]). This also fixes a bug where sshd was ignoring a "PermitRootLogin without-password" directive. - - David Randkin's SOCKS support using the Dante libraries. I have not

Platform: Compaq OpenVMS Alpha 7.3 Compiler: Compaq C T6.5 The following patch is an update to a previous patch that I submitted. The only change from the previous patch is that the const qualifier has been added to write_batch_*() routines to improve compiler efficiency. Because the gdiff -u was done against the distribution it includes the previous patch. The functions with no parameters

I am getting the following error from smbclient and am not sure as where the problem is. smb: \gcc\> dir write_socket_data: write failure. Error = broken pipe write_socket: Error writing 91 bytes to socket 3: ERRNO = broken pipe failed session setup Error writing 91 bytes to client. -1. Exiting This appears to be happening about a minute after I establish a session. Up until that time file

Here's a configure check to see if socklen_t is defined. Even though my man pages on linux say accept(2) takes (int *) as it's 3rd arg, the sys/socket.h files begs to differ. If not defined (which is doesn't seem to be on AIX 4.2.1), it can be explicitly typedef'ed to (unsigned int). Now do mainstream code changes get submitted back to the openbsd group, or would it be better to

In socket.c, the variable error is unitilialzed. Also the variable length should be an unsigned int. EAGLE> type socket.gdiff --- ref_src:socket.c Sat Jan 5 13:27:07 2002 +++ lcl_src:socket.c Sun Jan 6 08:40:51 2002 @@ -1,3 +1,4 @@ +/* Converted by prj_src:unix_c_to_vms_c.tpu AND prj_src:socket.tpu on 6-JAN-20 02 08:40:51.01 OPENVMS_AXP */ /* -*- c-file-style: "linux"

> From: jw schultz <jw@pegasys.ws.invalid> > > On Fri, Jul 26, 2002 at 09:03:32AM -0400, Bennett Todd wrote: > >>2002-07-26-03:37:51 jw schultz: >> >>>All that matters is that we can represent the timestamps in >>>a way that allows consistent comparison, restoration and >>>transfer. >> >>A very good statement indeed. There are