blob: 2663a13d4074f25d8e6c2dfd20615d8032074a24 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
// -*- C++ -*-
#ifndef _SHUTDOWN_UTILS_H
#define _SHUTDOWN_UTILS_H
#include /**/ "ace/pre.h"
// $Id$
#include "orbsvcs/svc_utils_export.h"
#include "tao/Versioned_Namespace.h"
#include "ace/Event_Handler.h"
#include "ace/Signal.h"
#include "ace/Sig_Handler.h"
TAO_BEGIN_VERSIONED_NAMESPACE_DECL
/**
* \brief Abstract definition for a Functor that shuts down a particular service.
*
* When subclassing, the developer should provide a constructor or
* other initialization method that somehow couples an instance of the
* functor to the service implementation. She should also provide an
* implementation of operator()(int which_signal) that actually performs
* the shutdown.
*/
class TAO_Svc_Utils_Export Shutdown_Functor
{
public:
virtual void operator() (int which_signal) = 0;
protected:
Shutdown_Functor (void) {}
virtual ~Shutdown_Functor (void) {}
};
/**
* \brief Class that permits graceful shutdown of a service.
*
* Services require graceful shutdown. Sending a SIGTERM (which is
* what Ctrl-C does on Unix) should trigger a graceful shutdown, not
* simply a graceful termination of the process.
*
* This class can be used to capture signals and gracefully shut down
* the service.
*/
class TAO_Svc_Utils_Export Service_Shutdown : public ACE_Event_Handler
{
public:
Service_Shutdown (Shutdown_Functor& sf);
Service_Shutdown (Shutdown_Functor& sf, ACE_Sig_Set& which_signals);
~Service_Shutdown ();
void set_signals (ACE_Sig_Set& which_signals);
virtual int handle_signal (int which_sig,
siginfo_t* siginfo,
ucontext_t* context);
protected:
Shutdown_Functor& functor_;
ACE_Sig_Handler shutdown_;
ACE_Sig_Set registered_signals_;
};
TAO_END_VERSIONED_NAMESPACE_DECL
#include /**/ "ace/post.h"
#endif
|
