Xref: utzoo comp.unix.ultrix:2431 comp.sys.dec:2381 Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!samsung!uunet!acd4!mjb From: mjb@acd4.UUCP ( Mike Bryan ) Newsgroups: comp.unix.ultrix,comp.sys.dec Subject: Re: DECserver 200 3.0 Software Fun Message-ID: <1990Jan2.151439.18234@acd4.UUCP> Date: 2 Jan 90 15:14:39 GMT References: <9184@cbmvax.commodore.com> Reply-To: mjb@acd4.UUCP ( Mike Bryan ) Organization: Applied Computing Devices, Inc., Terre Haute, IN Lines: 52 In article <9184@cbmvax.commodore.com> grr@cbmvax.commodore.com (George Robbins) writes: >One of the things that came with my 5810 was "DECserver 200 Release 3.0" >software. >One thing that isn't mentioned in the release notes is that the reponse >to the remote console port (ultrix ccr command) is much better than with >the 2.0 software. It seemed so much better that I decided to see if I >could use a script to change a bunch of setup stuff, rather than doing it >by hand. > >Amazingly enough, it worked fine! Below is the script I ended up with, >it's pretty obvious how to modify it to execute other command sequences... [Omitted example showing interspersed echo and sleep commands piped into ccr.] I just tried the same thing on Ultrix 3.1, but with DECServer 2.0 software, and it works perfectly! After messing around with it a bit, I discovered that the sleeps aren't needed at all. I have a file with DECServer commands such as this: ccr.commands: access mjb show server show sessions all show users (That's six lines total, including the first blank line used to get the initial "#" prompt for the remote console.) You can then issue the command "cat ccr.commands | ccr DSRV04", and it will work perfectly. Use of the pipe is the important thing, simple input redirection, such as "ccr DSRV04