Sponsored Content
Top Forums UNIX for Advanced & Expert Users Application Servers Installation and Users Post 302183452 by srikanths on Wednesday 9th of April 2008 05:06:53 AM
Old 04-09-2008
Application Servers Installation and Users

Hi,

When most of the server applications get installed, they create their own user. I believe this is to not use the "root" account. For example, Apache when installed creates a user called "apache". And the directories which it uses are all owned by this user. This seems to be the "professional" way of installing applications.

Is there any terminology for this kind of deployment? If I have to install a similar kind of server application, what are the steps that I need to take care? Has anyone written a blog post explaining these things? Or is there any standard guidelines published somewhere?

Thanks!
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

UNIX Database / Application Installation

Greetings, forgive me if this is listed in another thread somewhere, I am short on time. I am being interviewed for the position of UNIX Database and Job code installer for a consulting firm. I have never installed or worked on a native UNIX system. I have been running Linux (RH,SuSE,Slackware)... (3 Replies)
Discussion started by: OllieTech
3 Replies

2. UNIX for Dummies Questions & Answers

Application servers, proper usage

Is it common in the Unix/Linux environment to install compute intensive applications on a Server system and have the client machines download the executables into memory at runtime to run locally? This model seems taxing to the network, and as I understand, has been largely abandoned in the... (1 Reply)
Discussion started by: jonwillog
1 Replies

3. Shell Programming and Scripting

script to create users on many servers

Hi all, working on script to create a user acct on all our servers. for i in `cat $host_file`; do ssh $i /usr/bin/sudo /usr/bin/mkuser id='bpadm' gecos='NetBackup Admin' 2>&1 >> $log done error i get is: 3004-692 Error changing "id" to "bpadm" : Value is invalid. I have tried this in... (1 Reply)
Discussion started by: dnidiffer
1 Replies

4. AIX

Installation an application on AIX

Hi all I'm newbie In this forum, i have posted some topics about zip and unzip a file on AIX system. And i have some answers so that AIX can not work with zip file, and they tell me some files to zip and unzip my files on AIX such as: zip-2.3-3.aix4.3.ppc.rpm unzip-5.51-1.aix5.1.ppc.rpm... (2 Replies)
Discussion started by: leenguyen0101
2 Replies

5. Shell Programming and Scripting

Difference between development and Production unix servers for a application??

Hi all I am running a major script of my application in development for implementing code changes for process improvement in time. The script runs in production once in a month . It takes 8 hours 30 mins in Production server . what surprice me is , when I run the same script in development server... (9 Replies)
Discussion started by: sakthifire
9 Replies

6. Shell Programming and Scripting

Wants to create 3 users in 400 servers

I wants to create 3 users and set password for the users in 400 servers. I can run this script without error. If wants to set the password in the same command it is not working. Like that i have to create 3 users #!/usr/bin/ksh for server in `cat /tmp/servers` do echo "servername =... (5 Replies)
Discussion started by: G0kulakrishnan
5 Replies

7. Shell Programming and Scripting

I need to add 30 users to 50 servers

Hi Y'all, I need help adding 30 users to 50 servers. Is there a way to automate this? I'm using this command: sudo mkuser pgrp=srvadm gecos=Spears, Brittney auditclasses=ALL sugroups=system,security user01 But I'm doing it per user, per server...HOW CAN I MAKE THIS EASIER?... (7 Replies)
Discussion started by: jennie28n
7 Replies

8. Shell Programming and Scripting

Script to delete users in the servers

Hi Team, Hope you are doing good.I am new to scripting.I have a requirement of deleting around 10 users in 100 servers.It is very time consuming by logging into each servers and delete the user.Here I have redhat 6 ,Suse linux 10&11 environment servers. In one set of servers I have... (5 Replies)
Discussion started by: muraliinfy04
5 Replies

9. HP-UX

Sudden application crash in servers

Hi, This weekend there was a sudden application crash in the server. I did not know where to start to investigate the problem, so I first looked into the /var/adm/syslog/syslog.log, and this was what I found : Dec 17 00:38:02 L28bi01 sshd: error: accept: No buffer space available Dec 17... (9 Replies)
Discussion started by: anaigini45
9 Replies
Apache::DProf(3pm)					User Contributed Perl Documentation					Apache::DProf(3pm)

NAME
Apache::DProf - Hook Devel::DProf into mod_perl SYNOPSIS
#in httpd.conf PerlModule Apache::DProf DESCRIPTION
The Apache::DProf module will run a Devel::DProf profiler inside each child server and write the tmon.out file in the directory $ServerRoot/logs/dprof/$$ when the child is shutdown. Next time the parent server pulls in Apache::DProf (via soft or hard restart), the $ServerRoot/logs/dprof is cleaned out before new profiles are written for the new children. WHY
It is possible to profile code run under mod_perl with only the Devel::DProf module available on CPAN. You must have apache version 1.3b3 or higher. When the server is started, Devel::DProf installs an "END" block to write the tmon.out file, which will be run when the server is shutdown. Here's how to start and stop a server with the profiler enabled: % setenv PERL5OPT -d:DProf % httpd -X -d `pwd` & ... make some requests to the server here ... % kill `cat logs/httpd.pid` % unsetenv PERL5OPT % dprofpp There are downsides to this approach: - Setting and unsetting PERL5OPT is a pain. - Server startup code will be profiled as well, which we are not really concerned with, we're interested in runtime code, right? - It will not work unless the server is run in non-forking "-X" mode These limitations are due to the assumption by Devel::DProf that the code you are profiling is running under a standard Perl binary (the one you run from the command line). "Devel::Dprof" relies on the Perl "-d" switch for intialization of the Perl debugger, which happens inside "perl_parse()" function call. It also relies on Perl's special "END" subroutines for termination when it writes the raw profile to tmon.out. Under the standard command line Perl interpreter, these "END" blocks are run when the "perl_run()" function is called. Also, Devel::DProf will not profile any code if it is inside a forked process. Each time you run a Perl script from the command line, the "perl_parse()" and "perl_run()" functions are called, Devel::DProf works just fine this way. Under mod_perl, the "perl_parse()" and "perl_run()" functions are called only once, when the parent server is starting. Any "END" blocks encountered during server startup or outside of "Apache::Registry" scripts are suspended and run when the server is shutdown via apache's child exit callback hook. The parent server only runs Perl startup code, all request time code is run in the forked child processes. If you followed the previous paragraph, you should be able to see, Devel::DProf does not fit into the mod_perl model too well. The Apache::DProf module exists to make it fit without modifying the Devel::DProf module or Perl itself. The Apache::DProf module also requires apache version 1.3b3 or higher and "PerlChildInitHandler" enabled. It is configured simply by adding this line to your httpd.conf file: PerlModule Apache::DProf When the Apache::DProf module is pulled in by the parent server, it will push a "PerlChildInitHandler" via the Apache push_handlers method. When a child server is starting the "Apache::DProf::handler" subroutine will called. This handler will create a directory "dprof/$$" relative to ServerRoot where Devel::DProf will create it's tmon.out file. Then, the handler will initialize the Perl debugger and pull in Devel::DProf who will then install it's hooks into the debugger and start it's profile timer. The "END" subroutine installed by Devel::DProf will be run when the child server is shutdown and the $ServerRoot/dprof/$$/tmon.out file will be generated and ready for dprofpp. NOTE: $ServerRoot/logs/dprof/ will need to be writable by the user Apache is running as (i.e. nobody, apache, etc.). If you can not write to $ServerRoot as this user, set $ENV{APACHE_DPROF_PATH_ABSOLUTE} to an absolute path of a directory this user can. AUTHOR
Originally written by Doug MacEachern Currently maintained by Frank Wiles <frank@wiles.org> LICENSE
This module is distributed under the same terms as Perl itself. SEE ALSO
Devel::DProf(3), Apache::DB(3), mod_perl(3), Apache(3) perl v5.14.2 2006-09-13 Apache::DProf(3pm)
All times are GMT -4. The time now is 11:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy