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
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 REDHAT
sulogin
SULOGIN(8) Linux System Administrator's Manual SULOGIN(8)NAME
sulogin -- Single-user login
SYNOPSIS
sulogin [ -e ] [ -p ] [ -t timeout ] [ tty-device ]
DESCRIPTION
sulogin can be invoked by init(8) when the system goes into single user mode (this is done through an entry in inittab(5)). Init also tries
to execute sulogin when it is passed the -b flag from the bootmonitor (eg, LILO).
The user is prompted
Give root password for system maintenance
(or type Control-D for normal startup):
sulogin will connected to the current terminal, or to the optional device that can be specified on the command line (typically /dev/con-
sole).
If the -p flag was set, the single-user shell will be invoked with a dash as the first character in argv[0]. That will cause most shells to
behave as a login shell. The default is not to do this, so that the shell will not read /etc/profile or $HOME/.profile at startup.
After the user exits the single-user shell, or presses control-d at the prompt, the system will (continue to) boot to the default runlevel.
ENVIRONMENT VARIABLES
sulogin looks for the environment variable SUSHELL or sushell to determine what shell to start. If the environment variable is not set, it
will try to execute root's shell from /etc/passwd. If that fails it will fall back to /bin/sh.
This is very valuable together with the -b flag to init. To boot the system into single user mode, with the root file system mounted
read/write, using a special "failsafe" shell that is statically linked (this example is valid for the LILO bootprompt)
boot: linux -b rw sushell=/sbin/sash
FALLBACK METHODS
sulogin checks the root password using the standard methods first. If the -e option was specified, sulogin examines the next files to find
the root password. If they are damaged, or non-existant, it will use fallback methods that even go so far as to provide you with a shell
prompt without asking for the root password if they are irrepairably damaged.
/etc/passwd,
/etc/shadow (if present)
AUTHOR
Miquel van Smoorenburg <miquels@cistron.nl>
SEE ALSO init(8), inittab(5).
11 Sep 2000 SULOGIN(8)