07-22-2008
Someone mentioned that perhaps since this program runs in the background, that inittab thinks the program has ended and keeps respawning again and again.
But I don't know how to write a daemon that runs in the foreground. Is there such a thing? Then it would become a program, and no longer be a daemon anymore.
Not sure, dont' completely understand.
Last edited by jeffpas; 07-22-2008 at 04:07 PM..
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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)
Discussion started by: donald1111
1 Replies
2. UNIX for Dummies Questions & Answers
Ran into a new one today at work......
I was told to start 2 servers which were shut down due to a power outage(I don't believe they were shut down incorrectly).
After fsck, both console logins appear with the message:
INIT: Command is respawning too rapidly. Check for possible errors.
>... (5 Replies)
Discussion started by: finster
5 Replies
3. UNIX for Dummies Questions & Answers
Hello.
System is a HP Visualize C3600 running X11 and after a power failure machine will not boot (see error messages below)
From what I've read, this may be caused by a corrupted etc/inittab file. Solution suggested on other websites is to boot in single user mode and edit file inittab... (2 Replies)
Discussion started by: westcoast
2 Replies
4. HP-UX
INIT:Command is respawning too rapidly
Check for errors:
id:cons /usr/sbin/getty console console
A solution I read about in a different HPUX Forums help pages on line, said to add the -h option to this command in the /etc/inittab file to correct the problem.
I tried this and it did not... (2 Replies)
Discussion started by: 1bigdog
2 Replies
5. Solaris
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)
Discussion started by: kalpeer
7 Replies
6. Solaris
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)
Discussion started by: asalman.qazi
2 Replies
7. UNIX for Dummies Questions & Answers
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)
Discussion started by: ggayathri
2 Replies
8. AIX
hello,
i have an AIX6.1.7.2 machine that it was upgraded recently from AIX5.3.9.4.
when i kill system services that should restart automatically like /usr/sbin/cron it doesnt start.
i checked my /etc/inittab file and i confirmed that this service is in respawn status so when i kill this process... (2 Replies)
Discussion started by: omonoiatis9
2 Replies
9. UNIX for Dummies Questions & Answers
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)
Discussion started by: richard78
1 Replies
10. Shell Programming and Scripting
Hi to all ,
i wrote a small script and i add it to inittab to start the script during Startup. The script works fine , if i call it from the prompt but if it is call from inittab it is runnng too but it does not recognize system variable like USER , LOGNAME.
Since i running out of ideas i... (12 Replies)
Discussion started by: Nadielosabra
12 Replies
LEARN ABOUT CENTOS
setroubleshootd
setroubleshootd(8) setroubleshootd(8)
NAME
setroubleshootd - setroubleshoot daemon
SYNOPSIS
setroubleshootd [-d] [-f] [-h] [-c config]
DESCRIPTION
This manual page describes the setroubleshootd program.
setroubleshootd is the dbus service in the setroubleshoot system. setroubleshoot is used to diagnose SELinux denials and attempts to pro-
vide user friendly explanations for a SELinux denial (e.g. AVC) and recommendations for how one might adjust the system to prevent the
denial in the future.
In a standard configuration setroubleshoot is composed of two components, sealert and setroubleshootd.
setroubleshootd is a system daemon which runs with root privileges and listens for audit events emitted from the kernel related to SELinux.
When the setroubleshootd daemon sees an SELinux AVC denial it runs a series of analysis plugins which examines the audit data related to
the AVC. It records the results of the analysis and signals any clients which have attached to the setroubleshootd daemon that a new alert
has been seen.
OPTIONS
-f --nofork
Do not fork the daemon
-d --debug
Do not exit after 10 seconds
-h --help
Show this message
-c --config
section.option=value set a configuration value
AUTHOR
This man page was written by Dan Walsh <dwalsh@redhat.com>.
SEE ALSO
sealert(8),selinux(8)
20100520 setroubleshootd(8)