You installed this package using a documented procedure.
You can start Tomcat manually. Good!!!
The procedure created a script in /etc/rc2.d/S20tomcat7 but it doesn't run at boot time.
As per my post #12 you can test this manually to see any errors.
Pay particular attention to VBE's comment about run levels.
It could be that the script in rc2.d is the stop script, and the start script is in rc3.d, I don't know LinuxMint. Perhaps rc2.d is start and rc1.d is stop.
Take a look around and see.
Then, logged in as root you should be able to start and stop Tomcat from the command line using these scripts. Post any errors.
Dear Experts ,
I want to stop and Start tomcat at the time of shutdown and startup of our server . I was trying to stop tomcat with following command
# su - dm -c "/export/home/Finder/FinderWeb/jakarta-tomcat-3.3.1a/bin/shutdown.sh"
but i am getting following error. Please suggest .... (1 Reply)
Hi,
I have apache ,jboss and jon instances on various linux boxes.I need to create a generic startup script to restart those instances on server reboot.The script requirement is :
It should take the name of instances from one text file named active-servers and recycle those instances.
1.... (6 Replies)
hi all
I have a problem how to write a shell script which delete files/folder form directory whenever system boot and copy last updated folder/file in the specified directory.pse help me ASAP.
i write a script which copy files in directory.I want when system boot up using script it check whether... (1 Reply)
Great tins massive!
Im Manqoba from Midrand, South Africa...
I have installed Apache and PHP on a solaris 9 box, using the packages below:
apache-2.2.14-sol9-sparc-local
php-5.2.13-sol9-sparc-local
After installing the packages I edited my httpd.conf file, to load the php5 module when... (10 Replies)
Hello there!
I need help.
Everytime I login to my ssh, i see this:
-bash: .export: command not found
-bash: .export: command not found
-bash: .export: command not found
-bash: .export: command not found
any help ?
thanks (0 Replies)
I'm running Solaris 5.9 and Apache 2....
I've created a startup script for Apache....but it doesn't work!!!
it resides in /etc/init.d and has a link to /etc/rc3.d
and if it run it as /etc/init.d/apache_start stop it stops the httpd services and /etc/init.d/apache_start start starts the... (3 Replies)
New in Unix, I am adding a line "route add 57.14.y.y 57.14.x.x" every day after rebooting the system. Where can I add the line so during boot up (the system is re-started every day by design (???) the line is executed? (I tried the /etc/rc2.d/S90 but for some reason the line needs to be added... (2 Replies)
libapache2-mod-perl2-2.0.7::docs::api::ModPerl::RegistryUsereContributed Perl Dlibapache2-mod-perl2-2.0.7::docs::api::ModPerl::RegistryLoader(3pm)NAME
ModPerl::RegistryLoader - Compile ModPerl::RegistryCooker scripts at server startup
Synopsis
# in startup.pl
use ModPerl::RegistryLoader ();
use File::Spec ();
# explicit uri => filename mapping
my $rlbb = ModPerl::RegistryLoader->new(
package => 'ModPerl::RegistryBB',
debug => 1, # default 0
);
$rlbb->handler($uri, $filename);
###
# uri => filename mapping using a helper function
sub trans {
my $uri = shift;
$uri =~ s|^/registry/|cgi-bin/|;
return File::Spec->catfile(Apache2::ServerUtil::server_root, $uri);
}
my $rl = ModPerl::RegistryLoader->new(
package => 'ModPerl::Registry',
trans => &trans,
);
$rl->handler($uri);
###
$rlbb->handler($uri, $filename, $virtual_hostname);
Description
This modules allows compilation of scripts, running under packages derived from "ModPerl::RegistryCooker", at server startup. The script's
handler routine is compiled by the parent server, of which children get a copy and thus saves some memory by initially sharing the compiled
copy with the parent and saving the overhead of script's compilation on the first request in every httpd instance.
This module is of course useless for those running the "ModPerl::PerlRun" handler, because the scripts get recompiled on each request under
this handler.
Methods
new()
When creating a new "ModPerl::RegistryLoader" object, one has to specify which of the "ModPerl::RegistryCooker" derived modules to use.
For example if a script is going to run under "ModPerl::RegistryBB" the object is initialized as:
my $rlbb = ModPerl::RegistryLoader->new(
package => 'ModPerl::RegistryBB',
);
If the package is not specified "ModPerl::Registry" is assumed:
my $rlbb = ModPerl::RegistryLoader->new();
To turn the debugging on, set the debug attribute to a true value:
my $rlbb = ModPerl::RegistryLoader->new(
package => 'ModPerl::RegistryBB',
debug => 1,
);
Instead of specifying explicitly a filename for each uri passed to handler(), a special attribute trans can be set to a subroutine to
perform automatic remapping.
my $rlbb = ModPerl::RegistryLoader->new(
package => 'ModPerl::RegistryBB',
trans => &trans,
);
See the handler() item for an example of using the trans attribute.
handler()
$rl->handler($uri, [$filename, [$virtual_hostname]]);
The handler() method takes argument of "uri" and optionally of "filename" and of "virtual_hostname".
URI to filename translation normally doesn't happen until HTTP request time, so we're forced to roll our own translation. If the
filename is supplied it's used in translation.
If the filename is omitted and a "trans" subroutine was not set in new(), the loader will try using the "uri" relative to the
"ServerRoot" configuration directive. For example:
httpd.conf:
-----------
ServerRoot /usr/local/apache
Alias /registry/ /usr/local/apache/cgi-bin/
startup.pl:
-----------
use ModPerl::RegistryLoader ();
my $rl = ModPerl::RegistryLoader->new(
package => 'ModPerl::Registry',
);
# preload /usr/local/apache/cgi-bin/test.pl
$rl->handler(/registry/test.pl);
To make the loader smarter about the URI->filename translation, you may provide the "new()" method with a "trans()" function to
translate the uri to filename.
The following example will pre-load all files ending with .pl in the cgi-bin directory relative to "ServerRoot".
httpd.conf:
-----------
ServerRoot /usr/local/apache
Alias /registry/ /usr/local/apache/cgi-bin/
startup.pl:
-----------
{
# test the scripts pre-loading by using trans sub
use ModPerl::RegistryLoader ();
use File::Spec ();
use DirHandle ();
use strict;
my $dir = File::Spec->catdir(Apache2::ServerUtil::server_root,
"cgi-bin");
sub trans {
my $uri = shift;
$uri =~ s|^/registry/|cgi-bin/|;
return File::Spec->catfile(Apache2::ServerUtil::server_root,
$uri);
}
my $rl = ModPerl::RegistryLoader->new(
package => "ModPerl::Registry",
trans => &trans,
);
my $dh = DirHandle->new($dir) or die $!;
for my $file ($dh->read) {
next unless $file =~ /.pl$/;
$rl->handler("/registry/$file");
}
}
If $virtual_hostname argument is passed it'll be used in the creation of the package name the script will be compiled into for those
registry handlers that use namespace_from_uri() method. See also the notes on $ModPerl::RegistryCooker::NameWithVirtualHost in the
"ModPerl::RegistryCooker" documentation.
Also explained in the "ModPerl::RegistryLoader" documentation, this only has an effect at run time if
$ModPerl::RegistryCooker::NameWithVirtualHost is set to true, otherwise the $virtual_hostname argument is ignored.
Implementation Notes
"ModPerl::RegistryLoader" performs a very simple job, at run time it loads and sub-classes the module passed via the package attribute and
overrides some of its functions, to emulate the run-time environment. This allows one to preload the same script into different registry
environments.
Authors
The original "Apache2::RegistryLoader" implemented by Doug MacEachern.
Stas Bekman did the porting to the new registry framework based on "ModPerl::RegistryLoader".
SEE ALSO
"ModPerl::RegistryCooker", "ModPerl::Registry", "ModPerl::RegistryBB", "ModPerl::PerlRun", Apache(3), mod_perl(3)perl v5.14.2 2013-03-12 libapache2-mod-perl2-2.0.7::docs::api::ModPerl::RegistryLoader(3pm)