05-23-2007
Quote:
Originally Posted by ilak1008
I tried to run my ksh scripts in SFU and it always says "not found" as in the example below:
$ .file
/bin/ksh: .file: not found
Did I miss something in the SFU Installation?
try ./file
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Ih all,
i have multiples ksh scripts for crontab's unix jobs
they all have same variables declarations and some similar functions
i would have a only single script file to declare my variables, like:
var1= "aaa"
var2= "bbb"
var3= "ccc"
...
function ab { ...}
function bc { ... }... (2 Replies)
Discussion started by: wolfhurt
2 Replies
2. HP-UX
Hi,
I have small script written in korn shell. When it is called from different script, its dumping core, but no core dump when we run it standalone.
And its not dumping core if we run the script using "/bin/sh" instead of "ksh"
Can some body please help me how to resolve this issue.
... (9 Replies)
Discussion started by: simhe02
9 Replies
3. Shell Programming and Scripting
I have a script that runs fine under my home directory. No syntax errors, runs and returns as expected.
When I migrate the script to the UAT directories on the same server for User testing, I get a syntax error.
I've checked to make sure the .profile I'm using is the same in the UAT... (1 Reply)
Discussion started by: mpflug
1 Replies
4. Solaris
Hi,
I am currently in the process of testing upgrading from Solaris 8 to Solaris 10.
one problem i have encountered is when i am running any of my batch scripts.
All my scripts start with #! /bin/ksh so that they will excuted in the ksh shell.
but the scripts will not run correctly. The... (3 Replies)
Discussion started by: dshakey
3 Replies
5. Shell Programming and Scripting
I am trying a set up a very simple korn shell script. It has 2 basic steps.
Firstly I read the first line of a text file (which is a file name)
Secondly I run a fortran executable using that line
I must be doing something wring because it wouldn't work. I know that the executable wants the... (4 Replies)
Discussion started by: larangunn
4 Replies
6. UNIX for Advanced & Expert Users
Hi.
I have a ksh script I want to run, but I'm connecting through a telnet and I don't want to FTP the scripts itself.
is there a way of running the script from command line ?
like ksh "The script itself..."
Thanks,
Ramon (4 Replies)
Discussion started by: mellowcandle
4 Replies
7. Shell Programming and Scripting
When i use ssh command to execute local script on remote server , I am unable to do it.
Please let me know how this can be done in ksh
req=abc
dte=ghd
ssh username@hostname "$req $dte" < run_script.sh (2 Replies)
Discussion started by: lalitpct
2 Replies
8. UNIX for Dummies Questions & Answers
Hi
I searched this forum before posting the question, but couldnt find it, the issue
i'm facing is, i'm trying to select a column from a netezza table from a korn
shell script, but the query runs
var=$(nzodbcsql -q "select MAX(millcount) from table1";)
echo $var
it returns the value like... (10 Replies)
Discussion started by: maximus_jack
10 Replies
9. UNIX for Advanced & Expert Users
I noticed some strange looking parameters on some processes on one of our servers, and after a little playing around we deduced that ksh seemed to be adding a (somewhat random) extra parameter when calling a script without a hashbang in it.
It looks like it's the partial name of the parent... (10 Replies)
Discussion started by: CarloM
10 Replies
10. Shell Programming and Scripting
I have to kill the process "test" for a maintenance I do but want the script to check when it comes back up.
I can get what I want when I run this while loop:
while true;do ps -ef | grep test | grep -v grep | sed -e 's/^*//';sleep 60;done
but I want the script to do it for me and as soon as... (6 Replies)
Discussion started by: seekryts15
6 Replies
LKSH(1) BSD General Commands Manual LKSH(1)
NAME
lksh -- Legacy Korn shell built on mksh
SYNOPSIS
lksh [-+abCefhiklmnprUuvXx] [-+o opt] [-c string | -s | file [args ...]]
DESCRIPTION
lksh is a command interpreter intended exclusive for running legacy shell scripts. It is built on mksh; refer to its manual page for details
on the scripting language.
LEGACY MODE
lksh has the following differences from mksh:
o lksh is not suitable for use as /bin/sh.
o There is no explicit support for interactive use, nor any command line editing code. Hence, lksh is not suitable as a user's login
shell, either; use mksh instead.
o The KSH_VERSION string identifies lksh as ``LEGACY KSH'' instead of ``MIRBSD KSH''.
o Some mksh specific extensions are missing; specifically, the -T command-line option.
o lksh always uses traditional mode for constructs like:
$ set -- $(getopt ab:c "$@")
$ echo $?
POSIX mandates this to show 0, but traditional mode passes through the errorlevel from the getopt(1) command.
o lksh, unlike AT&T UNIX ksh, does not keep file descriptors > 2 private.
o lksh parses leading-zero numbers as octal (base 8).
o Integers use the host C environment's long type, not int32_t. Unsigned arithmetic is done using unsigned long, not uint32_t. Neither
value limits nor wraparound is guaranteed. Dividing the largest negative number by -1 is Undefined Behaviour (but might work on 32-bit
and 64-bit long types).
o lksh only offers the traditional ten file descriptors to scripts.
SEE ALSO
mksh(1)
https://www.mirbsd.org/mksh.htm
https://www.mirbsd.org/ksh-chan.htm
CAVEATS
lksh tries to make a cross between a legacy bourne/posix compatibl-ish shell and a legacy pdksh-alike but ``legacy'' is not exactly speci-
fied. Parsing numbers with leading zero digits or ``0x'' is relatively recent in all pdksh derivates, but supported here for completeness.
It might make sense to make this a run-time option, but that might also be overkill.
The set built-in command does not have all options one would expect from a full-blown mksh or pdksh.
Talk to the MirOS development team using the mailing list at <miros-mksh@mirbsd.org> or the #!/bin/mksh (or #ksh) IRC channel at
irc.freenode.net (Port 6697 SSL, 6667 unencrypted) if you need any further quirks or assistance, and consider migrating your legacy scripts
to work with mksh instead of requiring lksh.
MirBSD February 11, 2013 MirBSD