similar to: Samba configuration on Dynix

Hello Porters, I've finally (thanks to Wendy Palm of Cray) ported OpenSSH to Dynix v4.4.4. I had to make sure that "UseLogin" was set to "no" in the sshd_config file. Also, here are the old-style contextual diffs (obtained with 'diff -c' on the Dynix box) of the two files I had to change: *** configure Sat Jun 16 17:09:50 2001 --- configure.new Mon Oct 8

Hi, I am attempting to compile SSH under Sequent Dynix/ptx 4.4.7, After compiling and installing ZLIB to /usr/local/include and /usr/local/lib the ./configure command returns that ZLIB is not installed. Any ideas? Or should I be redirecting this question to the ZLIB mailing lists? Thanks T -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello Porters, I am attempting to compile OpenSSH 2.9.9p2 on a Dynix V4.4.4 host. I have set USE_PIPES and BROKEN_SAVED_UIDS (the latter because there are no functions for set{eu,eg}id() that I can find). I configured with "./configure '--with-libs=-lnsl -lsec'". Each time I attempt to login, I get this error: No utmp entry. You must exec "login" from

Do you know if OpenSSH supported for OS's ibm ptx/dynix 4.51 version? Thank you ============================================ Tony T. Doan SOI Devep. & Maint. Section 1160 W 1200 S Ogden, UT 84201 M/S 6380 tony.t.doan at irs.gov 801-620-7679 phone 801-620-7614 fax -------------- next part -------------- An HTML attachment was scrubbed... URL:

Greetings - In trying to get rsync-2.5.6pre1 working on DYNIX/ptx, I found I needed to pass ac_cv_lib_inet_connect=no to configure in order for it actually create a properly configured config.h file. I think this is because configure looks for connect in libinet, (and finds one there somehow). But connect() is resolved by libsocket (but configure doesn't find it when

Hello there, I am trying to build OpenSSH on the above (very old) version of unix. With a bit of hacking, I have managed to get everything to compile and run. Scp works fine however when I log in via ssh I end up with a session without a controlling terminal. I have followed the code in pty_make_controlling_tty and it seems to go as follows: 1. Starts with a controlling tty. 2. setsid works,

Hi, I am attempting install of samba 2.2.7 on a Sequent (IBM) Dynix 4.4.6 platform. I downloaded the samba-latest.tar from the samba website: samba.mirror.ac.uk/samba/download.html Having unzipped and untarred the file, I then started as per the "how to", very first part. I ran "./configure" which generated a number of messages before failing as follows: ... ... ...

Hi I am having problems with machine authentication on an NT workstation 4.0 SP6a client. The current version of samba is 2.0.4b complied on Sequent/Dynix 4.4.8. We are using "smbd" and "nmbd" as services launched from the inetd file. No restrictive or secure components have been enabled. The "smb.conf" simply has the appropriate mount options defined. The problem

Hello, Inspired by successfully compiling 2.0.6 on a SCO Unixware 7.1 box I attempted similar on a Sequent Numa-Q running Dynix 4.4.2. Er , Configure failed with the following message: checking for conflicting AUTH_ERROR define in rpc/rpc.h... no checking for test routines... configure: error: cant find test code. Aborting config I am mostly ignorant of C: any suggestions as to my next move

Hello, I am currently using Samba 2.2.3a on a Sequent box running DYNIX/ptx v4.0. We are serving up approximatly 4.5 terrabytes of data from a Hitachi Data Systems storage array connected to our server by fiber channel. Many of our users are on Citrix which connects to our SAMBA server via a Gigabit Ethernet connection. There are still others that are connecting directly from their PCs which are

This morning I see this in the syslog on our primary public DNS host. internal_send: 142.77.1.1#33950: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#35153: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#35644: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#49394: Connection timed out: 1 Time(s) internal_send: 142.77.1.1#49816: Connection timed

Hi, I'm using samba just for its "net join" functionality. Computer accounts and kerberos keytabs are created by Samba in Active Directory via "net ads join", then used by UNIX clients to authorise and authenticate via LDAP and Kerberos. Samba works perfectly until the computers hostname is longer than 15 characters. Then any attempt to join the domain fails with: ----

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Fraunhoffer claims patents on other formats") and forwarded it to the appropriate personnel for processing.

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("[vorbis] Improve your stepfamily life") and forwarded it to the appropriate personnel for processing. To help us provide

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Announce: VCE v0.1.2") and forwarded it to the appropriate personnel for processing. To help us provide you

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Announce: VCE v0.1.2") and forwarded it to the appropriate personnel for processing. To help us provide you

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Announce: VCE v0.1.2") and forwarded it to the appropriate personnel for processing. To help us provide you

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Announce: VCE v0.1.2") and forwarded it to the appropriate personnel for processing. To help us provide you

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("[vorbis] VCE 0.1.3") and forwarded it to the appropriate personnel for processing. To help us provide you with the best

** THE RETURN ADDRESSES ON THIS LETTER HAVE BEEN SET TO PREVENT MAIL ** ** LOOPS IN THE EVENT YOU ARE RUNNING SOFTWARE WHICH AUTO-REPLIES TO ** ** INBOUND MAIL. UUNET WILL NOT SEE ANY REPLY SENT TO THIS LETTER. ** Dear Customer, We have received your message ("Re: [vorbis] Experimental info editor for winamp") and forwarded it to the appropriate personnel for processing. To help