Sponsored Content
Operating Systems Solaris Service shutdown sequence via SMF Post 302598051 by jim mcnamara on Monday 13th of February 2012 07:51:48 AM
Old 02-13-2012
Use
Code:
svcadm enable [options] [servicename]
# and
svcadm disable ......

in the usual case statement construct.
Place the code in an executable script file in /etc/init.d : svcfoo
Two symlinks to /etc/init.d/svcfoo in /etc/rc3.d: S99foo & K99foo
You may want the S99foo symlink to be S10 and/or in a different directory: /etc/rc[n].d, because you want it started earlier. Change K[nn]foo as well to get what you want as well.
 

10 More Discussions You Might Find Interesting

1. Solaris

Smf managed service not starting

Hi Experts, While playing with smf in my local system ( which is not in production ) i am unable to restart the service svc:/network/nfs/server:default . I tried starting it in different way, however unable to restart the same. I was checking the dependency for that I disabled the... (11 Replies)
Discussion started by: kumarmani
11 Replies

2. Solaris

SMF service HELP

I would like to run command whenever system boot up, i.e "/opt/admin/script/closegen -c /opt/share/script/colsehg" How do I integrate above command in to SMF services. -sam (1 Reply)
Discussion started by: sam786
1 Replies

3. Solaris

Apache 2 doesnt create SMF service at installation

Hello everybody, I intended to use Apache 2 first time on my S10 U7 box. But the package (V2) is not ok for the developpers and they need 2.2.12 somehow. I removed Apache 1.3 and installed 2.2.12 with the stream package which I downloaded from Sunfreeware.com It's running perfectly if I start... (2 Replies)
Discussion started by: shadowfaxxxx
2 Replies

4. Solaris

Permission denied in SMF service log

I can't get the exact error message because I am at home, but on Solaris 10u5 machine I have at work, a few services are stuck in the maintenance state with the following error message in the individual service logs (/var/svc/log/FMRI:instance.log): Cannot chdir: permission denied Fortunately... (2 Replies)
Discussion started by: ilikecows
2 Replies

5. Red Hat

change the shutdown sequence in red hat linux

Hi, I use red hat linux kernel 2.6 I want to add the application shutdown in shutdown sequence . I add the K script in /etc/rc.d/ all sub directory for all running level . But the auto shutdown application is not appear when I type "shutdown -r now" .. There is no indication the application... (5 Replies)
Discussion started by: chuikingman
5 Replies

6. Infrastructure Monitoring

Using SMF to register & start a (Nagios) service

I'm trying to register & start a service using SMF on Solaris 10. It's nsca, part of the Nagios monitoring system. I've got nsca running fine as a detached process, and can manually create passive checks via send_nsca. But when I try to run nsca as a daemon, I need some advice. The nsca... (0 Replies)
Discussion started by: lyle
0 Replies

7. Solaris

Service shutdown sequence via SMF

Hi all, Is there any way to configure a certain service to be shutdown first via SMF? Thanks in advance Eugene (1 Reply)
Discussion started by: srage
1 Replies

8. Solaris

removing associated processes from a SMF service

I'm running Tibco Hawk (hawkhma and agent) on a number of solaris 10 boxes (both x86 and Sparc). Tibco Hawk is a monitoring system, that can monitor processs and logs on the OS and applications. It also have the ability to start a process, if it for some reason, have died. I have implemented... (2 Replies)
Discussion started by: u_paludan
2 Replies

9. Solaris

How to make SMF service start last?

I need to start a service among the last on a freshly booted system. Via the manifest, I've made it dependent on very milestone on the computer yet the service still comes back with an error that a kstat variable in the kernel does not exist. I run it right the service process right there... (6 Replies)
Discussion started by: JWH
6 Replies

10. UNIX for Advanced & Expert Users

Service smf ntp maintenance

Hello, My ntp service goes in maintenance mode in Solaris 11. I do "svcadm clear ntp", the service is back but after 1 minute it crashes but automatically restarted. After the third attempt it goes in maintenance again : After the clear : 1 minute later it crashes but it is... (2 Replies)
Discussion started by: bob74350
2 Replies
SYSTEMD-HALT.SERVICE(8) 				       systemd-halt.service					   SYSTEMD-HALT.SERVICE(8)

NAME
systemd-halt.service, systemd-poweroff.service, systemd-reboot.service, systemd-kexec.service, systemd-shutdown - System shutdown logic SYNOPSIS
systemd-halt.service systemd-poweroff.service systemd-reboot.service systemd-kexec.service /lib/systemd/systemd-shutdown /lib/systemd/system-shutdown/ DESCRIPTION
systemd-halt.service is a system service that is pulled in by halt.target and is responsible for the actual system halt. Similarly, systemd-poweroff.service is pulled in by poweroff.target, systemd-reboot.service by reboot.target and systemd-kexec.service by kexec.target to execute the respective actions. When these services are run, they ensure that PID 1 is replaced by the /lib/systemd/systemd-shutdown tool which is then responsible for the actual shutdown. Before shutting down, this binary will try to unmount all remaining file systems, disable all remaining swap devices, detach all remaining storage devices and kill all remaining processes. It is necessary to have this code in a separate binary because otherwise rebooting after an upgrade might be broken -- the running PID 1 could still depend on libraries which are not available any more, thus keeping the file system busy, which then cannot be re-mounted read-only. Immediately before executing the actual system halt/poweroff/reboot/kexec systemd-shutdown will run all executables in /lib/systemd/system-shutdown/ and pass one arguments to them: either "halt", "poweroff", "reboot" or "kexec", depending on the chosen action. All executables in this directory are executed in parallel, and execution of the action is not continued before all executables finished. Note that systemd-halt.service (and the related units) should never be executed directly. Instead, trigger system shutdown with a command such as "systemctl halt" or suchlike. SEE ALSO
systemd(1), systemctl(1), systemd.special(7), reboot(2), systemd-suspend.service(8) systemd 237 SYSTEMD-HALT.SERVICE(8)
All times are GMT -4. The time now is 09:16 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy