The purpose of those comands are to find the newest file in a directory acvrdind to system date, and it has to be recursively found in each directory.
The problem is that i want to list in a long format every found file, but the commands i use produce unexpected results ,so the output lists in a... (5 Replies)
I have the following statement in script:
find ${LANDING_FILE_DIR}${BTIME_FILENAME_PATTERN2} -print | while read file; do
...
done
When there are no files located by the find comand it returns:
"find: bad status-- /home/rnitcher/test/....." to the command line
How do I get control in... (3 Replies)
I want the output of the find command to be printed and also the total files found by it. Can someone help in this.
Obviously $ find . -type f | wc -l will not output the files found but only the count. I want both. There can be millions and trillions of files so dont want the output of find... (3 Replies)
Hi,
i'm currently writing a script which tidys up old files. When using the find command I found that some files were not being listed
/export/home/ops***/test: ls -l processed
total 0
-rw-rw-r-- 1 ops*** ****** 0 Apr 20 11:53 test99
/export/home/ops***/test: ls -l
total 4... (9 Replies)
Trying to locate files less than xx days old, throughout all directories/subdirectories, but excluding certain types of directories and files.
The directories I want to search all contain the same characteristic (dbdef, pldef, ghdef, etc), and there are subdirectories within that I need to... (2 Replies)
Hi, I am new in scripting, and I am currently working on a script that will look for other files in a certain directory and exclude some file type.
this works fine:Find_File2Exclude=`find ${paths} -maxdepth 1 -type f \( ! -iname '*.out' ! -iname '*.auc' ! -iname '*.cps' ! -iname '*.log' ! -iname... (4 Replies)
Hello Forum,
I'm using the following command to find all inactive kernels installed on my RHEL server:
$ rpm -qa | grep '^kernel-' |grep -vE `uname -r`
but the result is in two lines:
kernel-3.10.0-1062.1.1.el7.x86_64
kernel-3.10.0-1062.el7.x86_64
Is there a one line command I can... (3 Replies)
Discussion started by: greavette
3 Replies
LEARN ABOUT DEBIAN
catalyst::manual::deployment
Catalyst::Manual::Deployment(3pm) User Contributed Perl Documentation Catalyst::Manual::Deployment(3pm)NAME
Catalyst::Manual::Deployment - Deploying Catalyst
DEPLOYMENT OPTIONS
Catalyst applications are most often deployed as a FastCGI or mod_perl application (with FastCGI being the recommended option). However, as
Catalyst is based on the PSGI specification, any web handler implementing that specification can be used to run Catalyst applications.
This documentation most thoroughly covers the normal and traditional deployment options, but will mention alternate methods of deployment,
and we welcome additional documentation from people deploying Catalyst in non-standard environments.
Deployment in a shared hosting environment
Almost all shared hosting environments involve deploying Catalyst as a FastCGI application on Apache. You will usually want to have a set
of libraries specific to your application installed on your shared host.
Full details of deploying Catalyst in a shared hosting environment are at Catalyst::Manual::Deployment::SharedHosting.
FastCGI
FastCGI is the most common Catalyst deployment option. It is documented generally in Catalyst::Manual::Deployment::FastCGI, and there are
specific instructions for using FastCGI with common web servers below:
Apache
Catalyst::Manual::Deployment::Apache::FastCGI
nginx
Catalyst::Manual::Deployment::nginx::FastCGI
lighttpd
Catalyst::Manual::Deployment::lighttpd::FastCGI
Microsoft IIS
Catalyst::Manual::Deployment::IIS::FastCGI
mod_perl
Traditionally a common deployment option for dedicated applications, mod_perl has some advantages and disadvantages over FastCGI. Use of
mod_perl is documented in Catalyst::Manual::Deployment::Apache::mod_perl.
Development Server
It is possible to deploy the Catalyst development server behind a reverse proxy. This may work well for small-scale applications which are
in an early development phase, but which you want to be able to show to people. See Catalyst::Manual::Deployment::DevelopmentServer.
PSGI
Catalyst can be deployed with any PSGI-compliant handler. See Catalyst::PSGI for more information; a list of possible deployment servers
are shown below:
Starman
Starman is a high-performance Perl server implementation, which is designed to be used directly (rather than behind a reverse proxy). It
includes HTTP/1.1 support, chunked requests and responses, keep-alive, and pipeline requests.
Starlet
Starlet is a standalone HTTP/1.0 server with keepaXXalive support which is suitable for running HTTP application servers behind a reverse
proxy.
Twiggy
Twiggy is a high-performance asynchronous web server. It can be used in conjunction with Catalyst, but there are a number of caveats which
mean that it is not suitable for most deployments.
Chef
<LChef|http://www.opscode.com/chef/> is an open-source systems integration framework built specifically for automating cloud computing
deployments. A Cookbooks demonstrating how to deploy a Catalyst application using Chef is available at
<http://community.opscode.com/cookbooks/catalyst> and http://github.com/melezhik/cookbooks/wiki/Catalyst-cookbook-intro
<http://github.com/melezhik/cookbooks/wiki/Catalyst-cookbook-intro>.
AUTHORS
Catalyst Contributors, see Catalyst.pm
COPYRIGHT
This library is free software. You can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.14.2 2012-01-20 Catalyst::Manual::Deployment(3pm)