- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: script problem
Operating System - Linux
1748175
Members
4165
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 06:44 AM
тАО01-19-2006 06:44 AM
Re: script problem
Oh yea. To answer your original question, the dot slash ./ is a relative path name where the dot . represents the current working directory as returned by the pwd command. The slash separates the directory from the filename of the script. So, if you change to the /usr/contrib/bin directory and execute /usr/contrib/bin/gzcat it would be the equivalent of ./gzcat sense . will translate to /usr/contrib/bin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 08:45 PM
тАО01-19-2006 08:45 PM
Re: script problem
Hi,
test is a ksh command so you have to use ./ to inform the shell that you want to execute your script and not the bulldin command.
rename your script as test.ksh and you can simple test.ksh to invoke it (if you have . in teh PATH).
HTH,
Art
test is a ksh command so you have to use ./ to inform the shell that you want to execute your script and not the bulldin command.
rename your script as test.ksh and you can simple test.ksh to invoke it (if you have . in teh PATH).
HTH,
Art
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-19-2006 09:00 PM
тАО01-19-2006 09:00 PM
Re: script problem
first test is not a good name for the script. test is built in command for most of the shells.
Do following to know what exactly you will be executing.
type test
If you want to execute yout script names test, give full path when starting it.
/some_dir/some_dir/test
Do following to know what exactly you will be executing.
type test
If you want to execute yout script names test, give full path when starting it.
/some_dir/some_dir/test
There is no substitute to HARDWORK
- « Previous
-
- 1
- 2
- Next »
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP