10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Having a doubt on how Function keys are mapped.
1. In my HPUX box my infocmp shows that kf1 (F1 key mapping) is not mapped. But somehow I am able to use an Informix form which requires navigation using F1 keys.
vt100-w|vt100-w-am|dec vt100 132 cols (w/advanced video),
bce, bw, ccc,... (3 Replies)
Discussion started by: clemansy
3 Replies
2. Shell Programming and Scripting
Hi
I am try to use sed to remove decleration information from an XML file however their are special characters in the string and sed is not able to parse it . I am using the following commond.
sed -e "s/xmlns=http://www.abc.com/integration/services/testtemplate1//g" Orginal.xml... (3 Replies)
Discussion started by: jimmyb
3 Replies
3. Solaris
Hello,
I am running Solaris 8. When issuing the command "stty lcase" all text which is output to the terminal are capitalized. Letters that are supposed to be capitals are preceded by a backslash during output. All text which is input is converted to lower case. This is the expected behaviour... (5 Replies)
Discussion started by: rstor
5 Replies
4. Shell Programming and Scripting
Friends,
In the file i am having more then 100 lines like,
File1 had the values like this:
#Example East.server_01=EAST.SERVER_01
East.server_01=EAST.SERVER_01
West.server_01=WEST.SERVER_01
File2 had the values like this:
#Example EAST.SERVER_01=http://yahoo.com... (3 Replies)
Discussion started by: jothi basu
3 Replies
5. Red Hat
I ran the following grep and sed command.
grep "\t" emp.txt
sed -n '/\t/p' emp.txt
grep treated the '\' as to escape t and took the pattern as literal t whereas sed took the pattern as tab.
That means , grep doesn't understand escape sequence!!!!!!
what to do to make grep... (8 Replies)
Discussion started by: ravisingh
8 Replies
6. Shell Programming and Scripting
$table is the variable which contains name of the file.
Filename may have the special character $. Need to escape $ .
Tried below options to escape dollar:
\$$table
"\$"$table""
what is the escape sequence for egrep function..?
Below is the code snippet-
my $table;
foreach... (3 Replies)
Discussion started by: xylus77
3 Replies
7. Shell Programming and Scripting
Hi All,
I have added the script command to user profile so that to record the on-screen data.But when i i checked the O/P i could see lot of escape sequence is there way to remove it. (2 Replies)
Discussion started by: cutechaps
2 Replies
8. Shell Programming and Scripting
Hi all,
I have a requirement where the variable name starts with $, like
$Amd=/home/student/test/
How to work wit it? can some one help me, am in gr8 confusion:confused: (5 Replies)
Discussion started by: shreekrishnagd
5 Replies
9. UNIX for Dummies Questions & Answers
I couldn't seem to make 'HOME' key work on my remote windows ssh client to a Fedora Core3 server (the home key works perfectly when i'm physically on site.)
To my surprise, using control+V it seems that both my home and insert key send the same escape sequence ^So it must be my windows SSH client... (0 Replies)
Discussion started by: grossgermany
0 Replies
10. UNIX for Advanced & Expert Users
Hi,
Is it possible to view the escape sequence in the ascii file. That is I want to see the newlinw character,tab ........ etc
Thanks
Sweta (4 Replies)
Discussion started by: sweta
4 Replies
init.d(4) init.d(4)
NAME
init.d - initialization and termination scripts for changing init states
SYNOPSIS
/etc/init.d
/etc/init.d is a directory containing initialization and termination scripts for changing init states. These scripts are linked when appro-
priate to files in the rc?.d directories, where `?' is a single character corresponding to the init state. See init(1M) for definitions of
the states.
The service management facility (see smf(5)) is the preferred mechanism for service initiation and termination. The init.d and rc?.d direc-
tories are obsolete, and are provided for compatibility purposes only. Applications launched from these directories by svc.startd(1M) are
incomplete services, and will not be restarted on failure.
File names in rc?.d directories are of the form [SK]nn<init.d filename>, where S means start this job, K means kill this job, and nn is the
relative sequence number for killing or starting the job.
When entering a state (init S,0,2,3,etc.) the rc[S0-6] script executes those scripts in /etc/rc[S0-6].d that are prefixed with K followed
by those scripts prefixed with S. When executing each script in one of the /etc/rc[S0-6] directories, the /sbin/rc[S0-6] script passes a
single argument. It passes the argument 'stop' for scripts prefixed with K and the argument 'start' for scripts prefixed with S. There is
no harm in applying the same sequence number to multiple scripts. In this case the order of execution is deterministic but unspecified.
Guidelines for selecting sequence numbers are provided in README files located in the directory associated with that target state. For
example, /etc/rc[S0-6].d/README. Absence of a README file indicates that there are currently no established guidelines.
Do not put /etc/init.d in your $PATH. Having this directory in your $PATH can cause unexpected behavior. The programs in /etc/init.d are
associated with init state changes and, under normal circumstances, are not intended to be invoked from a command line.
Example 1: Example of /sbin/rc2.
When changing to init state 2 (multi-user mode, network resources not exported), /sbin/rc2 is initiated by the svc.startd(1M) process. The
following steps are performed by /sbin/rc2.
1. In the directory /etc/rc2.d are files used to stop processes that should not be running in state 2. The filenames are prefixed with K.
Each K file in the directory is executed (by /sbin/rc2) in alphanumeric order when the system enters init state 2. See example below.
2. Also in the rc2.d directory are files used to start processes that should be running in state 2. As in Step 1, each S file is executed.
Assume the file /etc/init.d/netdaemon is a script that will initiate networking daemons when given the argument 'start', and will terminate
the daemons if given the argument 'stop'. It is linked to /etc/rc2.d/S68netdaemon, and to /etc/rc0.d/K67netdaemon. The file is executed by
/etc/rc2.d/S68netdaemon start when init state 2 is entered and by /etc/rc0.d/K67netdaemon stop when shutting the system down.
svcs(1), init(1M), svc.startd(1M), svccfg(1M), smf(5)
Solaris now provides an expanded mechanism, which includes automated restart, for applications historically started via the init script
mechanism. The Service Management Facility (introduced in smf(5)) is the preferred delivery mechanism for persistently running applica-
tions. Existing init.d scripts will, however, continue to be executed according to the rules in this manual page. The details of execution
in relation to managed services are available in svc.startd(1M).
On earlier Solaris releases, a script named with a suffix of '.sh' would be sourced, allowing scripts to modify the environment of other
scripts executed later. This behavior is no longer supported; for altering the environment in which services are run, see the setenv sub-
command in svccfg(1M).
/sbin/rc2 has references to the obsolescent rc.d directory. These references are for compatibility with old INSTALL scripts. New INSTALL
scripts should use the init.d directory for related executables. The same is true for the shutdown.d directory.
17 Aug 2005 init.d(4)