05-06-2010
Quote:
Originally Posted by
pinga123
As i m new to linux can u please explain how would i avoid this?
Under UNIX all ports <1024 are "privileged" ports.
As a non-root user you cannot use ports < 1024. To my knowledge it is best to use "jsvc" (daemon mode). Try this scenario:
Installing Tomcat with commons-daemon (jsvc) - waelchatila.com
Another possibility is to put Tomcat behind an Apache HTTP-server and connect to Tomcat through the ajp13 protocol.
Regards, Qube
8 More Discussions You Might Find Interesting
1. SCO
I need to install Apache TOmcat 4.01 on SCO Openserver 5.07 rather than using the default 4.1.29 version which comes with the original release of 5.07
anyone got any ideas hw to go about this, really struggling having downloaded the source and binariys and getting nowhere fast (0 Replies)
Discussion started by: ccarcher
0 Replies
2. UNIX for Dummies Questions & Answers
Hi, can anyone explain the difference in terms of application server, web server concepts?
Thanks
james (0 Replies)
Discussion started by: james94539
0 Replies
3. UNIX for Advanced & Expert Users
Hi,
I have a machine with Unixware 7.1.3 and Apache 2 and Tomcat 4.0.3 it's works, but in the archive log from mod_jk.log
ajp13_process_callback - write failed
: Error
ajp13_process_callback - write failed
: Error
ajp13_process_callback - write failed
: Error... (1 Reply)
Discussion started by: By_Jam
1 Replies
4. AIX
Hello,
Where can i find the information about the compatibility versions of tomcat with AIX? for example, AIX 5.2 supported tomcat versions?? (1 Reply)
Discussion started by: balareddy
1 Replies
5. Web Development
Hi,
I am facing some problem with Apache to Tomcat forwarding. I have Tomcat (6.0.18) behind Apache (2.2). I want to use ‘https' for receiving request from the client. This request, when forwarded by Apache to Tomcat, will use ‘http'. My application's name is ‘abc', which is deployed in... (1 Reply)
Discussion started by: Technext
1 Replies
6. Red Hat
Evening,
I'm posting for help here, because I'll be honest I've reached the end of my tether, hopefully someone can give me some assistance and help me maintain a level of sanity...
I maintain a number of webservers on RHEL 5 64Bit (Red Hat Enterprise Linux Server release 5.3 (Tikanga)), the... (2 Replies)
Discussion started by: cpickering
2 Replies
7. Red Hat
Good evening, i've got a problem. I fail to enter "Manager App" in Apache Tomcat/9.0.0.M9 on server, it says "403 Access Denied». for example, server address is 192.168.1.4, when I type 'localhost ' in the browser and press "Manager App", then everything is ok. but if I enter 192.168.1.4 and press... (0 Replies)
Discussion started by: v.k.l.chr.by
0 Replies
8. UNIX for Advanced & Expert Users
Hi,
I have been assigned a task to build a server with these requirements :
> has multiple tomcats running under the same apache.
> tomcat & jdk has to be binded with apache.
> latest openssl with all necesarry "mod" to bind with apache & tomcat.
I am fairly new to... (1 Reply)
Discussion started by: anaigini45
1 Replies
LEARN ABOUT CENTOS
shell-quote
SHELL-QUOTE(1) User Contributed Perl Documentation SHELL-QUOTE(1)
NAME
shell-quote - quote arguments for safe use, unmodified in a shell command
SYNOPSIS
shell-quote [switch]... arg...
DESCRIPTION
shell-quote lets you pass arbitrary strings through the shell so that they won't be changed by the shell. This lets you process commands
or files with embedded white space or shell globbing characters safely. Here are a few examples.
EXAMPLES
ssh preserving args
When running a remote command with ssh, ssh doesn't preserve the separate arguments it receives. It just joins them with spaces and
passes them to "$SHELL -c". This doesn't work as intended:
ssh host touch 'hi there' # fails
It creates 2 files, hi and there. Instead, do this:
cmd=`shell-quote touch 'hi there'`
ssh host "$cmd"
This gives you just 1 file, hi there.
process find output
It's not ordinarily possible to process an arbitrary list of files output by find with a shell script. Anything you put in $IFS to
split up the output could legitimately be in a file's name. Here's how you can do it using shell-quote:
eval set -- `find -type f -print0 | xargs -0 shell-quote --`
debug shell scripts
shell-quote is better than echo for debugging shell scripts.
debug() {
[ -z "$debug" ] || shell-quote "debug:" "$@"
}
With echo you can't tell the difference between "debug 'foo bar'" and "debug foo bar", but with shell-quote you can.
save a command for later
shell-quote can be used to build up a shell command to run later. Say you want the user to be able to give you switches for a command
you're going to run. If you don't want the switches to be re-evaluated by the shell (which is usually a good idea, else there are
things the user can't pass through), you can do something like this:
user_switches=
while [ $# != 0 ]
do
case x$1 in
x--pass-through)
[ $# -gt 1 ] || die "need an argument for $1"
user_switches="$user_switches "`shell-quote -- "$2"`
shift;;
# process other switches
esac
shift
done
# later
eval "shell-quote some-command $user_switches my args"
OPTIONS
--debug
Turn debugging on.
--help
Show the usage message and die.
--version
Show the version number and exit.
AVAILABILITY
The code is licensed under the GNU GPL. Check http://www.argon.org/~roderick/ or CPAN for updated versions.
AUTHOR
Roderick Schertler <roderick@argon.org>
perl v5.16.3 2010-06-11 SHELL-QUOTE(1)