similar to: defunct in 1.24 on FreeBSD Alphaserver

Is this an acceptable machine or does it have to be "rackmount" ? http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=250111166910 - rh -- Abba Communications Spokane, WA www.abbacomm.net

hi, i've succesfully built R 1.6.0 on a ds10 with a " stock" redhat 6.2 all tests are ok i've installed the following packages survival and cmprsk succesfully but when i use the crr function (cmprsk package) i got a segmentation fault my question is : any one build a R version with ev6 processor (with or with out compaq fortran and c) thanks -- Get your free email from

Hi Paul, your suggestion about batch.c got by the compiler without a peep and it got much farther along again with complaint from cc until.... [root@hyperion: rsync-2.5.4]#CC=cc; export CC; ./configure configure: Configuring rsync 2.5.4 checking build system type... alphaev5-dec-osf5.1 checking host system type... alphaev5-dec-osf5.1 checking target system type... alphaev5-dec-osf5.1 checking for

Hi, I use previous 4.4 version on my two Compaq AlphaServer systems. Is there a chance that CentOS 5 will also become available for Alpha? Thanks, Rob. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

Hello. I'm hoping that you will provide some help with a Samba problem that I'm experiencing. We have an Alphaserver that has been functioning as the Samba-server in a Windows/NT Domain for about 5 years now. It was set up by an engineer here at Raytheon Missile Systems Company and he left the company about 2 years ago. I've inherited the administration of it. Last week

Dear List Sorry if this is trivial, but I can't find it in the manual, FAQ or mail list (2002). I just installed R 1.6.0 (2002-10-01) on Linux R.H. 7.2 (2.4.9-32.5) on an DIGITAL AlphaServer 800 5/500 The program starts up nicely but exits immediately with a "Segmentation fault" at the first command. It seems that it doesn't matter what command, I tried q(), help(), version,

>From a "Standards" thread I saw this : "Linux should be as easy as Windows" I would like to point out that this is a thinking problem. A shift in thinking is required. That should say : "Open source and Free software should be as easy as Windows" In this way we allow someone running BSD, Solaris or some port of Debian to an old Dec AlphaServer

Hi- Since the tru64 patch was designed for -current, I thought I would try to build it with a recent snapshot before backporting to 3.4p1. So I downloaded openssh-SNAP-20020826.tar.gz frpm the portable snapshots, but it does not contain the 'configure' script. I tried copying the 'configure' from 3.4p1, but that does not create a Makefile from the Makefile.in. Where are the

Well, next problem. Because of samba isn't running on alphaserver 1200 with gentoo linux and kernel 2.6.9-ac12 i've simply exported my smbroot (on alpha, it is my fileserver) and have samba running on an intel pentium4 box, also gentoo, kernel 2.6.0-ac12. Seems to work, eccept some locking problems. smbd[9450]: [2005/02/08 17:29:51, 0] locking/posix.c:posix_fcntl_lock(657) smbd[9450]:

I've been trying to find someone who can solve this problem. Unfortunately without any luck. Maybe someone on this site can help, here goes. I'm running TRU64 UNIX version 5.0a on my Alphaserver with Samba 2.07. When i try to access SWAT i am unable to login with the ROOT account. If i login with my own privileged account I am successful, but i only receive the basis 4 options for

Hi! I am trying to compile R-1.8.1 on an alphaserver running Tru64 Unix. I use the compilers cc,cxx and f77. After the compilation I try: make check and get the following message: Make: Cannot open /share/make/vars.mk. Stop. Does anyone have any suggestions on why? Regards Arne Gjuvsland

Over the last summer we took our home dir / applications servers for the 330 Win95 PCs that they service and attempted to replace them with a single AlphaServer 8200 (Digital Unix (OSF/1), Samba, 4GB RAM, 2x525Mhz cpus). The results were *not* good. In fact, it was terrible. We have since gone back to using the original 3 machines. My suspision is that the clients are making way too many

We are using rsync to maintain a warm mirror of our boot disks. I just updated to rsync 2.6.0 and noticed that the rsync runs are now getting errors when copying sockets. The system is running Tru64 5.1A pk 4 on an AlphaServer 4100. Is this a bug? Is there some way to not copy sockets or should I find all of them and add them to the exclude file? rsync was built using a straight ./configure

Dear openssh-unix-dev; I recently downloaded the tarball openssh-3.4p1 and built it for my Tru64 Unix ( OSF/1 ) 5.1a system. My configure statement is: ./configure --prefix=/usr/local/security/tools/openssh-3.4p1 \ --exec-prefix=/usr/local/security/tools/openssh-3.4p1 \ -with-ssl-dir=/usr/local/security/tools/openssl-0.9.6g \ -with-zlib-dir=/usr/local/compress/tools/zlib-1.1.3 \

Hi- I applied the privsep patch to Tru64 5.1A openssh 3.4p1 and it *almost* works. I get in from the client side and xauth is run, but in the meantime the server side disconnects. Running sshd in debug mode level 3 gives the following output: . . . debug1: session_input_channel_req: session 0 req shell debug1: fd 5 setting TCP_NODELAY debug1: channel 0: rfd 13

Samba 2.0.7 running on Compaq AlphaServer Tru64. Using smbclient to get files from a Windows 2000 Server. Nearly always we get a non-specific error code, sample below. When it does fail, it fails consistently. In the example below, whenever this particular get fails, it always fails at exactly the same point. The same is the case with other files and it doesn't seem to matter about the file

Hi- I built openssh-3.0p1 on a Tru64 4.0G without any problem. The system uses enhanced security, so the sia_* routines are used by sshd. Unfortunately, password authentication fails because sia_ses_authent() returns 0 in auth-sia.c. The thing is, the password is CORRECT; I verified this by inserting debugging statements before the call to sia_ses_authent(). The call to sia_ses_init()

Hi- Unfortunately, I just found out about the patch that was available for tru64 privsep. I was entirely unaware that there was a lack of support. Will the patch be considered for approval if it is applied to 3.4p1, or does it have to be done against -current? The reason I'm asking is that I have 3.4p1 working as is, so I know if I have a problem it is likely related to the patch and not

Hi, I've got a little problem with Dovecot IMAP. Everything works nice ( pam auth, ldap userdb, and so on ) BUT i need to uses quotas and it doesn't seem to work. I tried both ways : 1) user dovecot-ldap.conf with user_attrs, as it's shown on dovecot wiki ; 2) use the commandes "plugin {.........." in dovecot.conf But it didn't work. Strangely, when i try to use the

G'Day everyone, We are new to SAMBA and are having problems with initial configuration of SAMBA Version 1.9.18 on DigitalUnix 4.0B on a Digital AlphaServer 4100. If anyone can help us, we would be greatly appreciative. The installation and compilation all went OK. Following the points in DIAGNOSIS.TXT. Steps 1 to 6 all go OK. Step 7 says... TEST 7: -------