03-27-2012
It turns out that the log's location needed to be explicitly defined in a config file when starting the daemon from init. This is even though it was writing to the log successfully after manual initialization.
Also, I will post more information next time. Thanks for your quick response.
This User Gave Thanks to pong3d For This Post:
9 More Discussions You Might Find Interesting
1. HP-UX
I want to get my telnetd to run on startup and was wondering where it was? im used to having it in /etc/init.d/rc.d but it is not the same in hp-ux :(
thanks all (4 Replies)
Discussion started by: emplate
4 Replies
2. Shell Programming and Scripting
we have this script that stops, starts and monitor process scheduler. prcs_control. this script runs perfectly when executed by ps_user.
we are now creating a new script that will run this script and is executed by root. this script needs to execute the prcs_control as ps_user because root can... (1 Reply)
Discussion started by: tads98
1 Replies
3. HP-UX
Hello.
system fails on reboot this AM.
received message about not possible for kernel to find process that caused crash.
system does memory dump succesfully, then tries to boot again.
looking further at messages during this time, i'm getting 'init died with return value 256'...system panic... (12 Replies)
Discussion started by: mrviking
12 Replies
4. Shell Programming and Scripting
Hi All,
Am using the below command to start my application using the root user
su - bin -c "/home/bin/test/start.sh"
but am getting the error becaue i have set some environment varibales in bin's .profile
when i execute the command start.sh by logging directly into bin account it's... (9 Replies)
Discussion started by: ravi.sri24
9 Replies
5. Shell Programming and Scripting
Hi,
I have a linux redhat 9 server and I am concerned about the security on that server.
I would like to be able to write a script that records all the commands that were typed at the command prompt before the user calls the 'history -c' command and deletes all the history.
I was thinking about... (4 Replies)
Discussion started by: mishkamima
4 Replies
6. Solaris
Hi all.
On one workstation run Solaris 10 a simple user can to execute 'init 0' command without input (su and root password).
Example:
% init 0
%
OK
I don't understand how user can execute 'init 0' command on this workstation?
1) I checked /usr/local/etc/sudoers all lines are... (6 Replies)
Discussion started by: wolfgang
6 Replies
7. Boot Loaders
Hi Experts,
I am doing PXE boot for my GNU/Linux device and pxelinux.0 loads the kernel as well as initrd images I have mentioned in the config file but it looks like it is not considering the init= option. Instead it starts the default INIT program.
I wanted my customized init program to be... (3 Replies)
Discussion started by: learn more
3 Replies
8. Solaris
Hello all,
Fairly simple question here. I know that in Solaris 10 there is a way to tell a system running solaris 10 to init 0 and then boot disk1 all in the same command line from a SSH window. That way once you hit enter it then performs the init 0 and then does the boot disk1. ... (2 Replies)
Discussion started by: tording99z28
2 Replies
9. Solaris
Dear all,
I have a solaris 10 in my environment (VMware virtual machine). recently I increased the harddisk size from the VMware and reboot my server. after reboot the os is unable to boot and gives the below error message.
exec(/sbin/init) file not found
press any key to restart
... (3 Replies)
Discussion started by: krishna001
3 Replies
INIT(8) System Manager's Manual INIT(8)
NAME
init, rc - process control initialization
SYNOPSIS
/etc/init
/etc/rc
DESCRIPTION
Init is invoked as the last step of the boot procedure (see boot(8)). Generally its role is to create a process for each typewriter on
which a user may log in.
When init first is executed the console typewriter /dev/console. is opened for reading and writing and the shell is invoked immediately.
This feature is used to bring up a single-user system. If the shell terminates, init comes up multi-user and the process described below
is started.
When init comes up multiuser, it invokes a shell, with input taken from the file /etc/rc. This command file performs housekeeping like
removing temporary files, mounting file systems, and starting daemons.
Then init reads the file /etc/ttys and forks several times to create a process for each typewriter specified in the file. Each of these
processes opens the appropriate typewriter for reading and writing. These channels thus receive file descriptors 0, 1 and 2, the standard
input, output and error files. Opening the typewriter will usually involve a delay, since the open is not completed until someone is
dialed up and carrier established on the channel. Then /etc/getty is called with argument as specified by the last character of the ttys
file line. Getty reads the user's name and invokes login(1) to log in the user and execute the shell.
Ultimately the shell will terminate because of an end-of-file either typed explicitly or generated as a result of hanging up. The main
path of init, which has been waiting for such an event, wakes up and removes the appropriate entry from the file utmp, which records cur-
rent users, and makes an entry in /usr/adm/wtmp, which maintains a history of logins and logouts. Then the appropriate typewriter is
reopened and getty is reinvoked.
Init catches the hangup signal SIGHUP and interprets it to mean that the system should be brought from multi user to single user. Use
`kill -1 1' to send the hangup signal.
FILES
/dev/tty?, /etc/utmp, /usr/adm/wtmp, /etc/ttys, /etc/rc
SEE ALSO
login(1), kill(1), sh(1), ttys(5), getty(8)
INIT(8)