09-10-2004
[QUOTE]Originally posted by Kelam_Magnus
[B]yeniaoer (who I suspect is the OP) filing this report under another user name. Since yeniaoer has zero posts...
sorry not me, you may want to try pm'ing the user and asking why my post was reported.
READ THE FAQ...
read it didnt see anything relevant to my question. Maybe you see something I dont?
To clarify im trying to launch new terminal windows from the command line not just change shells
10 More Discussions You Might Find Interesting
1. Solaris
Hi all,
First time poster here. Great forum.
Im trying to spawn new shells and pass commands to the new shells in a solaris 8 environment utilizing dtterm and its option -e.
I can successfully spawn a window utilizing the following code:
/usr/dt/bin/dtterm -display <ip.address> &
... (4 Replies)
Discussion started by: Rocketman8541
4 Replies
2. Shell Programming and Scripting
Hi there,
I have a shell script which I need to run it from two different places on the same server, are there any specific rules I need to apply? What is the best practice to achieve this task.
Regards (5 Replies)
Discussion started by: JimJim
5 Replies
3. UNIX for Advanced & Expert Users
We have a program (reader) that reads audio files in a real-time continuous stream from a sender program. If the reader gets weird we want the sender to be able to send one command that will stop the current reader and start a new one that will be able to continue reading in the files. The sender... (9 Replies)
Discussion started by: laforge
9 Replies
4. UNIX for Advanced & Expert Users
Hi - I need help. My user crontab is spawning multiple at processes (and multiple mencoder program starts, that exit, then restart, repeatedly), locking up my system.
For example I have this entry in my crontab:
$ sudo crontab -u victoria -e
* * * * * ~/recordings/pvr1
* * * * *... (10 Replies)
Discussion started by: gstuart
10 Replies
5. UNIX for Dummies Questions & Answers
hi,
i am aa unix amateur and i am using tsh, csh and bash most of the time.
i have been looking over the net to find a summary of the differences in command syntax for example:
in csh and tsh you do
alias whatday date
while in bash and ksh you do
alias whatday=date
i just want more... (2 Replies)
Discussion started by: hobiwhenuknowme
2 Replies
6. UNIX for Dummies Questions & Answers
Guys
I now have a script that's working in a BASH environment, however one line doesn't appear to be working on an embedded device that has a busybox therefore ASH shell. I've googled but there's very little I can find regarding the ASH shell.
In BASH the following line works...
if ] ;... (6 Replies)
Discussion started by: Bashingaway
6 Replies
7. Programming
I use Ubuntu 10.4, and I installed GNUStep, Gorm (a gui builder) and ProjectCenter (the GNU alternative to Xcode) because I want to develop Objective-C apps. I opened the ProjectCenter and I created an application that displays only an empty window. I sourced the GNUstep.sh and I compiled the app. ... (0 Replies)
Discussion started by: mghis
0 Replies
8. Shell Programming and Scripting
When trying to get the correct syntax to cron a script that creates a file with the date stamp as its output, sometimes I get these results:
- from the command line, I may encounter an error that leaves me without the usual $ prompt. Am I in a new shell? I try to exit it with 'exit' or :q! and... (1 Reply)
Discussion started by: landog
1 Replies
9. UNIX for Dummies Questions & Answers
Whenever I run manual page on a command I get information about arguments, syntax and so on. However, I wounder if that information is valid only for a certain shell and if yes, then for which one?
In other words, would I have different man outputs for csh, ksh, bash and others?
Thanks (7 Replies)
Discussion started by: rdogadin
7 Replies
10. Shell Programming and Scripting
Hi there,
I would like to understand the purpose of spawning a TTY shell?
Does it mean that it will help to open up a new Windows on the current interactive shell such that when the session gets lost the other won't
Any explanation will be helpful. (3 Replies)
Discussion started by: alvinoo
3 Replies
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)