Noted Don. I will provide OS/Shell for any future posts. For now, I am using SunOS unix 5.10 Generic_150400-30 and shell is K Shell.
Your suggested code appears to be for use in a script file. Although I would prefer a one line command but I tried it anyway from the command line with "\;" after each line. It goes back to ">" prompt expecting some input.
I played around a little more with my original command and the following seems to have worked for me.
Please have a look and let me know if you see any potential problem with this.
Thanks.
Subhash.
Moderator's Comments:
Please use CODE tags as required by forum rules!
Last edited by RudiC; 08-21-2017 at 02:39 PM..
Reason: Changed QUOTE to CODE tags.
Hi,
Please help me.
Suppose I have a file which contains files like:
My file :/tmp/rooh_20020518.lst
it consists:
ASI00320225041925URD01
ASI00320225041925KER02
ASI00390228095244KER08 ... (1 Reply)
I am trying to cp files that have F0 as prefix in their name in path p1/p2 to path p3/p4
this command does not work - Why? (I am using HP/UX)
cp p1/p2/F0* p3/p4
thanks. (2 Replies)
Hi,
Is there a way to use find command to list the directories for certain permissions. I know we can use find . -type d -perm nnn, where nnn is the permission number . However I wold like to know if I wanna search for wild card permissions i.e 75* / 7* / 55* , as i do not know the actual... (1 Reply)
Hi,
I want to monitor my filesystem capacity and I want to df with grep wildcard for all 9*%.
Is this possible? I want to replaced all the existing complicated scripts I have in the system.
Thanks,
Itik (2 Replies)
Hi All,
I would like to find out the existence of files with wild card using CSH.
I have used the below code but does not seem to work.
Can any expert give me some advice ?
set nonomatch
set pattern = "_xxx"
set filetype = ( *$pattern* )
if ( -e $filetype) then
echo... (2 Replies)
Can somebody help me with the following syntax? I want to find all
files that end with *.arc
SUFFIX=".arc"
find /tmp -name "\*$SUFFIX" -print 2>/dev/null
---------- Post updated at 03:45 PM ---------- Previous update was at 03:41 PM ----------
got it thanks
-name... (0 Replies)
Hi
I need a unix command which generates the list of files that dont match the wild card pattern in the current directory
say for example
I have files like
x.addfd.txt.H2012.txt
x.addfd.txt.H2012.txt
x.asegfd.txt.H2012.txt
adfd.bagddf
I need the list of files which dont match... (4 Replies)
Hi All,
My server is AIX and i am trying to search for a file in a specific path in directory.
The file name can be of two types:
Position_20131114.csv
Position123333_20131114.csv
I am trying to assign a SOURCEFILE variable as mentioned below:, but i am unable to find/locate the files... (2 Replies)
I have dir structure like this :
/opt/oracle/product/abc/sqlplus/admin/
/opt/oracle/product/def/sqlplus/admin
/opt/oracle/product/ghi/sqlplus/admin
I am trying to use wildcard ( for dirs abc,def,ghi) ..something like this :
cp xyz.txt ... (1 Reply)
Hi Firends,
I have requirement like find the directories in unix after my my deployment is done.
generally my requirement as follows.
/data/common/scripts is folder and it has multiple scripts in this path.
I have taken the back up of scripts folder as below
/data/common/0816_scripts... (4 Replies)
Discussion started by: victory
4 Replies
LEARN ABOUT HPUX
sh
sh(1) General Commands Manual sh(1)NAME
sh - overview of various system shells
SYNOPSIS
POSIX Shell
option] ... string] [arg ...]
option] ... string] [arg ...]
Korn Shell
option] ... string] [arg ...]
option] ... string] [arg ...]
C Shell
[command_file] [argument_list ...]
Key Shell
DESCRIPTION
Remarks
The POSIX .2 standard requires that, on a POSIX-compliant system, executing the command activates the POSIX shell (located in file on HP-UX
systems), and executing the command produces an on-line manual entry that displays the syntax of the POSIX shell command-line.
However, the command has historically been associated with the conventional Bourne shell, which could confuse some users. To meet stan-
dards requirements and also clarify the relationships of the various shells and where they reside on the system, this entry provides com-
mand-line syntax and a brief description of each shell, and lists the names of the manual entries where each shell is described in greater
detail.
The Bourne shell is removed from the system starting with HP-UX 11i Version 1.5. Please use the POSIX shell as an alternative.
Shell Descriptions
The HP-UX operating system supports the following shells:
POSIX-conforming command programming language and command interpreter
residing in file Can execute commands read from a terminal or a file. This shell conforms to current POSIX standards in
effect at the time the HP-UX system release was introduced, and is similar to the Korn shell in many respects. Similar in
many respects to the Korn shell, the POSIX shell contains a history mechanism, supports job control, and provides various
other useful features.
Korn-shell command programming language and commands interpreter
residing in file Can execute commands read from a terminal or a file. This shell, like the POSIX shell, contains a his-
tory mechanism, supports job control, and provides various other useful features.
A command language interpreter
that incorporates a command history buffer, C-language-like syntax, and job control facilities.
Restricted version of the POSIX shell command interpreter.
Sets up a login name and execution environment whose capabilities are more controlled (restricted) than normal user
shells.
restricted version of the Korn-shell command interpreter
Sets up a login name and execution environment whose capabilities are more controlled (restricted) than normal user
shells.
An extension of the standard Korn Shell
that uses hierarchical softkey menus and context-sensitive help.
+--------------+--------------------+
| To obtain: | Use the command: |
+--------------+--------------------+
| POSIX Shell | /usr/bin/sh ... |
| Korn Shell | /usr/bin/ksh ... |
| C Shell | /usr/bin/csh ... |
| Key Shell | /usr/bin/keysh |
+--------------+--------------------+
These shells can also be the default invocation, depending on the entry in the file. See also chsh(1).
WARNINGS
Many manual entries contain descriptions of shell behavior or describe program or application behavior similar to ``the shell'' with a ref-
erence to ``see sh(1)''.
SEE ALSO
For more information on the various individual shells, see:
keysh(1) Key Shell description.
ksh(1) Korn Shell description.
sh-posix(1) POSIX Shell description.
csh(1) C Shell description.
sh(1)