If you're using Bash, then the simplest way to do this is just to separate them with semi-colon (;) characters. Commands separated by semi-colons will be executed one after the other, regardless of the success or failure of the preceding command.
Example:
There are a few other ways to do this. If you only want the next command in the chain to be executed if the previous command was a success, then you can use a logical 'and' operator, represented by two ampersand (&) symbols:
And lastly, if you only want a command chain to continue if the previous command fails rather than succeeds, you can use the logical 'or' operator, represnted by a double pipe (|) symbol:
hi,
i have a script that runs on bash and would like to run it on a machine that has csh and bash. the default setting on that machine is csh. i dont want to change my code to run it with a csh shell. is there any way i can run the script (written in bash) on this machine? in other words is there... (3 Replies)
Hello All. I suspect that this will be a clear noob question, but I haven't been able to figure it out using the usual methods, so I turn to you.
I've written a script to create input files for the quantum chemistry program NWCHEM. Generally you create an input file and then execute it by... (12 Replies)
Server: IBM p770
OS: AIX 6.1 TL5 SP1
When one of our develoeprs types "bash" on the command line to switch shells, it hangs. For some reason, two bash processes are created....the first bash process spawns a second bash process in the same console, causing a hang. Anyone have any idea what... (2 Replies)
Hi all. On X11 I'm on a shell ...shell_1 (/bin/bash). From here I want to open another shell window shell_2 who executes commands like "ls -l" or programs like ". /program"... so the "result" of commands shows in shell_2 window and not in shell_1. Is that possible ? (4 Replies)
#!/bin/bash
#...
for i in `ls -c1 /usr/share/applications`
do
name="cat $i | grep ^Name= | cut -d = -f2"
echo $name
#...
done
Now inside name as output is present:
while i want only the result of the command.
Ideally i would like obtain that information using only bash ... or... (8 Replies)
I am having trouble with bash. I am trying to put a command in an if statement and then compare it to a string.
This works perfectly.
echo $(ipcs | grep Shared | awk '{print $2}')When I put it in an if statement I get some problems.
$ if ; then echo expression evaluated... (10 Replies)
hello, i am facing some issue. I am using a simple bash script that via sshpass put a command into router. Now, problem is that i have a file and commands into it.
sshpass -p $pass ssh -o $log -n $user@$h /ip address set address=10.0.0.1/24
so if I have that command ip address set ... (0 Replies)
I use plink.exe to automate remote commands that return data to Windows machines. This works well on newer servers running Red Hat since the commands were developed for bash and the designated user's login shell is bash. I need to also support older servers which are running Solaris 10 but the... (5 Replies)
Hi everyone,
I want to kill process through the web, so I create html page with single bottom that run kill command in shell script with CGI.
Here is html code:
<td><form METHOD="GET" action="http://IP:port/cgi_bin/script.cgi" > <input type="submit" value= "Submit" > <INPUT name="q"... (7 Replies)
Hi,
I downloaded source code file from The GNU website and changed the source code of ls.c file, added printf command to it. It worked fine. Then, I deleted the printf command, saved the file and ran the command 'make sudo && make install' closed the terminal and printf statement went away.
I... (1 Reply)
Discussion started by: akanksha1509
1 Replies
LEARN ABOUT OSF1
chroot
chroot(8) System Manager's Manual chroot(8)NAME
chroot - Changes the root directory of a command
SYNOPSIS
/usr/sbin/chroot directory command
DESCRIPTION
Only root can use the chroot command. The chroot command changes the root directory from / to the specified directory when the command
executes. (The command specified includes both the command name as well as any arguments.) Consequently, the root of any path (as indicated
by the first / (slash) in the pathname) changes to directory and is always relative to the current root. Even if the chroot command is in
effect, directory is relative to the current root of the running process.
Several programs may not operate properly after chroot executes. You must ensure that all vital files are present in the new root file
system and the relevant pathnames for the files map correctly in the new root file system.
For example, the ls -l command fails to give user and group names if the new root file system does not have a copy of the /etc/passwd and
/etc/group files. If the /etc/passwd and /etc/group files in the new root file system represent different user and group names, then the
output from the ls -l command will be based on those names, not the ones for the system's own name database. Utilities that depend on
description files produced by the ctab command may also fail if the required description files are not present in the new root file system.
The chroot program uses the execv() function to invoke the specified command. As a consequence, the command specified must be an exe-
cutable binary, not a shell script. Further, if the program requires indirect loading (for example, due to unresolved symbols requiring
use of a shared library), then /sbin/loader as well as any files it requires (for example, shared libraries) must be present in the new
root file system in the appropriate locations.
EXAMPLES
To run a subshell with another file system as the root, enter a command similar to the following. Note in this example, the file system is
on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a: chroot /mnt/dsk13a /sbin/sh The command shown in the previous example spec-
ifies a change from the current root file system to the one mounted on /mnt/dsk13a while /sbin/sh (which itself is relative to the new root
file system) executes. When /bin/sh executes, the original root file system is inaccessible. The file system mounted on /mnt/dsk13a must
contain the standard directories of a root file system. In particular, the shell looks for commands in /sbin, /bin, and /usr/bin (among
others) on the new root file system.
Running the /sbin/sh command creates a subshell that runs as a separate process from the original shell. Press to exit the subshell and
return to the original shell. This restores the environment of the original shell, including the meanings of the current directory (.) and
the root directory (/). To run a command in another root file system and save the output on the initial root file system, enter a command
similar to the following. Note in this example, the file system is on the /dev/disk/dsk13a device and is mounted to /mnt/dsk13a:
chroot /mnt/dsk13a /bin/cc -E /u/bob/prog.c > prep.out
The previous command runs the /bin/cc command with /mnt/dsk13a as the specified root file system. It compiles the /mnt/dsk13a/u/bob/prog.c
file, reads the #include files from the /mnt/dsk13a/usr/include directory, and puts the compiled text in the prep.out file on the initial
root file system. To create a file relative to the original root rather than the new one, use this syntax and enter:
chroot directory command > file
CAUTIONS
If special files in the new root have different major and minor device numbers than the initial root directory, it is possible to overwrite
the file system.
FILES
Specifies the command path.
RELATED INFORMATION
Commands: cc(1), cpp(1), ls(1), sh(1)
Functions: chdir(2), chroot(2)exec(2) delim off
chroot(8)