You are not logged in. Login Now
 0-24   25-49   50-74   75-99   100-113      
 
Author Message
25 new of 113 responses total.
supremor
response 75 of 113: Mark Unseen   Feb 2 12:13 UTC 2002

Crud, let me try that again. 
Howdy! I
I'm wondering if any one shell is faster than another in Grex. I changed to
`sh' from `csh', but there's still alot of typing lag. I'm telnetting from
Manhattan and maybe I just have to get a shell account in my area.
scott
response 76 of 113: Mark Unseen   Feb 2 13:32 UTC 2002

It's not your shell, it's the network between you and Grex which is causing
the lag.

Aside from that, welcome to Grex!
gelinas
response 77 of 113: Mark Unseen   Feb 2 17:35 UTC 2002

(Could also be the load on grex, which varies.  I find it much slower
when the load is above 20 than when it is below 5.  Currently, it is:

 12:35pm  up 5 days, 22:46,  38 users,  load average: 4.46, 3.76, 3.40

)
keesan
response 78 of 113: Mark Unseen   Feb 2 20:02 UTC 2002

I have been getting a lot of lag this past week while dialed in - 30 sec wait
for a word to appear.
pclash
response 79 of 113: Mark Unseen   Feb 3 01:25 UTC 2002

I got a GREX acct for the purpose of writing simple Kornshell programs.  To
run them I need to know what to put on the first line --#!/bin/ksh isn't
working.  Is the ksh command located elsewhere?  Any FAQs available on this
for GREX?  pclash@yahoo.com
gelinas
response 80 of 113: Mark Unseen   Feb 3 01:47 UTC 2002

} Respond, pass, forget, quit, or ? for more options? !whereis ksh
} ksh: /usr/local/bin/ksh
other
response 81 of 113: Mark Unseen   Feb 3 19:22 UTC 2002

shouldn't that be in his PATH, though?
davel
response 82 of 113: Mark Unseen   Feb 3 20:07 UTC 2002

Re 81: /usr/local/bin should be in his PATH, but it won't look there for ksh
if he specifies /bin/ksh.
other
response 83 of 113: Mark Unseen   Feb 4 02:47 UTC 2002

Oh, oops.  Didn't notice that.
tsty
response 84 of 113: Mark Unseen   Feb 4 17:17 UTC 2002

by that logic, then,     #!ksh   would be sufficient?
based on the full path already existing in PATH.
gelinas
response 85 of 113: Mark Unseen   Feb 4 18:33 UTC 2002

Except that shell scripts don't have a path.  That's why you have to specify
it after the #!
blaise
response 86 of 113: Mark Unseen   Feb 4 18:33 UTC 2002

Only if you're willing to rely on everyone who might use the script having
ksh in their path.
blaise
response 87 of 113: Mark Unseen   Feb 4 18:46 UTC 2002

sorry, #85 slipped in.  #86 was referring to #84.  Joe, shell scripts can
inherit the environment (including the path), but you can't count on that
environment being what you expect...
gelinas
response 88 of 113: Mark Unseen   Feb 4 18:53 UTC 2002

Ah.  Thanks.
remmers
response 89 of 113: Mark Unseen   Feb 4 20:41 UTC 2002

I don't think the path is consulted when interpreting the shebang
line.  e.g. on my linux system, "#!/usr/local/bin/perl" works but
"#!perl" doesn't, despite the fact that /usr/local/bin is in my
path.
jp2
response 90 of 113: Mark Unseen   Feb 4 20:43 UTC 2002

This response has been erased.

davel
response 91 of 113: Mark Unseen   Feb 5 14:48 UTC 2002

Hmm.  I thought it did use the path, too (though I always use the full path),
but quick tests say Joe & John are right on the SYSV system I use most.  And
there the error message is particularly awful: it implies that the script is
not found.  Bleah.
gull
response 92 of 113: Mark Unseen   Feb 5 15:11 UTC 2002

Yeah, that's one of the all-time worst UNIX error messages.
tpryan
response 93 of 113: Mark Unseen   Feb 5 19:46 UTC 2002

        In the stupid UNIX tricks department, someone told me that
an unfinished command of 'make love' returns the error message of:
'can't make love'.  Isn't that what being a UNIX is all about?
gull
response 94 of 113: Mark Unseen   Feb 5 19:49 UTC 2002

bash-2.05$ make love
make: *** No rule to make target `love'.  Stop.
oval
response 95 of 113: Mark Unseen   Feb 5 20:11 UTC 2002

love me unix!

remmers
response 96 of 113: Mark Unseen   Feb 5 20:14 UTC 2002

The TOPS-10 platform I used to use responded to the command
"make love" with "Not war?"
blaise
response 97 of 113: Mark Unseen   Feb 5 21:15 UTC 2002

The FreeBSD machine I use gave this:
osm# make love
make: don't know how to make love. Stop
twill
response 98 of 113: Mark Unseen   Feb 5 23:54 UTC 2002

Hi, I'm Twill!
ea
response 99 of 113: Mark Unseen   Feb 6 02:26 UTC 2002

what about the ever popular "man woman" command?
 0-24   25-49   50-74   75-99   100-113      
Response Not Possible: You are Not Logged In
 

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss