HDTenEightyP/NetNews huggingface dataset:
From: dswartz@redondo.sw.stratus.com (Dan Swartzendruber)
Newsgroups: comp.unix.aux,comp.sys.mac.comm
Subject: Bizarre modem behavior
Date: 22 Jul 92 00:48:33 GMT
Followup-To: comp.unix.aux
Organization: Stratus Computer, Software Engineering

Newsgroups: comp.unix.aux,comp.sys.mac.com
Subject: Modem session hanging
Summary: 
Followup-To: 
Distribution: world
Organization: Stratus Computer, Software Engineering
Keywords: 


I've got a bizarre problem which occurs unpredictable when I'm logged
in from home.  We have a bunch of Microcom modems, a couple of which
are high-speed (9600 baud).  The problem is that occasionally my login
session just freezes.  Nothing I type echoes, and I end up having to
hangup and try again.  I'm using Microphone 4.0, but I doubt that's
the problem, as I've had the same experience with two other terminal
emulators.  One interesting datum is that this only seems to happen
during a high-speed connect session.  My theory is that it has something
to do with flow-control, since occasionally I will respond to a posting
by following up, which invokes GNU emacs, with a screen full of text.
Sometimes, emacs will start out with a forward search command which
looks something like: "I-search: ^S^Q^S" or some variation.  It seems
like the high-speed modems don't allow user-typed ^S or ^Q (maybe they
are doing automatic XON-XOFF processing?).

They are configured (don't ask me why!) for 7-bit, odd parity.

Any ideas?


-- 

Dan S.
Newsgroups: comp.unix.aux
From: tromo@rice.edu (Tod Romo)
Subject: BullDozer problem in AUX 3.0 on Quadra 700
Keywords: bulldozer, bug, aux
Organization: Rice University, Houston, Texas
Date: Sun, 26 Jul 1992 21:41:33 GMT

Hello,
	We have been seeing a rather strange problem while running
TextEditor under AUX 3.0 on a Mac Quadra 700.  Periodically, TextEditor
will break spontaneously break sending us into MacsBugs.  When hitting
'es' the drive light then begins blinking, the GUI locks, but the cursor
is still active and changes from the std pointer to a bulldozer.
Hitting the `break` button again and yet another 'es' then gives full
control back over the mac.  We are using v6.2.2 of MacsBugs.  Has anyone
seen anything like this?  Thanks!


--
*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*
Tod D. Romo                     Department of Biochemistry and Cell Biology
713-527-8750 x3346 x3034        Rice University
713-285-5154 (FAX)              P.O. Box 1892
tromo@rice.edu                  Houston, TX  77251  USA
From: ctso@wam.umd.edu (CT Shock)
Newsgroups: comp.unix.aux
Subject: Re: Swap Space Kernel Param
Date: 21 Jul 92 13:02:59 GMT
Organization: University of Maryland, College Park

In article <841@jagubox.gsfc.nasa.gov> jim@jagubox.gsfc.nasa.gov (Jim Jagielski) writes:
>>Does anyone know what parameter he is taking about? And what value
>>I should add to it?
>
>This is most certainly wrong... You simply need to use '/etc/swap -a'
>to tell A/UX that you have more swap space on another disk... For example,
>if you added swap space on SCSI #3 (on slice 1, which is the default):
>
>	$ /etc/swap -a /dev/rdsk/c3d0s1

It is also important to note here that listing your new swap slice in 
/etc/fstab will not cause it to be added to system swap space with 
each boot, this must be done explicitly with the swap -a command.
I've found that a good place for it is at the end of the 
/etc/sysinitrc file.

	-Todd
Newsgroups: comp.unix.aux
From: jim@jagubox.gsfc.nasa.gov (Jim Jagielski)
Subject: Re: FMbackup version 1.0.4
Reply-To: jim@jagubox.gsfc.nasa.gov (Jim Jagielski)
Organization: NASA/Goddard Space Flight Center
Date: Thu, 30 Jul 1992 10:31:08 GMT

I further clarify things:

>I answer myself:

>>I note:

>>>I've just noticed that when using FMbackup, I get the "Backing up
>>>your file system cache..." window but NOT the "Finishing up..."
>>>one... The .Desktop.Z file is created Okay though...

>>Well, I discovered that it's an incompatibility with Moire... once I
>>took Moire out, all worked fine.

>Just a further followup... AfterDark version u -or- v work just fine.
>The problem with Moire seems to be that it "mucks around" with the Shutdown
>proc in the System heap and FMbackup is sensitive to that...

One last (I hope) note: Even with Moire installed, FMbackup (and Moire)
worked fine... FMbackup did what it was supposed to do as did Moire. The
only problem was that the "Finishing up..." window wasn't shown. If you
looked at the total amount of time that the "Backing..." and "Finish..."
windows are displayed (about 4 seconds) it's equal to the time that just
the "Backing..." window is shown shown when Moire is installed. Thus,
the backing up and the sleep functions (see /mac/bin/fsBACKUP) _are_ being
done, the window just isn't being updated.
-- 
==============================================================================
#include <std/disclaimer.h>

                Jim Jagielski                  NASA/GSFC, Code 734.4
          jim@jagubox.gsfc.nasa.gov             Greenbelt, MD 20771

           "The great scallop... this tatty, scrofulous old rapist,
               is second in depravity only to the common clam."
Newsgroups: comp.unix.shell
From: Harald.Eikrem@delab.sintef.no
Subject: Re: tcsh in the future - what should it be like?
Organization: SINTEF DELAB, Trondheim, Norway.
	<1992Jul27.031238.10376@chpc.utexas.edu>
	<1992Jul27.215202*Harald.Eikrem@delab.sintef.no>
	<smr.712419130@hitkw14>
Date: 31 Jul 92 01:09:03

! >! I'd like to see a history mechanism that works like VMS' RECALL, i.e. 
! >! type something like !vi .cs  and get the last vi command that edits 
! >! .cshrc.  Simple, powerful concept; only a single command to learn. 
! 
! >It's there.  You just need to try.
! 
! care to enlighten us?? or are you still telling failed entrepreneurs
! that there is a pot of gold at the end of every rainbow?

You're absolutely right.  Like in csh, a history match (event) string does
not span over spaces, and definitely shouldn't ('you know why?).  One may
probably wish that the case where the history expansion appears absolutely
first on a command line, and where it is the sole one on the entire line,
for practical reasons be treated almost like a combination of a history-
search-backward and implicit newline.

However, I dont really see the wonderful reasons to deviate from csh on
this, since there are so many other powerful consepts in tcsh which you
should rather learn.  If you find it so extremely hard to get rid of
antique csh habits, then what's the point...   Csh history substitution is
NOT really a *command* in itself, it is a feature that may appear in multi-
ple instances on a command line.

However, there is one other case where spaces in a history match does make
sense, i.e. !?aaa bbb ccc?, it doesn't work, probably because the old csh
matching algoritms are so primitive.

! >! Also, the history list should save a command only if it is different 
! >! from the last one.
! 
! >No way.  You will be able to reach the next *different* command in the
! 
! DISAGREE!
! if you are developing something, and you get into a debug mode, the
! usual sequence of commands goes something like:
!     edit
!     compile
!     run ( or debug )
!     edit
!     compile
!     ... ( ad infinitum )
! 
! if after doing this 30 times, the last 100 entries in your history are
! the same three commands over and over, what if you then want to do

Have you ever seen a windowing environment?

! Also, I would really love a 'merge_histories' feature, this is relevant
! only if you have many tcsh's running at the same time, because when I
! quit my XWindows session, by dumb luck or whatever, the last tcsh to
          ^^^^^^^^^^^^^^^^somehow answers the question above, I guess.....

! save the history seems to be the one I used the least, with all the
! most boring, and least used commands in the history, any solutions?
! anyone come up with some sort of .logout hack?

No suggestions.  What exactly do you mean with "merge histories"?  I imagine
the last 100 or so commands from 5-10 shells, intermixed, but will it ever
constitute interesting stuff?  Oh sure, you might want to use it for
documentational purposes........:)

  ~~harald E.
Newsgroups: comp.unix.shell
From: chintam@alw.nih.gov (Niranjan Chintam)
Subject: check for time stamp in ksh
Organization: National Inst. of Health, DCRT, CSL
Date: Fri, 24 Jul 1992 19:21:27 GMT

Is there a simple script which can check if a particular file has been updated on a give day.

I have written the following script is there any other way to do the same.

#!/usr/bin/ksh

   stamp=`ls -l $filename | awk '$7 ~ /.*:.*/ {print $5$6}'`
   today=`date | awk '{print $2$3}'`
   if [ "$stamp" != "$today" ]; then
      ..........
      ...........
      ...........
   fi


Thanks 


-- Niranjan Chintam                                            chintam@alw.nih.gov
                                               National Inst. of Health, DCRT, CSL
From: adh@cbnewsi.cb.att.com (andrew.d.hay)
Newsgroups: comp.unix.shell
Subject: Re: ksh prompt (PS1) and cd
Date: 21 Jul 92 13:20:16 GMT
Distribution: ba
Organization: AT&T

In article <l5n3efINN3g7@exodus.Eng.Sun.COM> opensys@sunvi.Eng.Sun.COM (Anil Visariya) writes:
"
"Using ksh, how can one alias "cd" to change directory as well as
"to set PS1 to $PWD.
"
"I tried:
"alias cd="cd; PS1=$PWD" 
"but didn't work.

don't bother with an alias.  i do
export UNAME=$(uname -n) LOGNAME=$(logname) PS1='$UNAME ~$LOGNAME ${PWD##*/}/ '
in my .profile.  note the SINGLE quotes.
it may seem roundabout, but it's efficient.  you probably don't need
uname or logname, but at one time i had logins on 13 machines, some
as different user ids!  the pwd stuff gives just the current directory,
not the whole path.

"Also I frequently use "ls" command as follow:
"ls -la *mystring*
"to get list of files whose name contain 'mystring' in its name.
"How can I create an alias for the same?
"
"I tried: 
"alias llnew="ls -la '*'\!*'*' "
"but didn't work.

alias myls='ls -la *mystring*'
single quotes again.

"Any help?
"thanks

in general: double quoted stuff is evaluated at alias creation, single
quoted stuff at alias execution.

"Anil 


-- 
		+--------------------------------------------------------------+
Andrew Hay	|         I want to lie, shipwrecked and comatose -	       |
a_d_hay@att.com	|              Drinking fresh mango juice...		       |
		+--------------------------------------------------------------+
Newsgroups: comp.unix.shell
From: xzs0886@rchland.vnet.ibm.com (Chris Johnson)
Subject: csh -> ksh translation?
Date: Wed, 29 Jul 1992 16:34:14 GMT
Distribution: na
Reply-To: ceej@cup.portal.com
Disclaimer: This posting represents the poster's views, not necessarily those of IBM
Organization: Broadway & Seymour
Keywords: translat csh ksh

Hello, is anyone aware of a method or tool to provide translation between ksh and csh?
I have a lot of (somewhat basic) csh scripts that I need to be able to translate to 
ksh... The translation from ksh to csh is less important-- my main interest is generating
ksh scripts from csh scripts.

Any information is appreciated; please either post here or respond to ceej@cup.portal.com
since this account does not have internet mail access.

Thank you.

-- 
c. e. johnson/ e-mail: please use ceej@cup.portal.com
Newsgroups: comp.unix.shell
From: jpr@jpradley.jpr.com (Jean-Pierre Radley)
Subject: Re: setting variable from script to current environment??
Organization: Unix in NYC
Date: Wed, 22 Jul 1992 01:48:34 GMT

In article <1992Jul21.070212.16485@gbrmpa.gov.au> wayne@gbrmpa.gov.au (Wayne Amisano) writes:
>Hi,
>
>I am trying to write a script to set an environment variable in
>my tcsh environment.  I could use an alias to do it, but would
>much rather do it from a script.  What i need to do is, run a
>script to change the value of one environment variable, but
>every time i do this, it changes the variable in the spawned
>process, but it then disappears when it dies.
>
>I need this variable to remain around!!  Any ideas would be welcome.

It is an IMPERATIVE in unix that a child process CANNOT change the environment
of its parents. You should seek to understand this why this is necessary.

If you have a script that sets variables, running the script will never set
those variables for the calling shell, its parent.

If you "source script" (csh, tcsh), or ". script" (sh, ksh), then yes, you can
set variables that way.

Running a script spawns a new process. Sourcing a script interprets its
commands within the current shell just as if you'd typed them from the shell
prompt.
-- 
Jean-Pierre Radley   Unix in NYC   jpr@jpr.com   jpradley!jpr   CIS: 72160,1341
From: rjackson@gmuvax2.gmu.edu (Richard L Jackson Jr)
Newsgroups: comp.unix.shell
Subject: csh/ksh comparison summary. Thanks!
Date: 24 Jul 92 14:26:05 GMT
Organization: George Mason University, Fairfax, Va.

Thank you for your responses on my 'csh/ksh comparison questions?  This
group has been the most responsive of all other groups I have delt with.
I am including a summary of responses to my three questions.  One point
seemed to be clear; use a more advanced interactive shell (e.g., bash, zsh,
tcsh).  The following are people kind enough to offer a response.  Please
excuse me if I accidentally left your name out.

Tim Shelling	(tim@mal-s1.gatech.edu)
Colum Mylod	(cmylod@nl.oracle.com)
James Yorton	(yorton@turtle11.rtsg.mot.com)
Dave Anderson	(dla@westford.ccur.com)
Bob Halloran	(rkh@d1.att.com)
Mike O'Connor	(mjo@fmsr17.srl.ford.com)
David Wagner	(dawagner@phoenix.Princeton.edu)

A summary/collection of responsives follows:

In article <1992Jul21.183727.20364@gmuvax2.gmu.edu>, rjackson@gmuvax2.gmu.edu (Richard L Jackson Jr) writes:
|> I did a simple comparison of CSH and KSH.  I am asking this
|> group for solutions to csh feature that ksh appears to lack.
|> I am using ULTRIX 4.1, VAX 8530.
|> 
|> 1) set filec or file completion

In ksh, using vi-style command line editing, try

<ESC>* or <ESC>\ 

where <ESC> is the ESCAPE key.
There is a slight difference.  I'm not a tcsh user, but users tell
me that <ESC>\ is quite similar to tcsh's file name completion.

In ksh, using emacs-style command line editing, try

<ESC><ESC>

|> 
|> 2) concurrent sessions inadvertently use the same history
|>    file.  Appending a pid to the history file at login may help
|>    but there is no logout facility to remove the file.
|> 

How about using a different history file for each tty?
How about something like:

tty=`tty`
export HISTFILE=~/.history_${tty#/dev/}

I suggest you clean up the history files periodically, or you
may have a lot of them laying around.  It's like politics,
some people want it one way, some the other.  Neither is wrong.

I use the same history file name (".sh_history"), but explicitly remove 
it in my .profile just prior kicking off my .kshrc.  This unlinks any 
visible versions of ".sh_history" -- however the "removed" versions are 
still available to the previous invocation(s) of ksh (as temporary files). 

|> 3) how does one invoke a .logout script at ksh exit?
|> 

How about putting this at the top of your .profile:

trap '[[ -x ~/.logout ]] && ~/.logout' 0 1 15

which will execute your .logout script (if it's executable)
on the receipt of certain signals.  Do a chmod +x ~/.logout too.
You can then put anything in .logout, including removal of
your history files.
From: navarra@casbah.acns.nwu.edu (John Navarra)
Newsgroups: comp.unix.shell
Subject: Re: file name completion for ksh?
Date: 23 Jul 92 08:21:08 GMT
Distribution: na
Organization: Northwestern University, Evanston Illinois.

In article <1992Jul23.033602.19925@news.eng.convex.com> tchrist@convex.COM (Tom Christiansen) writes:
>From the keyboard of sjs@netcom.com (Stephen Schow):
>:The ksh is hands down the best.  As the last response showed, there is usually
>:a way to do it in the ksh.  In addition, the ksh has tons of over features
>:that none of the other shells can even touch.  
>
>Down boy.  That's overkill.  Read the tcsh man page some day.
>
	And zsh has even more features! Ruf! Ruf!

-tms
Newsgroups: comp.unix.shell
From: messina@netcom.com (Tony Porczyk)
Subject: Re: Sort problem . .
Date: Fri, 31 Jul 92 06:45:49 GMT
Organization: Messina Software

Tom Christiansen <tchrist@convex.COM> writes:
>I am constantly incensed by massively
>UNIX-ignorant programmers who inflict brain-damaged software on 
>the rest of us who actually try to use it.

Yep, I guess this whole discussion about how to patch up a utility so
it produces exactly what we want is because it was the best possible
way to do it.  You know, this is really amusing.  Have you ever though
of actually treating this as another solution, renaming the changed
code and using it when it is called for, or would it be too much to
ask to use something without "wrappers"?   What I mean is:  Are you
sure there is always only ONE way to do things?
By no means I am trying to suggest closed-mindness, I am just amused
at your single-track approach to doing things.
To your remark - noone is trying to inflict anything on you, that was
a suggestion for creating a tool to this a particular task.  I suppose
if you're been trained for 20 years at using a wrapper, then a wrapper
it is...
I guess as long as it makes you feel non-ignorant and important, it
does the job.

t.
Newsgroups: comp.unix.shell
From: boyd@prl.dec.com (Boyd Roberts)
Subject: Re: Sort problem . .
Organization: Digital Equipment Corporation - Paris Research Laboratory
Date: Wed, 29 Jul 1992 20:54:22 GMT

In article <zynm!yh.messina@netcom.com>, messina@netcom.com (Tony Porczyk) writes:
> to:
> 
> fprintf(stderr, "%s COMMAND\n", hdr);
> 

Yeah, right.  Information to stderr.


Boyd Roberts			boyd@prl.dec.com

``When the going gets wierd, the weird turn pro...''
Newsgroups: comp.unix.shell
From: esh@lithium.tekbspa.com (Edward S. Hirgelt)
Subject: Re: Where does the sugar go? (was Re: Sort problem )
Organization: Direct Interfaces Corporation @ Teknekron
Date: Fri, 31 Jul 1992 18:17:23 GMT


On 31 Jul 92 03:30:28 GMT,
chip@eniac.seas.upenn.edu (Charles H. Buchholtz) said:
Charles> Sender: news@netnews.upenn.edu
Charles> Nntp-Posting-Host: eniac.seas.upenn.edu

Charles> So, folks, what's the verdict?  Output goes to stdout, preferably
Charles> arranged in lines and fields for easy filtering.  Error messages and
Charles> diagnostics (abnormal stuff) goes to stderr.  Where should the sugar
Charles> go?  stdout?  /dev/tty?  /dev/null?  >&3?

Actually, I think it should go to stdout as well. To be filterable, the
headers and other `sugar' ought to disappear. The right answer (for the
future) is that the command ought to have a flag to disable headers.

You don't really want to route that to a different file descriptor
because the command would then have to worry about synchronizing the two
descriptors to keep the non-filtered output looking good. ps could use a
-noheader flag or something that tells it to forget the header this
time, I want to play with the output.

Ed
--
Ed Hirgelt			esh@tss.com
Direct Interfaces Corporation
San Jose, Ca.
Newsgroups: comp.unix.shell
From: 911288c@ace.acadiau.ca (HON (EDWIN) KIN CHUNG)
Subject: Help in find address
Organization: Acadia University
Date: Wed, 22 Jul 1992 19:42:29 GMT

Dear friends,
		Would anybody help me to find out how to find out the 
	numerical address of the site
		Like @dragon.acadiau.ca
		is   179.11.12.1
	Any program to do this ,Help me Please !!
							EDwin
Newsgroups: comp.unix.shell
From: chet@odin.INS.CWRU.Edu (Chet Ramey)
Subject: Re: Sort problem . .
Organization: Case Western Reserve University, Cleveland, OH (USA)
Date: Fri, 31 Jul 92 12:30:24 GMT

In article <1992Jul30.094428.17460@prl.dec.com> boyd@prl.dec.com (Boyd Roberts) writes:

>Standard error is for _errors_.

Gee, like the /bin/sh prompt?  And the rest of the sh messages?
-- 
``The use of history as therapy means the corruption of history as history.''
	-- Arthur Schlesinger

Chet Ramey, Case Western Reserve University	Internet: chet@po.CWRU.Edu
From: keesh@wsinti01.info.win.tue.nl (Kees Huizing)
Newsgroups: comp.unix.shell
Subject: How to send a signal to a shell script? (ANSWER)
Date: 22 Jul 92 12:10:11 GMT
Reply-To: keesh@info.win.tue.nl

Thanks to Michael Cook <mcook@merlin.dev.cdx.mot.com>, I know the answer to
my question. 

Summary of the problem:
A signal is sent to a shell script with process id 12345 and job number 1 (in
csh) that is currently executing a sleep command.
The signal USR1 seems not to arrive when sent with the command:

kill -30 12345

It does arrive, however, when sent with

kill -30 %1

How is this possible, and how can I interrupt the script in case the job number
is not accessible and I don't want to signal the sleep process explicitly?

The answer is that the first command sends a signal to the script process
*only*, whereas the second sends it to the process *group* (all processes
dependent on 12345).  As long as the sleep is executing, the shell script
process is suspended and buffers the incoming signals. And the intention was
abort the sleep process and ahndle the signal immediately.

Solution: use 

kill -30 -12345

This to me unknown (SysV?) feature of the kill command sends the signal to
every member of the process group. It works on my Sun. 

Thanks to everyone who thought about this, especially to Michael.
Kees

-- 
Kees Huizing - Eindhoven Univ of Techn - Dept Math & Comp Sc - The Netherlands
e-mail: keesh@win.tue.nl   telephone: +31-40-474120    fax: +31-40-463992
Newsgroups: comp.unix.shell
From: Tom Christiansen <tchrist@convex.COM>
Subject: Re: Shell Scipt Security
Originator: tchrist@pixel.convex.com
Reply-To: tchrist@convex.COM (Tom Christiansen)
Organization: CONVEX Realtime Development, Colorado Springs, CO
Date: Sat, 25 Jul 1992 13:34:33 GMT
X-Disclaimer: This message was written by a user at CONVEX Computer
              Corp. The opinions expressed are those of the user and
              not necessarily those of CONVEX.

From the keyboard of ian@horse.UUCP ( as in Bunny):
:Whether that be a "shell compiler" or some other mechanism I am open
:to advice. We need to protect our time and investment in this little project 
:and stop it from being copied and stolen.    

Rewrite it in inflexible C, then: lock it in stone and throw away the
key.  Now your effort is safe.  A shell compiler would buy you negligible
speed and little security, since it would still call the base programs,
which can be trivially traced.

Seriously, put a copyright notice on the top of the source.  
That's what AT&T does.

:find / -type f -print | xargs -t ls -qb 2>/dev/null | grep '\\'

No option b
usage: ls [-acdfghilqrstu1ACHLFR] name

It also has the problem of not working if someone has done this to you:

    mkdir "/tmp/etc^J"
    cd $!
    touch passed


Furthermore, you've assumed an xargs command, not supplied 
on some systems I run on.  I suggest instead this:

    #!/usr/bin/perl
    require 'find.pl';
    &find('/');
    sub wanted { /\001-\037\177-\377/ && print("-->$name<--\n"); }


--tom
-- 
    Tom Christiansen      tchrist@convex.com      convex!tchrist
I do not feel obliged to believe that the same God who has endowed us
with sense, reason, and intellect has intended us to forgo their use.
                -- Galileo Galilei
Newsgroups: comp.unix.shell