![]() |
Hello and Welcome from United States to the UNIX and Linux Forums! Thank You for Visiting and Joining Our Global Community.
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Shell Programming and Scripting Post questions about KSH, CSH, SH, BASH, PERL, PHP, SED, AWK and OTHER shell scripts and shell scripting languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| problem with shell script execution | anju | Shell Programming and Scripting | 2 | 05-08-2008 01:50 AM |
| Is there a way to tell how long does a shell script's execution take? | meili100 | UNIX for Dummies Questions & Answers | 4 | 02-25-2008 07:49 AM |
| Please help on shell scripts execution | duke0001 | Shell Programming and Scripting | 13 | 09-20-2006 03:31 PM |
| How to create file execution in KSH shell | heru_90 | Shell Programming and Scripting | 4 | 06-23-2006 12:43 PM |
| execution of shell script | malaymaru | Shell Programming and Scripting | 5 | 06-13-2005 09:49 AM |
![]() |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
Hi,
I have a question regarding Korn shell script execution in HP-UX 11.11. What sort of environmental settings do I need to run a Korn shell script such as below without entering "./" at the begining of the command? Code:
cat test.ksh date Cheers Steve |
|
||||
|
I must point out that you increase your risk of an exploit if you modify the root PATH, particularly if you insert in front of the path rather than extending it. For instance, if you put the current-dir (".") in the front of the PATH, then any ordinary user can destroy the system by putting a "rm -fr /" inside a file called "/tmp/ls". If root ever cd's to /tmp and types "ls"...bang.
For security purposes, you should never put a directory in the root PATH that ordinary users have write-access to. Additionally, the root user should not rely on the PATH but rather use full pathnames (I realize this additional step is annoying, so adjust your paranoia level accordingly). |
|
||||
|
I'll second that - do not have "." in your PATH - it's an accident waiting to happen.
And a decent sys admin will not allow it in root's PATH! In fact, root shouldn't be running things that don't belong to root, anyway. Thinking you ned root to run something usually just means you haven't thought through what is really required. |
![]() |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|