bheil@umaxc.weeg.uiowa.edu (Brian Heil) (05/11/91)
I've been using the AUX: device to hook a terminal up to my A1000, and have
run into a disheartening problem. I use SKsh 1.5, as a shell replacement
and invoke it (as resident code) on each login from the remote terminal.
This works great but each invocation seems to cost me about 4.5-5K of fast
ram on logging out and exiting SKsh. On a 1 meg system this mounts up with
several subsequent logins. Is it pretty standard for SKsh to steal my
memory like this? Another related question concerning version 1.7, will this
version fix this problem? (if it's a problem of course! :)
--
Brian Heil ) University of Iowa
bheil@scout-po.biz.uiowa.edu ( College of Business Administration
bheil@umaxc.weeg.uiowa.edu ) Computing Services Organization
AMIGA There is no substitute!kent@swrinde.nde.swri.edu (Kent D. Polk) (05/11/91)
In article <6007@ns-mx.uiowa.edu> bheil@umaxc.weeg.uiowa.edu (Brian Heil) writes: [...] >run into a disheartening problem. I use SKsh 1.5, as a shell replacement [...] >This works great but each invocation seems to cost me about 4.5-5K of fast >memory like this? Another related question concerning version 1.7, will this >version fix this problem? (if it's a problem of course! :) I would highly suggest you ftp SKsh 1.7. Much has been changed. Steve has added several new features and options to help conserve memory. He has also fixed the file completion problem (wrote to loc. 04), seems to have fixed the problems with the A3000, and is working on 2.0 compatibility. Note to those complaining about wildcards vs. regexp`s and lack of a Unix-feel, or, if you want 'real' shell scripts without having to learn AREXX, or lots of other unix-like shell niceties: Go get Sksh and quit your griping! :^) Kent Polk: Southwest Research Institute Internet : kent@swrinde.nde.swri.edu UUCP : $ {cs.utexas.edu, gatech!petro, sun!texsun}!swrinde!kent
griff@anvil.intel.com (Richard Griffith) (05/11/91)
In article <2814@swrinde.nde.swri.edu>, kent@swrinde.nde.swri.edu (Kent D. Polk) writes: > > Note to those complaining about wildcards vs. regexp`s and lack of a > Unix-feel, or, if you want 'real' shell scripts without having to learn > AREXX, or lots of other unix-like shell niceties: > > Go get Sksh and quit your griping! :^) > > Kent Polk: Southwest Research Institute > Internet : kent@swrinde.nde.swri.edu > UUCP : $ {cs.utexas.edu, gatech!petro, sun!texsun}!swrinde!kent Maybe I was just using it wrong, but I installed Sksh and was using it with Manx's "make" utility. My makefile "cd's" to different subdirectories and run "make" in each of those. Sksh seems to blow out when used in this manner.... Is that just me or what? :Richard E. Griffith, "griff" : iNTEL, Hillsboro Ore. :griff@anvil.intel.com :SCA!: Cyrus Hammerhand, Household of the Golden Wolf, Dragons' Mist, An Tir :These are MY opinions, if iNTEL wanted them, They'd pay for `em!
tsarna@polar.bowdoin.edu (Tyler Sarna) (05/11/91)
In article <2814@swrinde.nde.swri.edu> of comp.sys.amiga.misc, "Kent D. Polk" <kent@swrinde.nde.swri.edu> writes: > I would highly suggest you ftp SKsh 1.7. Much has been changed. Steve > has added several new features and options to help conserve memory. He > has also fixed the file completion problem (wrote to loc. 04), seems to > have fixed the problems with the A3000, and is working on 2.0 > compatibility. Sure, it's been fixed some, but have you ever run it with enforcer? Just doing an ls makes enforecer VERY unhappy. This is really a shame, as I love SKsh, but also want to use enforcer for debugging my own programs. -- Tyler "Ty" Sarna tsarna@polar.bowdoin.edu "Isolation, rows and rows of cars. Isolation, like Jupiter and Mars."
koren@hpfcdc.HP.COM (Steve Koren) (05/14/91)
> I would highly suggest you ftp SKsh 1.7. Much has been changed. Steve > has added several new features and options to help conserve memory. He > Sure, it's been fixed some, but have you ever run it with > enforcer? Just doing an ls makes enforecer VERY unhappy. This is > really a shame, as I love SKsh, but also want to use enforcer > for debugging my own programs. I think I've fixed most (if not all) of the _writes_ in 1.7. I plan to work on the _reads_ (which I considered a bit less important) in the next version. The whole thing is complicated by the fact that I can't actually run the enforcer myself - it doesn't grok my '030 card, through no fault of the program itself. I have to fix the enforcer problems by sending someone a binary, having them report what happens, and then trying to guess what broken. Its a bit of a pain, but I'm working on it... :-) As for 2.0 support, there is a little there now, but it'll get better as soon as 1) C= releases 2.0 for 2000s, and 2) there is some documentation available to non-developers on how to use the 2.0 calls. - steve
koren@hpfcdc.HP.COM (Steve Koren) (05/14/91)
>>This works great but each invocation seems to cost me about 4.5-5K of fast >>memory like this? Another related question concerning version 1.7, will this >>version fix this problem? (if it's a problem of course! :) In 1.7, I can invoke it and exit multiple times in a row with all memory freed. Actually that's not quite true for the first one, since it brings in some shared libs which hang around after its gone, but it is for every execution after that. > have fixed the problems with the A3000, and is working on 2.0 Yup, as Kent points out, it seems to run on 3000's, but there is one known problem. The install script doesn't work on 3000s. If you copy the files by hand, though, it will work right. (Sort of a pain, but you're not any worse off for installation than you were in 1.6 :-) ). - steve
koren@hpfcdc.HP.COM (Steve Koren) (05/14/91)
> Maybe I was just using it wrong, but I installed Sksh and was using it > with Manx's "make" utility. My makefile "cd's" to different subdirectories > and run "make" in each of those. Sksh seems to blow out when used in > this manner.... Is that just me or what? From what you describe, it doesn't sound like SKsh. From the moment you invoke the first "make", everything that happens (program execution, etc) is in manx-land. Could you clairfy what you mean by "blow out"? - steve
tsarna@polar.bowdoin.edu (Tyler Sarna) (05/16/91)
In article <37090014@hpfcdc.HP.COM> of comp.sys.amiga.misc, Steve Koren <koren@hpfcdc.fc.hp.com> writes: > I think I've fixed most (if not all) of the _writes_ in 1.7. I > plan to work on the _reads_ (which I considered a bit less important) The problem is not with the hits making SKsh useless, but enforcer useless. If I forget to turn it off and do an ls, I have to turn my printer off before it wastes a bunch of paper. > in the next version. The whole thing is complicated by the fact > that I can't actually run the enforcer myself - it doesn't grok my > '030 card, through no fault of the program itself. I have to That's right, you have one of those Hurricane things, don't you? I'm not sure how one can mess up the MMU on an 030, being built in, but I guess they did, huh? > fix the enforcer problems by sending someone a binary, having them > report what happens, and then trying to guess what broken. Its a > bit of a pain, but I'm working on it... :-) A bit of a pain? Sounds more like a effective method of torture! Thanks for SKsh, even with it's little problems! -- Tyler "Ty" Sarna tsarna@polar.bowdoin.edu "Navy. It's not just a job, it's $98.76 a week." -SNL