10-17-2012
It's a very weird model, as server daemons usually log to flat files in text, sometimes via syslog(), and take requests on tcp/ip, named pipes or message queues (mmap()'d files would work, too). You could run each on a Xnc desktop and connect with vncviewer as necessary. What is your security model?
9 More Discussions You Might Find Interesting
1. AIX
I understand that by putting in entries into the /etc/inittab file. We can actually call the our scripts during startup.
mkitab "start_server:2:once:sh /scripts/startserver.sh"
Would the system wait for startserver.sh finish executing before it goes to another entry? and how long would it... (1 Reply)
Discussion started by: vincente
1 Replies
2. Linux
I've created the following link in order to startup apache tomcat on startup, however, it does not seem to run. Am I missing something out?
:confused:
/etc/init.d
lrwxrwxrwx 1 root root 16 Sep 5 14:59 K73ypbind -> ../init.d/ypbind
lrwxrwxrwx 1 root root 16 Sep 11 13:09 S100tomcat ->... (5 Replies)
Discussion started by: jon80
5 Replies
3. AIX
Hello Friends,
Does anyone know how to create a startup script for Jboss on IBM AIX 5.3?
Please help me, I'd be highly grateful to you...
Thanks & Regards,
Vinit (0 Replies)
Discussion started by: vpatil6688
0 Replies
4. HP-UX
Hi all
We have HP UX 11.23 installed on 4 RISC servers (2 oracle databases, 2 Oracle App Servers) , we are in a construction period , so the power failure may happen more than once a day.
I need to learn how to create an automatic startup services as in Windows, if we know that the services... (5 Replies)
Discussion started by: kafaween
5 Replies
5. AIX
Hi,
I am trying to start services on system reboot on AIX.
Have put the S* links under rd2.d & K* links under other rc*.d
At the moment, all scripts are getting called.
However, the services aren't coming up.
Where can i find the logs for these to check what failed. (8 Replies)
Discussion started by: vibhor_agarwali
8 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I have to perform an audit of a system at work and I am looking at its /etc/rc3.d:
K01tog-pegasus K74nscd S08iptables S50openemm
K01yum K74ntpd S09isdn S55cups
K02NetworkManager K85mdmpd S09pcmcia S55sshd
K03rhnsd ... (8 Replies)
Discussion started by: mojoman
8 Replies
7. AIX
hi,
If we place Sxx (startup script) and Kxx(shutdown script) in /etc/rc.d/rc2.d,then it would start and stop automatically(assume they are linked to other script that actually starts/stops).
is there really a link needed here to /etc/rc.d/init.d? if not,what is the use of this directory..?... (1 Reply)
Discussion started by: to_bsr
1 Replies
8. UNIX for Advanced & Expert Users
Can someone please tell me how to run xsession startup scripts whenever I start or after I restart my X session? I'm not trying to do anything fancy I just want this to run. This makes life a lot easier when I use a dual monitor.
xrandr --output VGA1 --mode 1024x768 --rate 60 (7 Replies)
Discussion started by: cokedude
7 Replies
9. Solaris
Hi all,
I have a server in maintenance mode and need to boot it up. Its due to a broken service "RepX".
I need to stop the service from trying to start at boot up but i can't find where it is booting up from... it is not in any of the rcX.d directories and the two locations i have found it... (6 Replies)
Discussion started by: Tommyk
6 Replies
vxiod(7) Miscellaneous Information Manual vxiod(7)
NAME
vxiod - Veritas Volume Manager I/O daemon process control device
DESCRIPTION
The vxiod device in Veritas Volume Manager (VxVM) is used to control the number of volume I/O daemons active on the system. A process con-
text is necessary to implement the plex consistency recovery and writeback error handling policies for multi-plex volumes, and for continu-
ing normal I/O after a log write if the volume has logging enabled. It is also required for the plex recovery performed with a mirrored
volume in the read/writeback mode.
There are three aspects of I/O daemon operations:
o General I/O
o Error handling
o Log handling
I/O handling is achieved by an ioctl command that does not return, but instead calls the vxiod routine to wait for errors or I/O requests
and process them. When an error occurs, if there are no I/O daemons active, the I/O simply turns into a failure on that plex. If a gen-
eral I/O request is queued up when no daemons exist, then the I/O will hang forever until a daemon process is created. If I/O daemons are
active, then the I/O is put on a work queue and the daemons are awakened. A daemon takes an error request and tries to read other plexes
until a read succeeds or all plexes have been tried. Then, if the writeback facility is enabled, the daemon tries to write the good data
to each plex that failed on the read. If the write is successful, the read error is nullified. An I/O request is handled in a similar
manner.
Logging is handled in a similar manner. An ioctl command, which does not return, is issued to create a daemon for each volume which has
logging enabled. This daemon monitors two queues: one queue of I/O which was started while the log was busy (the ``log'' queue), and
another queue of requests which have been logged and now need to be started (the ``ready'' queue). I/O requests are taken from the log
queue when the log is no longer busy, and another log write is started. Completion of a log write results in all I/O requests which have
just been logged being placed on the I/O daemon's ready queue where they are immediately started.
One mechanism finds out how many I/O error daemons are running, and another mechanism allows a process to become an I/O daemon. Before a
process becomes an I/O daemon, it should close all open files and detach from the controlling tty. An I/O or logging daemon cannot be
killed except through an explicit ioctl.
FILES
/dev/vx/iod vxiod control device
SEE ALSO
vxiod(1M), ioctl(2)
VxVM 5.0.31.1 24 Mar 2008 vxiod(7)