But when I run below command, tree structure getting
what is permanent solution to print tree structure with "tree" command.
The set of language-specific characters in your environment is (maybe erronously) set so that the line-drawing characters are replaced by some other characters (which you called "junk"). Which set of characters is taking these places (german umlauts, french accents, ....) is controlled by the "LC_ALL" variable. To set this variable to "C" means to use a set of characters without any diacriticals at all, which is enough for english language but probably no other.
When you enter a certain setting for a variable and then a command it means that the value for this variable is in effect only for this one command. This means:
The first of the two commands will have set LC_ALL to "C" and therefore work, the second one will produce junk again because "LC_ALL" is set to something else.
Solution: set the variable somewhere where it has a lasting effect. The best place is your shells startup file: "~/.kshrc" if you use ksh (Korn shell), "~/.bashrc" if you use bash (Bourne Again Shell).
Hi,
I am new to UNIX and I am more used to simple commands like those in VMS.
One of them is the ability to get the output from a job using the /out=<file> command in VMS.
I want to submit a job (a set of unix commands) using the AT command but to get the output in a file like that used in... (4 Replies)
In DOS, to get the complete directory structure, we use 'TREE' command..
can anyone tell me what is the equivalent command in Unix
I am using
SunOS ABC 5.8 Generic_117350-18 sun4u sparc SUNW,Sun-Fire-V240
thanks.. (1 Reply)
How can i install tree command in ubundu without root ? I have found some shell script which does the same job as tree but i would like to get all the options in tree command
thanks (2 Replies)
Hi All
I'm using a tree command in a script that for me outputs:-
| - - DIRECTORYNAME
However a different user is getting the following output:-
aaa (actually with an umlat above them) DIRECTORYNAME
I'm not sure where this could be coming from, any ideas anyone? (0 Replies)
Hi, I have this command:
ls -R | grep ":$" | sed -e 's/:$//' -e 's/*\//--/g' -e 's/^/ /' -e 's/-/|/' Works nicely to show the current file structure as a tree.
I'd like to have it as an alias in '' but doesn't work just like that and I can't fix it with backslashes:
alias tree='?'
... (4 Replies)
Hi all,
Can any guru please help on how I can tweak the following ps command so that it only shows the lines that I wanted.
$ command ps -HAcl -F S -A f
F S UID PID PPID CLS PRI ADDR SZ WCHAN RSS PSR STIME TTY TIME CMD
4 S root 1 0 TS 24 - 2592 ? ... (3 Replies)
Hi,
in my script, i take the last month by
a=$(date --date '1 month ago' +%Y%m)
i expect that it give me in this month "March" as result 201402,
but linux gave me 201403.
IMPe@ABC123:> ~/date --date '1 month ago' +%Y%m
201403
i'm reasonably confused. Any idea?
Thanks in advance,
... (2 Replies)
Hello friends,
There is one requirment where I need to login into database environment and pull all schema names into a text file ...
as of now below are the schemas available...
$> describe keyspaces;
system_schema system_auth system abc system_distributed system_traces
Now from... (4 Replies)
Discussion started by: onenessboy
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)