09-25-2012
Either create a .profile file in your home directory that executes these commands, or create an entry in /etc/rc.d/rc5.d. The file name should start with Snn, where nn is a number between 00 and 99. The scripts in this directory are executed in alphabetical order, so you need to use a high enough number that all dependencies are executed before your new script.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
I have a problem not really dramatic but realyl annoying:
i've got a groups of users who logon a sunos 2.3 box via a windows telnet client (KEAI, but this is not the problem).
they login as perso1 and password.
It takes a very very very long time to get in.
If i log on the same box... (2 Replies)
Discussion started by: penguin-friend
2 Replies
2. Web Development
Hi all,
I am stepping into web-development as a hobby point of view. I am using WAMP server & have created the initial page & SQL set-up too. My problem is, I was able to login to a page/redirect to a page though I haven't specified my username & password. I thought of using both... (2 Replies)
Discussion started by: gameboy87
2 Replies
3. Shell Programming and Scripting
I'm Not really sure if this is the best place to ask this question but logic tells me it is :P
I'm Trying to change the login screen for OpenSuse the green Screen for something a little bit more of my liking, and I think the only way to do it perfect and right is through the command Line, do not... (1 Reply)
Discussion started by: JuankyKong
1 Replies
4. Shell Programming and Scripting
Hello all!
This is my first post and I'm very new to programming. I would like help creating a simple perl or bash script that I will be using in my work as a junior bioinformatician.
Essentially, I would like to take a tab-delimted or .csv text with 3 columns and write them to a "3D" matrix:
... (16 Replies)
Discussion started by: torchij
16 Replies
5. SuSE
Hi,
I installed OpenSuse 12.1 on my Dell 690 (X2 dual core Xeon 2.66GHZ, 8G RAM 667 FBDIMM quad channel, 500G at striping RAID (2X 250G SATA), nVidia Quadro FX 3400).
All installation was smooth, took less than 15 minutes. But when I'm trying to login, instead of showing me the desktop... (1 Reply)
Discussion started by: netwalker
1 Replies
6. Shell Programming and Scripting
Hello,
I just started with shell and i am doin simple script to check if certain user is logged in. Script takes 3 args. name sleep time and quit value
if there is q for quit then date and user name is printed to file, not to screen.
so far i have got this...
login()
{
while :... (3 Replies)
Discussion started by: shelllo
3 Replies
7. Linux
Hi team,
I have two select statements and need to run them using SYSDBA user
select * from temp_temp_seg_usage;
select segment_name, tablespace_name, bytes/ (1024*1024) UsedMb from
dba_segments where segment_name='TEMP_TEMP_SEG_USAGE';
Need to run this using a shell script say named... (1 Reply)
Discussion started by: pamsy78
1 Replies
8. Shell Programming and Scripting
Hello all,
for security reasons my compagny imposes that my script be launch remotly via ssh under the users login shell.
So serverA launches the ssh command to serverB which has a local user with my script as a login shell.
Local script works like a charm on his own.
serverB$ grep... (20 Replies)
Discussion started by: maverick72
20 Replies
9. UNIX for Dummies Questions & Answers
Hi Guys
Im new to bash script, trying hard to learn and enjoying this process. However i'm pretty much stumped, so i will put my problems out there. In the hope someone can help me. I am trying to make a bash script that allows users of a Unix system (with little knowledge under the hood ) to be... (12 Replies)
Discussion started by: willo
12 Replies
10. Shell Programming and Scripting
Hello,
I am having an odd problem in open suse 12. I have a shell script and when I try to run it, I get "permission denied" The permissions from ls -l are,
-rw------- 1 user1 users 25904 Jan 10 16:26 script.sh
I have tried to change the permissions in dolphin but this does not change the... (5 Replies)
Discussion started by: LMHmedchem
5 Replies
LEARN ABOUT MOJAVE
init.d
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)