Those variables are set during user login and thus are only available in a user session.
During startup, no login shell is executed and no user is logged in (although root might be the owner of the startup processes). So, referring to those variables doesn't make any sense.
Does your crontab provide the @reboot time/date specifier?
Hi RudiC,
Thanks a lot for your reply
Sorry that i do not have much knowledge with AIX , I was not aware that this variables not available at boot up
I will come back to you when I am back in the office to answer your question
Thanks for your help
Kind regards
---------- Post updated at 08:15 PM ---------- Previous update was at 08:06 PM ----------
Quote:
Originally Posted by vbe
To help you, we'd have to know a bit more about the script...
Who do you think runs the script in /etc/inittab ?
Let's say it must be oracle, and as we all kmow, oracle will not run like that, it needs loads of env variables set. Is it the case? as of course e.g. LOGNAME cannot be found as the script is launched by ? at boot time, so how do you expect that specific variable to be initialised when no login occured?...
In most cases it the use of su that solves the problem like using
Code:
su -c user4thisapplication /opt/application/somebinary
In case when you need the same environment as in interactive mode ( login) you can use su - <user> at the condition you modified the .profile or whaterver profile you are using to bypass what is not used for batch mode : all that has to do with terminal settings etc... when in batch mode.
Hi VBE,
Thanks for your reply
I did add the call to my script with mkittab and it works but the problems is with the variables
When I am back in office I will try your recommendation with su
I was expecting it will use root as user
when I login as user root the script works perfect
When back in the office I will post the script and the entry i made in inittab
Thanks for your support
With kind regards
Hi guys,
For some reason a client has given us a Sun Netra T1 with Solaris 8 to administer for them. That's always good business. However, the other day we rebooted the machine and to our amazement, after doing the preliminary hardware tests, we got an error messgae saying that /etc/inittab was... (3 Replies)
Hi!
Is it possible to add more ttys in Solaris, like with inittab in Linux? I want to switch between the ttys with Alt F1+F2+F3 .... like Linux does.
How can i do this? (1 Reply)
How do i get the value of the variable from the called script(script2) to the calling script(script1) in ksh ?
I've given portion of the script here to explain the problem.
Portion of Script 1
=============
-----
-----
tmp=`a.ksh p1 p2 p3`
if then
# error processing
fi
-----... (10 Replies)
Hi,
In Solaris 9 and below release we are using the rc script in inittab. I don't have much idea abt inittab in Solaris.
In Solris 9 and below:
We use rc3 script to start up the server. And we run database script before the rc3.
os:23:respawn:/etc/init.d/database start >/dev/null 2>&1... (7 Replies)
Hi..
When i was just looking throught /etc/inittab file..
i had stuck with some problems that i dont known in shell scripts
Here how the lablel like
si
ca
lo
l1
etc works..
do scripts proivide any label features..
please help...
thanks in advance
esham (3 Replies)
Hi,
I have a solaris 10 server,which has a process running that communicates with other system.I have made following entry in the inittab file.
PM15:s12345:respawn:/ncm/bin/communicator
PM15 : Unique process ID
s12345 : run levels
respawn : if anytime the process... (2 Replies)
Hi
currently my linux instance is running in runlevel 3 ( someone has set the default to 3)
i have to change it to runlevel 5 . my question
1) does the editing of /etc/inittab needs system restart to enter runlevel 5.
2) how can we avoid system restart because if some users are... (3 Replies)
Today there was a situation where processes running from inittab was broken. Can someone help me understand, how to find out, who might have stopped those processes? Or how does it get broken?
G (2 Replies)
I am installing BusyBox on a device that does not have keyboard or serial connection, so I log into the system with SSH. I am in doubt about what to put in the inittab file. This is the content of the file:
::sysinit:/etc/init.d/rcS
::respawn:/bin/login
::shutdown:/sbin/swapoff -a... (1 Reply)
Hi All,
I am booting by Linux box with the run level 3 and it gets booted successfully.
I want to execute a script once the system is up and running in the run level 3. I was trying to add a entry to /etc/inittab to execute my script once the system is up.
I have added the below... (5 Replies)
Discussion started by: kalpeer
5 Replies
LEARN ABOUT OSF1
init
init(8) System Manager's Manual init(8)NAME
init - Process control initialization
SYNOPSIS
/sbin/init [0123456789MmQqSs]
DESCRIPTION
The init program initializes the system by creating and controlling processes. The processes run by init at each run level are defined in
the inittab file. The init program reads and processes the entries in the inittab file.
The init program considers the system to be in a run level at any given time; each run level has a specific group of processes that run at
that level. The init program operates in one of eleven run levels: 0-9 and Ss. Of these, only 0, s, 2, and 3 are configured in the inittab
file by default. The run level changes when a privileged user invokes init. The new init sends appropriate signals to the original init
that tell it which run level to change to.
Running the init program is the last step in the boot process after the root file system is mounted. The init program scans the inittab
file and looks for an entry with the initdefault keyword. If the entry is there, init uses the run level specified in that entry as the
initial run level to enter. If the entry is not found in the inittab file or if the inittab file does not exist, init requests that the
user enter a run level from the system console, /dev/console. If the user enters the letter s, init enters single user state, assigns the
virtual console terminal to the user's terminal and opens it for reading and writing. The su command is invoked and the system displays a
message on the console stating the location of the virtual console.
To change the run level, the user specifies either the 0, 2, 3, or s flag.
For the first post-boot execution of init to a run level other than single user, it searches the inittab file for entries at the new run
level that have the boot or bootwait keywords. If the run level that is specified matches the entry, the init program acts on these
entries before processing other entries in the inittab file. Any special initialization of the system, such as checking and mounting file
systems, takes place before users are allowed on the system. The init program then scans the inittab file to find all entries that are to
be handled for that level.
Before starting a new process, init reads each entry in the inittab file, and for each entry that should be respawned, init forks a child
process. After spawning all required processes, init waits for one of its descendant processes to stop, a power-fail signal, or a signal
that it should change the run level. If one of the preceding three conditions occurs, init reexamines the inittab file. You can add new
entries to the inittab file, but init does not reexamine the file until one of the three previous conditions actually occurs. To immedi-
ately reexamine the inittab file, invoke the init program with the q flag.
FLAGS
Shuts down and halts the system. Changes the run level to a multiuser state with local processes and daemons. Changes the run level to a
multiuser state with remote processes and daemons. Changes run level to that specified by the number flag in the /etc/inittab file. If no
such entry exists, no action is taken and no message is output. Moves control to the console device and halts to single-user mode. Forces
init to reexamine the entries in the inittab file and terminates any live processes which have had their configuration entries removed from
/etc/inittab. Users should be aware that when a getty(8) line has been removed from /etc/inittab, and a login shell is active on the ter-
minal line that was formerly designated in inittab as a getty entry, the login shell will be killed. Changes the run level to a single
user state with only the essential kernel services.
FILES
Specifies the command path Specifies the init command control file Specifies the permanent login accounting file
RELATED INFORMATION
Commands: getty(8), rc0(8), rc2(8), rc3(8), shutdown(8)
Calls: kill(2), reboot(2)
Files: inittab(4) delim off
init(8)