02-07-2007
Services persistant across reboot
Hi All,
I need to run a daemon which should start automatically during reboot.
which all files i need to alter/modify ?
/etc/inittab ?
Thanks,
Amit
10 More Discussions You Might Find Interesting
1. Solaris
Hi Guru's
Can any want here could explain to me the different between soft reboot and hard reboot .
Best Regards
Seelan (3 Replies)
Discussion started by: seelan3
3 Replies
2. AIX
Hi,
I am nerw to AIX.
how can i make certain services to be persistant across reboot,similar to "chkconfig" in linux.
Thanks,
amit (2 Replies)
Discussion started by: amit4g
2 Replies
3. UNIX for Dummies Questions & Answers
hi,
i want to know cpu utilizatiion per process per cpu..for single processor also if multicore in linux ..to use these values in shell script to kill processes exceeding cpu utilization.ps (pcpu) command does not give exact values..top does not give persistant values..psstat,vmstat..does njot... (3 Replies)
Discussion started by: pankajd
3 Replies
4. Shell Programming and Scripting
Hi
What is the best way to reboot a Linux computer?
i) Press the power switch
ii) type 'init 6' as any user, then enter the root password when prompted
iii) Pour metal filings in the top of the computer.
iv) su to root then type 'init 6' (6 Replies)
Discussion started by: tjay83
6 Replies
5. AIX
Hello,
Running AIX 6.1, AIX machine is HACMP node.
Recently I set up ntp service. Started xntpd by hand - everythig is OK. Configured xntpd to start after reboot and rebooted the machine. After reboot checked xntpd:
# lssrc -a|grep ntp
xntpd tcpip ... (5 Replies)
Discussion started by: vilius
5 Replies
6. Red Hat
I had a doubt if any services need to be restarted if port no in /etc/services in an RHEL setup is changed. For eg, the port no of 443 for SSL may need to be changed.
I hope my query is clear whether any services need to be restarted if port no in /etc/services is changed.
Please revert with... (10 Replies)
Discussion started by: RHCE
10 Replies
7. Shell Programming and Scripting
Hi,
I just started working on a script. After my research, i found a command which can help me:
AIM: To build a script which starts the services (Services 1) on server 1 automatically whenever its down. And it has a dependency on other service (Service 2) on Server 2.
So my script has to... (4 Replies)
Discussion started by: draghun9
4 Replies
8. Solaris
Hello all, I'm not having much luck figuring out why this machine keeps sending these messages. svcs -xv is clean. Machine was just patched via latest IPS. I would appreciate any help offered.
Jan 21 00:48:54 t4 in.dlmpd: dlm_icmp_sock_handler(127.0.0.1/127.0.0.1) incorrect ICMP type 3
Jan... (2 Replies)
Discussion started by: LittleLebowski
2 Replies
9. Linux
Hi All,
My application uses three different sub-services to make complete application up and running to normal.
The entry of all the three services are present in /etc/init.d directory with proper softlink created to application home path where it actually exists.
In one rare case one of the... (3 Replies)
Discussion started by: hk_kamozalwar
3 Replies
10. Solaris
Hello,
This is Solaris-10 server, running with 4 non-global zones.
This server was hung today and I had to reboot it forcefully from console. Then root file-system was not clean and I had to run fsck from failsafe mode. After it came back in run-level-3, lot of services are showing in... (3 Replies)
Discussion started by: solaris_1977
3 Replies
reboot(1M) reboot(1M)
NAME
reboot - restart the operating system
SYNOPSIS
/usr/sbin/reboot [-dlnq] [boot_arguments]
The reboot utility restarts the kernel. The kernel is loaded into memory by the PROM monitor, which transfers control to the loaded kernel.
Although reboot can be run by the super-user at any time, shutdown(1M) is normally used first to warn all users logged in of the impending
loss of service. See shutdown(1M) for details.
The reboot utility performs a sync(1M) operation on the disks, and then a multi-user reboot is initiated. See init(1M) for details. On
systems, reboot may also update the boot archive as needed to ensure a successful reboot.
The reboot utility normally logs the reboot to the system log daemon, syslogd(1M), and places a shutdown record in the login accounting
file /var/adm/wtmpx. These actions are inhibited if the -n or -q options are present.
Normally, the system reboots itself at power-up or after crashes.
The following options are supported:
-d Force a system crash dump before rebooting. See dumpadm(1M) for information on configuring system crash dumps.
-l Suppress sending a message to the system log daemon, syslogd(1M) about who executed reboot.
-n Avoid calling sync(2) and do not log the reboot to syslogd(1M) or to /var/adm/wtmpx. The kernel still attempts to sync
filesystems prior to reboot, except if the -d option is also present. If -d is used with -n, the kernel does not attempt to
sync filesystems.
-q Quick. Reboot quickly and ungracefully, without shutting down running processes first.
The following operands are supported:
boot_arguments An optional boot_arguments specifies arguments to the uadmin(2) function that are passed to the boot program and kernel
upon restart. The form and list of arguments is described in the boot(1M) and kernel(1M) man pages.. If the arguments are
specified, whitespace between them is replaced by single spaces unless the whitespace is quoted for the shell. If the
boot_arguments begin with a hyphen, they must be preceded by the -- delimiter (two hyphens) to denote the end of the reboot
argument list.
Example 1: Passing the -r and -v Arguments to boot
In the following example, the delimiter -- (two hyphens) must be used to separate the options of reboot from the arguments of boot(1M).
example# reboot -dl -- -rv
Example 2: Rebooting Using a Specific Disk and Kernel
The following example reboots using a specific disk and kernel.
example# reboot disk1 kernel.test/unix
/var/adm/wtmpx login accounting file
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
mdb(1), boot(1M), dumpadm(1M), fsck(1M), halt(1M), init(1M), kernel(1M), shutdown(1M), sync(1M), syslogd(1M), sync(2), uadmin(2),
reboot(3C), attributes(5)
The reboot utility does not execute the scripts in /etc/rcnum.d or execute shutdown actions in inittab(4). To ensure a complete shutdown
of system services, use shutdown(1M) or init(1M) to reboot a Solaris system.
11 Apr 2005 reboot(1M)