From: David Steinbrunner Date: Thu, 16 May 2013 17:13:01 +0000 (-0700) Subject: spelling (RT#85351) (committed by ether) X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=gitmo%2FMooseX-Daemonize.git;a=commitdiff_plain;h=b37fcc5f9a086f8204bea2490775aaea6d3859e3 spelling (RT#85351) (committed by ether) --- diff --git a/lib/MooseX/Daemonize.pm b/lib/MooseX/Daemonize.pm index c9fdb76..83680f4 100644 --- a/lib/MooseX/Daemonize.pm +++ b/lib/MooseX/Daemonize.pm @@ -213,7 +213,7 @@ sub stop { $self->clear_exit_code; # if the pid is not running - # then we dont need to stop + # then we don't need to stop # anything ... if ($self->pidfile->is_running) { @@ -351,7 +351,7 @@ The maintainers of this module now recommend using L instead. =head1 DESCRIPTION -Often you want to write a persistant daemon that has a pid file, and responds +Often you want to write a persistent daemon that has a pid file, and responds appropriately to Signals. This module provides a set of basic roles as an infrastructure to do that. @@ -410,7 +410,7 @@ be set via Getopt's -f. =item I If true, the process will not perform the typical double-fork, which is extra -added protection from your process accidentally aquiring a controlling terminal. +added protection from your process accidentally acquiring a controlling terminal. More information can be found by Googling "double fork daemonize". =item I @@ -534,7 +534,7 @@ Handle a HUP signal. By default calls C<$self->restart()> =head2 Exit Code Methods -These are overriable constant methods used for setting the exit code. +These are overridable constant methods used for setting the exit code. =over 4 diff --git a/lib/MooseX/Daemonize/Core.pm b/lib/MooseX/Daemonize/Core.pm index 38d3549..3eb7252 100644 --- a/lib/MooseX/Daemonize/Core.pm +++ b/lib/MooseX/Daemonize/Core.pm @@ -39,7 +39,7 @@ has dont_close_all_files => ( sub _get_options { my ($self, %options) = @_; - # backwards compability.. old code might be calling daemon_fork/_detach with options + # backwards compatibility.. old code might be calling daemon_fork/_detach with options foreach my $opt (qw( ignore_zombies no_double_fork dont_close_all_files )) { $self->$opt( $options{ $opt } ) if ( defined $options{ $opt } ); } @@ -83,7 +83,7 @@ sub daemon_detach { umask 0; # clear the file creation mask unless ( $self->dont_close_all_files ) { - # get the max numnber of possible file descriptors + # get the max number of possible file descriptors my $openmax = POSIX::sysconf( &POSIX::_SC_OPEN_MAX ); $openmax = 64 if !defined($openmax) || $openmax < 0; @@ -188,7 +188,7 @@ daemon process or not. Setting this attribute to true will cause this method to not perform the typical double-fork, which is extra added protection from your process -accidentally aquiring a controlling terminal. More information can be +accidentally acquiring a controlling terminal. More information can be found above, and by Googling "double fork daemonize". If you the double-fork behavior off, you might want to enable the @@ -221,7 +221,7 @@ the built in fork, it returns the child pid to the parent process, 0 to the child process. It will also set the is_daemon flag appropriately. -The C<%options> argument remains for backwards compatability, but +The C<%options> argument remains for backwards compatibility, but it is suggested that you use the attributes listed above instead. =item B @@ -229,7 +229,7 @@ it is suggested that you use the attributes listed above instead. This detaches the new child process from the terminal by doing the following things. -The C<%options> argument remains for backwards compatability, but +The C<%options> argument remains for backwards compatibility, but it is suggested that you use the attributes listed above instead. =over 4 @@ -271,7 +271,7 @@ false), this method will simply return and do nothing. This will simply call C followed by C. -The C<%options> argument remains for backwards compatability, but +The C<%options> argument remains for backwards compatibility, but it is suggested that you use the attributes listed above instead. =item meta()