Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!haven!adm!news
From: postmaster@ecf.ncsl.nist.gov (SMTP MAILER)
Newsgroups: comp.unix.questions
Subject: Mail Delivery Problem
Message-ID: <24116@adm.BRL.MIL>
Date: 13 Aug 90 11:24:50 GMT
Sender: news@adm.BRL.MIL
Lines: 317


 ----Reason for mail failure follows----
Sending mail to host ecf.ncsl.nist.gov :
  Fatal reply code to command 'RCPT TO:<ise.ncsl.nist.gov@ecf.ncsl.nist.gov>':
  550 User "ise.ncsl.nist.gov" Unknown.


 ----Transcript of message follows----
Date: 13 Aug 90 06:38:00 EST
From: info-unix@BRL.MIL
Subject: INFO-UNIX Digest  V10#115
To: "ise.ncsl.nist.gov" <ise.ncsl.nist.gov@ecf.ncsl.nist.gov>

Return-Path: <unixinfo-request@ecf.ncsl.nist.gov>
Received: from SEM.BRL.MIL by ecf.ncsl.nist.gov with SMTP ; 
          Mon, 13 Aug 90 06:37:59 EST
Received: from SEM.BRL.MIL by SEM.BRL.MIL id ab02332; 13 Aug 90 6:01 EDT
Received: from sem.brl.mil by SEM.BRL.MIL id aa02326; 13 Aug 90 5:45 EDT
Date:       Mon, 13 Aug 90 05:45:26 EST
From:       The Moderator (Mike Muuss) <Info-Unix-Request@BRL.MIL>
To:         INFO-UNIX@BRL.MIL
Reply-To:   INFO-UNIX@BRL.MIL
Subject:    INFO-UNIX Digest  V10#115
Message-ID:  <9008130545.aa02326@SEM.BRL.MIL>

INFO-UNIX Digest          Mon, 13 Aug 1990              V10#115

Today's Topics:
                Re: 'foo bar' <- What's the meaning of?
                  Re: How to tell if a process exists
                        System VR4/i386 - when ?
                         Re: Millisecond clock
                        Re: Suid script security
                          Re: Working with sed
                       fuser for sco unix v3.2.1
                          Re: the f2c program
                     Re: Timeout on shell command.
-----------------------------------------------------------------

From: George Turczynski <george@hls0.hls.oz>
Subject: Re: 'foo bar' <- What's the meaning of?
Keywords: foo bar
Date: 10 Aug 90 00:28:36 GMT
To:       info-unix@sem.brl.mil

As you can see from the subject line, "foo bar" came from
"fubar".

I think this MUST be in one of the FAQ lists, no ?

Ich hoffe dass das genug klar ist.

-- 
| George P. J. Turczynski.          |---------------------------------------------------- 
| Computer Systems Engineer.        | ACSnet: george@highland.oz | I can't speak for the |
| Highland Logic Pty. Ltd.          | Phone: +61 48 683490       | company, I can barely |
| Suite 1, 348-354 Argyle St        | Fax:   +61 48 683474       | speak for myself...   |
| Moss Vale. NSW. Australia. 2577   |---------------------------------------------------- 

-----------------------------

From: Sam Bassett RCS <samlb@pioneer.arc.nasa.gov>
Subject: Re: How to tell if a process exists
Date: 11 Aug 90 06:20:20 GMT
Sender: news@amelia.nas.nasa.gov
To:       info-unix@sem.brl.mil


	Ooops -- yer right -- my mistake.  Sorrreee.....


Sam'l Bassett, Sterling Software @ NASA Ames Research Center, 
Moffett Field CA 94035 Work: (415) 604-4792;  Home: (415) 969-2644
samlb@well.sf.ca.us                     samlb@ames.arc.nasa.gov 
<Disclaimer> := 'Sterling doesn't _have_ opinions -- much less NASA!'

-----------------------------

From: Per Andersson <perand@admin.kth.se>
Subject: System VR4/i386 - when ?
Date: 11 Aug 90 12:35:19 GMT
To:       info-unix@sem.brl.mil


Has anybody seen a sold rel4 for the 386 ? Can anybody quote a price ?
This has to be the best vapourware of 1990. In January agents promised
'it would be for sale in a couple of weeks'. The market is probably
screwed because it's too many home systems and too many poor system
managers which doesn't make good customers. So why worry their heads 
with all this new stuff ?. SCO has no plan when r4 will be considered,
and Interactive just released 2.2. Why not concentrate on getting the
enhancement working on r4 instead ? r4 working on ICLs machines doesn't 
help one bit because the big 386 market couldn't afford one, and should
better buy a Sparcstation SLC, 'cos thats not more expensive than a top
end 386, and runs DOS programs, just like the 386.

WHEN WILL I BE ABLE TO BUY SYSTEM V rel 4 FOR THE i386 ?

Per
-- 
---
Per Andersson
Royal Institute of Technology, Stockholm, Sweden
perand@admin.kth.se, @nada.kth.se 

-----------------------------

From: Guy Harris <guy@auspex.auspex.com>
Subject: Re: Millisecond clock
Keywords: HP-UX SYSV
Date: 11 Aug 90 20:55:54 GMT
To:       info-unix@sem.brl.mil

>The folowing program for millisecond sleep works under HP-UX SYSV,  so
>it should work on an ATT (serious finger crossing :-).

Crossing the fingers is a good idea here.  "Xxx works under HP-UX SYSV,
therefore it should work on an [arbitrary] ATT [System V release]" isn't
a valid deduction.  While some systems, including HP-UX, have
"setitimer()", which your program uses, vanilla AT&T System V releases
prior to S5R4 don't have it.

-----------------------------

From: Guy Harris <guy@auspex.auspex.com>
Subject: Re: Suid script security
Date: 11 Aug 90 21:01:33 GMT
To:       info-unix@sem.brl.mil


 >Now, what if the name of the very shell script were e.g. "-i"? Wouldn't that
 >give a nice exec?
 >
 >	execl("/bin/sh", "sh", "-i", (char *) 0);
 >
 >So link the script to a file named "-i", and voila!
 >Yes, one needs write permission somewhere on the same device, if one's
 >operating system doesn't support symbolic links.
 >
 >What about the csh command interpreter? Well, 4.2BSD provides us with a csh
 >which has a NEW option: "-b"! Its goal is to avoid just the thing described
 >above:

Whereas the Bourne shell already has an option whose effect is to avoid
the thing just described above - "-".  Yup, just a dash by itself, as in

	#! /bin/sh -

>the mnemonic for `b' is `break';

To quote the C shell source code:

		case 'b':               /* -b   Next arg is input file */
			batch++;

so I don't think the mnemonic was intended to be "break"....

-----------------------------

From: Guy Harris <guy@auspex.auspex.com>
Subject: Re: Working with sed
Date: 11 Aug 90 21:04:08 GMT
To:       info-unix@sem.brl.mil


 >On SysV and SunOS 4.0.3_EXPORT (therefore probably BSD systems in
 >general??)

Nope.  SunOS picked "dirname" up from S5, not from BSD.

-----------------------------

From: Philip Hall <phil@dprmpt.uucp>
Subject: fuser for sco unix v3.2.1
Keywords: fuser, sco v3.2.1
Date: 11 Aug 90 23:59:49 GMT
To:       info-unix@sem.brl.mil

I have been trying to port the fuser.c source that can be found
on uunet to the sco unix v3.2.1.
Has anyone had any success doing this, and if so, can you mail me
info on how to do it.
The version of fuser.c that i got from uunet is realying on a tune structure
being defined in tuneable.h.
the structure is there, but not the info
that fuser is expecting. i can hard code these values
(nfile, nproc ...) but i don't know if there is anything else it is looking
for.
i would rather not re-envent the wheel if someone has already done so.
i was surprised that sco doesn't provide fuser as a standard package.

thanks for any help
Philip Hall
Sys admin
Data Prompt Inc.
Silver Spring Md.

uunet!dprmpt!phil

-----------------------------

From: Henry Spencer <henry@zoo.toronto.edu>
Subject: Re: the f2c program
Date: 12 Aug 90 00:58:36 GMT
To:       info-unix@sem.brl.mil

In article <1990Aug11.202542.9891@ux1.cso.uiuc.edu> mcdonald@aries.scs.uiuc.edu (Doug McDonald) writes:
>On the computer research.att.com is a program called "f2c". It converts
>Fortran programs to, mostly, C. But it does NOT convert Fortran IO
>calls to C. Instead it just invokes some mysterious io routines. I
>take these to be somebody's Fortran IO runtime library... whose will this
>thing work with????

Also on research.att.com, in the same directory, are files named "libF77.Z"
and "libi77.Z", which might be worth investigating.
-- 
It is not possible to both understand  | Henry Spencer at U of Toronto Zoology
and appreciate Intel CPUs. -D.Wolfskill|  henry@zoo.toronto.edu   utzoo!henry

-----------------------------

From: Tom Christiansen <tchrist@convex.com>
Subject: Re: Timeout on shell command.
Date: 12 Aug 90 01:24:12 GMT
Sender: news@convex.com
Followup-To: comp.unix.questions
To:       info-unix@sem.brl.mil

In article <BRISTER.90Aug10222433@westworld.decwrl.dec.com> brister@decwrl.dec.com (James Brister) writes:
>I'd like to have a shell script run a command, but if that command doesn't
>finish in X seconds, then the script should kill it, if the command
>finishes sooner then the script should immediately continue. Any ideas on
>how one could achieve this?

Here's timeout.c; syntax is 'timeout seconds command'.  

--tom

#include <stdio.h>
#include <signal.h>
#include <sysexits.h>
#include <sys/wait.h>

int pid,count;
union wait status;
int bang();
char **commands;

main(ac,av) 
    char **av;
{
    if (ac < 3) {
usage:  fprintf (stderr, "usage: %s seconds command\n",*av);
	exit (EX_USAGE);
    } 
    if ((count=atoi(av[1])) < 1) {
	fprintf (stderr, "seconds (%s) malformed or nonpositive\n",av[1]);
	goto usage;
    } 

    commands = &av[2];
    switch (pid=fork()) {
	default: parent(); 
		 /* NOTREACHED */
		 break;
	case 0: child();  
		 /* NOTREACHED */
	case -1: perror("fork"); 
		 exit(EX_OSERR); 
		 /* NOTREACHED */
    } 
} 

parent() {
    (void) signal(SIGALRM,bang);
    alarm(count);
    while(wait(&status) != pid) 
	  /* VOID */; 
    if (WIFSIGNALED(status)) 
	exit(-status.w_termsig);
    exit(status.w_retcode);

} 


bang() {
    fprintf(stderr,"Timeout!\n");
    (void) signal(SIGALRM,SIG_DFL);
    (void) kill(pid,SIGTERM);
    if (kill(pid,0)) {
	sleep(1);
	(void) kill(pid,SIGKILL);
    }
    exit(EX_TEMPFAIL);
} 

child() {
    execvp(*commands,commands);
    perror(*commands);
    _exit(EX_DATAERR);
    /* NOTREACHED */
} 

/* lint output:
 *	timeout.c:
 */
--

    Tom Christiansen                       {uunet,uiucdcs,sun}!convex!tchrist 
    Convex Computer Corporation                            tchrist@convex.COM
		 "EMACS belongs in <sys/errno.h>: Editor too big!"

-----------------------------


End of INFO-UNIX Digest
***********************