Sponsored Content
Full Discussion: Definitions/explanations
Top Forums UNIX for Dummies Questions & Answers Definitions/explanations Post 302334149 by pludi on Wednesday 15th of July 2009 02:09:40 AM
Old 07-15-2009
"Interactive shell" is an instance of a shell (ksh/bash/csh/...) that interacts with the user, = where you enter commands. A non-interactive shell would be a shell started to run an automated script, eg. via cron/at

"Built-In commands" are commands defined by the shell for which it doesn't need to start a sub-process. Those mostly affect the internal state of the shell (like 'set -x'), environment variables (like export), or control flow (if/case/...). You can see if a command is a built-in by entering 'type <command>'

As for man page sections: the -S switch defines which sections man should search in for the command you specified, not the sections inside the man page. An example of man sections (from Linux):
Code:
       0   Header files (usually found in /usr/include)
       1   Executable programs or shell commands
       2   System calls (functions provided by the kernel)
       3   Library calls (functions within program libraries)
       4   Special files (usually found in /dev)
       5   File formats and conventions eg /etc/passwd
       6   Games
       7   Miscellaneous  (including  macro  packages and conven-
           tions), e.g. man(7), groff(7)
       8   System administration commands (usually only for root)
       9   Kernel routines [Non standard]

It doesn't know about any sections inside the page itself, as it just passes the content of the page through a formatter (groff/troff/...) and then into a pager (more/less/...). Think of it as HTML: Just because there's a <h1> tag somewhere the browser won't automatically generate an index, it's just a formatting instruction.
 

8 More Discussions You Might Find Interesting

1. Linux

Termcap Definitions

Hi. How do I enter and escape from graphics mode on RedHat Linux to capture escape sequences. I'm trying to edit the system termcap. (2 Replies)
Discussion started by: cstovall
2 Replies

2. IP Networking

ping program with explanations please!!!!!

need help!! need a ping program written in c with the explanations as to what each variable,function does!!! please help!! (4 Replies)
Discussion started by: sachin_zeus
4 Replies

3. Shell Programming and Scripting

function definitions file for bc

Hello, All :) ...I just figured out how to setup a function definitions file for bc...I was going to create lots more functions for it, but I'll bet that a huge file with tons of definitions has already been written...? Thanx in advance for any replies, Pudnik (0 Replies)
Discussion started by: Pudnik
0 Replies

4. AIX

/etc/subsync parms definitions ?

In our Cron table, we have the /etc/subsync client ipadr1 ipadr2 Each ipadr is an actual IP adress. I think it has something to do with synchronizing the clock between servers, but what is the ipadr2 for ? (0 Replies)
Discussion started by: Browser_ice
0 Replies

5. Shell Programming and Scripting

bashscript for learning definitions

Hi, I am a german lawstudent and have to learn a few hundred definitions and laws in the next months. I thought it would be cool to have a little helper, a bashscript which is working with flat textfiles. I found one in the archlinuxforum which was almost perfect...almost. It is on some point based... (2 Replies)
Discussion started by: phr0st
2 Replies

6. UNIX for Dummies Questions & Answers

Sensors Explanations

Hello, I am trying to get some information from the sensors on my pc. But i get confuse with what i get. I don t know where to find out which sensors watches what.. I use "sensors" under ubuntu 10.10. Here is the result of the cmd line sudo sensors. the temp 3 indicates 79°C which... (0 Replies)
Discussion started by: Mat_k
0 Replies

7. UNIX for Dummies Questions & Answers

Need some explanations in commands

I want to know what's the meaning of the following commands first eg ^*a*e*i*o*u*$What does exactly the *a,*e,*i ...*$ means in this command? I know that i can also use this command without the *a,*e,*i ... *$! At this ocassion what's the difference? second eg sed ‘s/^/<tab>/’ file1In sed... (2 Replies)
Discussion started by: kotsos13
2 Replies

8. Programming

I need some explanations

hello let me start with i am a php ,vb ,c# programmer i heared that Routers run a smaller version of linux called an Embedded Operating System i don't know what is that mean so i want to know how to get into router files ? how to edit it ? what language it use , is it c and c++ ?... (1 Reply)
Discussion started by: mr.vip
1 Replies
exec(1) 							   User Commands							   exec(1)

NAME
exec, eval, source - shell built-in functions to execute other commands SYNOPSIS
sh exec [argument...] eval [argument...] csh exec command eval argument... source [-h] name ksh *exec [arg...] *eval [arg...] DESCRIPTION
sh The exec command specified by the arguments is executed in place of this shell without creating a new process. Input/output arguments may appear and, if no other arguments are given, cause the shell input/output to be modified. The arguments to the eval built-in are read as input to the shell and the resulting command(s) executed. csh exec executes command in place of the current shell, which terminates. eval reads its arguments as input to the shell and executes the resulting command(s). This is usually used to execute commands generated as the result of command or variable substitution. source reads commands from name. source commands may be nested, but if they are nested too deeply the shell may run out of file descrip- tors. An error in a sourced file at any level terminates all nested source commands. -h Place commands from the file name on the history list without executing them. ksh With the exec built-in, if arg is given, the command specified by the arguments is executed in place of this shell without creating a new process. Input/output arguments may appear and affect the current process. If no arguments are given the effect of this command is to mod- ify file descriptors as prescribed by the input/output redirection list. In this case, any file descriptor numbers greater than 2 that are opened with this mechanism are closed when invoking another program. The arguments to eval are read as input to the shell and the resulting command(s) executed. On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways: 1. Variable assignment lists preceding the command remain in effect when the command completes. 2. I/O redirections are processed after variable assignments. 3. Errors cause a script that contains them to abort. 4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari- able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not performed. EXIT STATUS
For ksh: If command is not found, the exit status is 127. If command is found, but is not an executable utility, the exit status is 126. If a redi- rection error occurs, the shell exits with a value in the range 1-125. Otherwise, exec returns a zero exit status. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
csh(1), ksh(1), sh(1), attributes(5) SunOS 5.10 17 Jul 2002 exec(1)
All times are GMT -4. The time now is 01:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy