File perl-FCGI-ProcManager.spec of Package perl-FCGI-ProcManager

Overview Repositories Revisions Requests Users Attributes Meta

File perl-FCGI-ProcManager.spec of Package perl-FCGI-ProcManager (Revision e4d3ba51c6752140e851192c857a54a4)

Currently displaying revision e4d3ba51c6752140e851192c857a54a4 , Show latest

#
# spec file for package perl-FCGI-ProcManager
#
# Copyright (c) 2014 SUSE LINUX Products GmbH, Nuernberg, Germany.
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via http://bugs.opensuse.org/
#

Name:           perl-FCGI-ProcManager
Version:        0.24
Release:        0
%define cpan_name FCGI-ProcManager
Summary:        Functions for managing FastCGI applications
License:        CHECK(Distributable)
Group:          Development/Libraries/Perl
Url:            http://search.cpan.org/dist/FCGI-ProcManager/
Source          http://search.cpan.org/CPAN/authors/id/B/BO/BOBTFISH/%{cpan_name}-%{version}.tar.gz
BuildRequires:  perl
BuildRequires:  perl-macros
BuildRoot:      %{_tmppath}/%{name}-%{version}-build
BuildArch:      noarch
%{perl_requires}

%description
FCGI::ProcManager is used to serve as a FastCGI process manager. By
re-implementing it in perl, developers can more finely tune performance in
their web applications, and can take advantage of copy-on-write semantics
prevalent in UNIX kernel process management. The process manager should be
invoked before the caller''s request loop

The primary routine, 'pm_manage', enters a loop in which it maintains a
number of FastCGI servers (via fork(2)), and which reaps those servers when
they die (via wait(2)).

'pm_manage' provides too hooks:

C<managing_init> - called just before the manager enters the manager loop.
 C<handling_init> - called just before a server is returns from C<pm_manage>

It is necessary for the caller, when implementing its request loop, to
insert a call to 'pm_pre_dispatch' at the top of the loop, and then
7'pm_post_dispatch' at the end of the loop.

Signal Handling
    FCGI::ProcManager attempts to do the right thing for proper shutdowns
    now.

When it receives a SIGHUP, it sends a SIGTERM to each of its children,
    and then resumes its normal operations.

When it receives a SIGTERM, it sends a SIGTERM to each of its children,
    sets an alarm(3) "die timeout" handler, and waits for each of its
    children to die. If all children die before this timeout, process
    manager exits with return status 0. If all children do not die by the
    time the "die timeout" occurs, the process manager sends a SIGKILL to
    each of the remaining children, and exists with return status 1.

In order to get FastCGI servers to exit upon receiving a signal, it is
    necessary to use its FAIL_ACCEPT_ON_INTR. See FCGI.pm's description of
    FAIL_ACCEPT_ON_INTR. Unfortunately, if you want/need to use CGI::Fast,
    it appears currently necessary to modify your installation of FCGI.pm,
    with something like the following:

-*- patch -*-
     --- FCGI.pm     2001/03/09 01:44:00     1.1.1.3
     +++ FCGI.pm     2001/03/09 01:47:32     1.2
     @@ -24,7 +24,7 @@
      *FAIL_ACCEPT_ON_INTR = sub() { 1 };
      
      sub Request(;***$$$) {
     -    my @defaults = (\*STDIN, \*STDOUT, \*STDERR, \%ENV, 0, 0);
     +    my @defaults = (\*STDIN, \*STDOUT, \*STDERR, \%ENV, 0, FAIL_ACCEPT_ON_INTR());
          splice @defaults,0,@_,@_;
          RequestX(@defaults);
      }   
     -*- end patch -*-

Otherwise, if you don't, there is a loop around accept(2) which
    prevents os_unix.c OS_Accept() from returning the necessary error when
    FastCGI servers blocking on accept(2) receive the SIGTERM or SIGHUP.

FCGI::ProcManager uses POSIX::sigaction() to override the default
    SA_RESTART policy used for perl's %SIG behavior. Specifically, the
    process manager never uses SA_RESTART, while the child FastCGI servers
    turn off SA_RESTART around the accept(2) loop, but re-enstate it
    otherwise.

The desired (and implemented) effect is to give a request as big a
    chance as possible to succeed and to delay their exits until after
    their request, while allowing the FastCGI servers waiting for new
    requests to die right away.

%prep
%setup -q -n %{cpan_name}-%{version}

%build
%{__perl} Makefile.PL INSTALLDIRS=vendor
%{__make} %{?_smp_mflags}

%check
%{__make} test

%install
%perl_make_install
%perl_process_packlist
%perl_gen_filelist

%clean
%{__rm} -rf %{buildroot}

%files -f %{name}.files
%defattr(644,root,root,755)
%doc ChangeLog COPYING README

%changelog

Places

File perl-FCGI-ProcManager.spec of Package perl-FCGI-ProcManager (Revision e4d3ba51c6752140e851192c857a54a4)

Places