INFO-VAX Tue, 04 Sep 2007 Volume 2007 : Issue 485 Contents: Re: ANN: VMS Mosaic 4.2 Re: cannot ssh login with expired password Re: If PL/I is the king of languages... Re: If PL/I is the king of languages... Re: is this a race condition? Re: Nasty? was: SSH login welcome message? VMS Audio Update - Episode 11 ---------------------------------------------------------------------- Date: 3 Sep 07 14:59:15 EDT From: cook@wvnvms.wvnet.edu (George Cook) Subject: Re: ANN: VMS Mosaic 4.2 Message-ID: In article <2beae$46db76c0$cef8887a$17501@TEKSAVVY.COM>, JF Mezei writes: > George Cook wrote: >> Release 4.2 of VMS Mosaic is now available at >> ftp://alpha.wvnet.edu/mosaic/mosaic4_2.zip > > > How dare you release this on a sunday during Labour day (long weekend in > Canada). I'd had to disrupt my rest after a very long bike ride to > download it, unzip it and type @make_mosaic "" "UCX" and wait a few > minutes for it to compile cleanly and give it a try. Completely > disrupted my evening :-) :-) :-) :-) :-) :-) It is normally best to not specify the TCP/IP package. The build usually figures it out properly. V4.2 will fail at startup for first time Mosaic users (the problem will also occur if an old preference file is rewritten using V4.2). There is a corrected PREFS.C file for the [.SRC] directory at ftp://alpha.wvnet.edu/mosaic/prefs.c I also updated all the prebuilt executables at ftp://alpha.wvnet.edu/mosaic/exe/ George Cook WVNET ------------------------------ Date: 3 Sep 2007 20:22:44 +0200 From: peter@langstoeger.at (Peter 'EPLAN' LANGSTOeGER) Subject: Re: cannot ssh login with expired password Message-ID: <46dc6d14$1@news.langstoeger.at> In article <20070903154924.GA48876@mech-aslap33.men.bris.ac.uk>, Anton Shterenlikht writes: >On Mon, Sep 03, 2007 at 05:59:33AM -0700, Jose Baars wrote: >> It is expected behaviour ( known bug?) on older versions of TCPIP >> services. >> On TCP/IP 5.6 (probably since 5.5) it will allow you to login with an >> expired password by default, >> but you should check SSHD2_CONFIG which says in TCPIP 5.6: >> >> # V5.5-04: Correct default for AllowVmsLoginWithExpiredPw >> # AllowVmsLoginWithExpiredPw yes >> # AllowNonvmsLoginWithExpiredPw no >> # UserLoginLimit -1 > >Jose, many thanks > >Yes I'm running TCPIP 5.6 on VMS 8.3. I uncommented these lines > ># V5.5-04: Correct default for AllowVmsLoginWithExpiredPw > AllowVmsLoginWithExpiredPw yes > AllowNonvmsLoginWithExpiredPw yes > UserLoginLimit -1 > >but still no luck. Now I'm being told that the password has expired, >but when I change it, the access is still denied: The default has changed and that means, that you cannot enable what is already enabled. You can only disable it ;-) What client do you use? We had to upgrade PuTTY to get the password change feature (IIRC it was 0.59 instead 0.58 - 0.60 is current) So, check your client and maybe upgrade... -EPLAN PS: PuTTY 0.58 and before was no problem with TCPware SSH and expired passwords (but then again, TCPware logs out after a successful pwdchg and you have to reconnect with the new password) -- Peter "EPLAN" LANGSTOEGER Network and OpenVMS system specialist E-mail peter@langstoeger.at A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist ------------------------------ Date: Mon, 03 Sep 2007 12:02:52 -0700 From: "Tom Linden" Subject: Re: If PL/I is the king of languages... Message-ID: On Sun, 02 Sep 2007 20:04:34 -0700, Ron Johnson wrote: > On 09/02/07 21:11, Tom Linden wrote: >> On Sun, 02 Sep 2007 18:47:48 -0700, Ron Johnson >> wrote: >> >>> On 09/02/07 09:15, Tom Linden wrote: >>>> On Sat, 01 Sep 2007 23:32:36 -0700, Mark Daniel >>>> >>>> wrote: >>>> >>>>> Ron Johnson wrote: >>>>>> On 09/02/07 00:17, Mark Daniel wrote: >>>>>> >>>>>>> Ron Johnson wrote: >>>>>>> >>>>>>>> ... why is the web site powered by not-the-king-of-languages? >>>> >>>> It is in a way, financially. But even if I were to write a web >>>> server in >>>> PL/I why would I? Mark has done such a fine job with WASD, and it is >>>> well written. I frankly don't understand why HP doesn't throw Apache >>>> and >>>> promote WASD. I have Apache running on a Tru64 system, or did, and >>>> there >>>> is no comparison. >>> >>> While "why didn't he write the web server in PL/1?" *did* >>> momentarily cross my mind, that was quickly discarded for practical >>> reasons. >>> >>> What I was really thinking more of was the Python-powered pages. >> >> The thought cross my mind, but Jean-François Piéronne had already done >> the trail blazing so there was no point to reinvent the wheel. > > Mmm-hmmph. So, you're saying that PL/1 is not adequate to the task? > Such a great language shouldn't need much wheel-reinventing, right? > Why recode an app that is working? -- PL/I for OpenVMS www.kednos.com ------------------------------ Date: Mon, 03 Sep 2007 12:05:05 -0700 From: "Tom Linden" Subject: Re: If PL/I is the king of languages... Message-ID: On Mon, 03 Sep 2007 04:41:16 -0700, FrankS wrote: > On Sep 2, 10:11 pm, "Tom Linden" wrote: > > > Tom, > > Just out of curiosity, what language are the PL/I compiler and run- > time libraries written in? > > Your web site mentions that you do not have a native Itanium compiler > available, but the run-time library is available as a native shared > image. That suggest to me that perhaps the compiler and run-times are > written in different languages. > Compiler is mostly PL/I and TBL (Table Building Language) runtime is VAX macro and recoded in C and some Bliss on Alpha and (I didn't do, Digital did) -- PL/I for OpenVMS www.kednos.com ------------------------------ Date: 3 Sep 2007 14:45:30 -0500 From: cornelius@encompasserve.org (George Cornelius) Subject: Re: is this a race condition? Message-ID: In article , koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes: > In article <1187830870.915352.211590@e9g2000prf.googlegroups.com>, "dpm_google@myths.com" writes: >> 23 years ago, fresh out of university, my first job was maintaining >> FORTRAN on a VAX. Last month I started a new job, and I am maintaining >> FORTRAN on a VAX (sigh). The operating-system part is nice, the language >> is not. Check this out: [...] > > I see nothing inherently wrong with the two I/Os as written, > but the logic seems faulty. If the IO$_READVBLK fails to submit > or fails to complete (STATUS is bad or IOSB(1) is bad) then the > outer loop will never terminate. Both of these should be terminal > conditions. > > I'd add an ELSE to both of those tests and call LIB$SIGNAL just > as the program does if the IO$_WRITEVBLK fails. Faulty logic seems to be the crux of the matter. That plus the sharing of the IOSB and the use of asynchronous completion in a QIO where it may not even have been intended. I should mention that I posted a comment about Fortran optimization and asynchronous I/O from another Usenet account, and while it did seem to show up on some news servers it is not present on my usual server, so I'll state this once more: asynchronous I/O generally involves passing addresses to subroutines that then return while retaining that information in order to later modify the associated data. Standard compiler behavior is to assume no asynchronous modification of local variables will occur. Current compilers include a VOLATILE directive to address this, just as in other languages such as C. You either need to use something of that sort, or you need a command line switch, perhaps /NOOPTIMIZE, if you want to properly deal with asynchronous I/O completion in Fortran [not to mention the usual reentrancy considerations if you choose to field AST's]. If you don't take these steps you're likely to be rather frustrated by your program's inability to behave in a predictable / logical manner. -- George Cornelius cornelius(at)eisner.decus.org cornelius(at)mayo.edu ------------------------------ Date: Mon, 03 Sep 2007 12:40:47 -0700 From: Fred Bach Subject: Re: Nasty? was: SSH login welcome message? Message-ID: VAXman- @SendSpamHere.ORG wrote: > In article <5j5rbpF3sv1a5U1@mid.individual.net>, bill@cs.uofs.edu (Bill Gunshannon) writes: >> >> In article , >> Malcolm Dunnett writes: >>> VAXman- @SendSpamHere.ORG wrote: >>> >>>> If you want to know about nasty, being that you are a relative newcomer >>>> to comp.os.vms, I suggest you research one Carl J. Lydick. While c.o.v. >>>> sometimes gets hostile and vituperations fill the threads, it is nothing >>>> at all like the when Carl would chime in with his castigatory vitrolic >>>> rhetoric! >>> Carl was also a great resource and could be very helpful if you >>> asked what he deemed a worthy question. All things considered I >>> miss Carls postings. >>> >>> Lets not forget Ehud Gavron either, there was a time when c.o.v. >>> flamage was rated in units called the Gavron. >> Now there is a name I haven't seen in a dog's age although I still often >> wonder what became of him. > > One of the last times I saw Ehud in person was at one of the last national > DECUS events -- TGV was still a company then. > > I heard he sold a domain name (wallstreet.com) for a significant amount of > money and is now living on easy street... figuratively. A google search > of Ehud Gavron and wallstreet.com shoudl turn up some articles. > Yeah, Carl and I used to get into some good discussions but I always kept him civil in our discussions. I just had a way to do it. But I always thought Ehud would go big someday .... So it's true! That's why I don't see him on this newsgroup any more. I believe I owe Ehud a bottle of Anchor Steam beer. I had looked forward to having it with him and having a good discussion of obfuscated VMS DCL coding at the same time.... I got this from google: http://www.wired.com/techbiz/media/news/1999/04/19285 . Fred Bach . music at triumf dot c a . ------------------------------ Date: Mon, 03 Sep 2007 11:13:20 -0700 From: IanMiller Subject: VMS Audio Update - Episode 11 Message-ID: <1188843200.565623.141780@57g2000hsv.googlegroups.com> It's been a while but VMS Audio Update #11 is now available. In this episode, we cover some of the news highlights from the last six weeks since the last update, and get some insight on testing from Colin Butcher. http://www.openvms.org/stories.php?story=07/09/03/3081144 ------------------------------ End of INFO-VAX 2007.485 ************************