I have a command in init that trys to start a daemon and open a log, but a get an error error that the file access permissions do not allow the specified action. My permissions on the log file are:
The logfile is written to by the main application during processing, but on bootup the daemon fails to open.
So my question is on bootup is init run by the root user?
Last edited by methyl; 03-27-2012 at 05:06 PM..
Reason: please use code tags
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)
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)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT OSF1
writesrv
writesrv(8) System Manager's Manual writesrv(8)NAME
writesrv - Lets users send messages to and receive messages from a remote system.
SYNOPSIS
/usr/sbin/writesrv
DESCRIPTION
The writesrv daemon allows users to send messages to users on a remote system, and to receive responses from users on a remote system with
the write command.
The writesrv command receives incoming requests from a write command and creates a server process to handle the request. This server
process communicates with the client process (write) and provides whatever services are requested.
To perform these services, the writesrv daemon creates a socket on the port defined in the /etc/services file. All requests for service go
as messages to this socket.
STARTING AND STOPPING writesrv.
You can cause the writesrv daemon to be started during system boot with /sbin/init.d/write. The writesrv daemon starts automatically if the
WRITESRV variable is defined properly in /etc/re.config. To start writesrv automatically during system boot, do the following as superuser.
rcmgr set WRITESRV yes
To prevent writesrv from starting automatically during system boot, do the following as superuser:
rcmgr set WRITESRV no
By default, writesrv is not set and therefore /usr/sbin/writesrv does not run.
You can start the writesrv daemon manually as follows:
/sbin/init.d/write start
You can stop writesrv manually as follows:
/sbin/init.d/write stop
NOTES
If the writesrv daemon terminates abnormally (that is, for a system crash, a power failure, or the kill -9 command), someone must manually
clean out the /usr/spool/writesrv directory to remove any files left behind.
RELATED INFORMATION
Commands: write(1)
Files: services(4) delim off
writesrv(8)