Sponsored Content
Full Discussion: Run tomcat at startup
Top Forums UNIX for Dummies Questions & Answers Run tomcat at startup Post 38021 by cbkihong on Thursday 3rd of July 2003 11:18:20 PM
Old 07-04-2003
I suggest you read the documentation of your distro, because the way to do it is a bit different in different Linux distros.

Search for sections on RC scripts, runlevels, system startup or the like in the docs.
 

10 More Discussions You Might Find Interesting

1. Linux

Run a script during reboot/startup

Hi all, i have a script in /etc/init.d directory. -rwxr-xr-x 1 root root 26 Mar 28 16:00 myscript I need it to run when my linux reboots/startup. However is it not being executed. Do i need to put in in the rc.local directory? (1 Reply)
Discussion started by: new2ss
1 Replies

2. AIX

run script at startup

I am using AIX 5.3 in P6 machine. I have a script "test.sh", when i run it manually it runs properly. I want to run the script automatically when system starts. I kept the script in /etc/rc.d/init.d and also in /etc/rc.d/rc2.d but it is not working. Do i have to write it in inittab instead of... (1 Reply)
Discussion started by: pchangba1
1 Replies

3. Shell Programming and Scripting

Need to run script at startup.

Hi guys , I Need to run a specific command (pinging a particular machine). Which need to run every time i reboot the server till the time it shut down. What is the preferred way of doing this. Will it impact my system performance. My Operating system is as below. # lsb_release -a... (3 Replies)
Discussion started by: pinga123
3 Replies

4. UNIX for Dummies Questions & Answers

run a script at startup

hi, i am using rhel 5, and i wanna run a script as soon as the operating system open. How can i do this ? ( i was reading rc.d files but i could not understand exactly what are the run levels and where should i put the my shell script. my script will be : #!/bin/ksh iptables -I INPUT... (1 Reply)
Discussion started by: futi
1 Replies

5. Shell Programming and Scripting

run a shellscript in background after startup

hi. i need to start a shellscript AFTER full system startup the script will then run permanently in a loop checking the server every minute and in case of major hangs it just reboots the machine. i put it into /etc/rc.local file like this: #!/bin/sh -e # # rc.local # # This script is... (4 Replies)
Discussion started by: scarfake
4 Replies

6. SuSE

Unable to Run a script at startup in suse

Hi I have a script myscript.sh that needs to be run whenever the server boots. The script is actually logging Syslog-ng messages to sql server. I need to lauch it at startup I have copied the script in etc/init.d i have also added the link ln -s /etc/init.d/syslog-ng-mssql-pipe.sh... (5 Replies)
Discussion started by: SystemEng
5 Replies

7. AIX

Run script with different user at the startup ..

Run script with different user at the startup .. I have created this user appuser And I have a script should to be up thru the startup by this user appuser I have defined the path of the script /user/appstart.sh in /etc/rc But at the startup starting will be by root , I’d like to keep... (6 Replies)
Discussion started by: Mr.AIX
6 Replies

8. Shell Programming and Scripting

Run application at startup

We have a Windows Service written in C# ported over to linux using Mono Develop... The code is working 100% when we run a script file which runs the exe... but we want the application to run at startup.... The application gathers info of the computer eg. Hard Disk Space etc... And compress it into... (1 Reply)
Discussion started by: yodzaan
1 Replies

9. Shell Programming and Scripting

Automatic shutdown and startup of Tomcat in Solaris

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)
Discussion started by: Amit.saini333
1 Replies

10. Shell Programming and Scripting

Apache tomcat startup script not booting at startup.

I copied the script from an AskUbuntu post - #!/bin/bash ### BEGIN INIT INFO # Provides: tomcat7 # Required-Start: $network # Required-Stop: $network # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: Start/Stop Tomcat server ### END INIT INFO ... (14 Replies)
Discussion started by: Hijanoqu
14 Replies
pki_tomcat_selinux(8)					     SELinux Policy pki_tomcat					     pki_tomcat_selinux(8)

NAME
pki_tomcat_selinux - Security Enhanced Linux Policy for the pki_tomcat processes DESCRIPTION
Security-Enhanced Linux secures the pki_tomcat processes via flexible mandatory access control. The pki_tomcat processes execute with the pki_tomcat_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep pki_tomcat_t ENTRYPOINTS
The pki_tomcat_t SELinux type can be entered via the pki_tomcat_exec_t file type. The default entrypoint paths for the pki_tomcat_t domain are the following: /usr/bin/pkidaemon PROCESS TYPES
SELinux defines process types (domains) for each process running on the system You can see the context of a process using the -Z option to ps Policy governs the access confined processes have to files. SELinux pki_tomcat policy is very flexible allowing users to setup their pki_tomcat processes in as secure a method as possible. The following process types are defined for pki_tomcat: pki_tomcat_t, pki_tomcat_script_t Note: semanage permissive -a pki_tomcat_t can be used to make the process type pki_tomcat_t permissive. SELinux does not deny access to permissive process types, but the AVC (SELinux denials) messages are still generated. BOOLEANS
SELinux policy is customizable based on least access required. pki_tomcat policy is extremely flexible and has several booleans that allow you to manipulate the policy and run pki_tomcat with the tightest access possible. If you want to allow all daemons to write corefiles to /, you must turn on the daemons_dump_core boolean. Disabled by default. setsebool -P daemons_dump_core 1 If you want to enable cluster mode for daemons, you must turn on the daemons_enable_cluster_mode boolean. Enabled by default. setsebool -P daemons_enable_cluster_mode 1 If you want to allow all daemons to use tcp wrappers, you must turn on the daemons_use_tcp_wrapper boolean. Disabled by default. setsebool -P daemons_use_tcp_wrapper 1 If you want to allow all daemons the ability to read/write terminals, you must turn on the daemons_use_tty boolean. Disabled by default. setsebool -P daemons_use_tty 1 If you want to deny any process from ptracing or debugging any other processes, you must turn on the deny_ptrace boolean. Enabled by default. setsebool -P deny_ptrace 1 If you want to allow all domains to use other domains file descriptors, you must turn on the domain_fd_use boolean. Enabled by default. setsebool -P domain_fd_use 1 If you want to allow all domains to have the kernel load modules, you must turn on the domain_kernel_load_modules boolean. Disabled by default. setsebool -P domain_kernel_load_modules 1 If you want to allow all domains to execute in fips_mode, you must turn on the fips_mode boolean. Enabled by default. setsebool -P fips_mode 1 If you want to enable reading of urandom for all domains, you must turn on the global_ssp boolean. Disabled by default. setsebool -P global_ssp 1 If you want to allow confined applications to use nscd shared memory, you must turn on the nscd_use_shm boolean. Enabled by default. setsebool -P nscd_use_shm 1 MANAGED FILES
The SELinux process type pki_tomcat_t can manage files labeled with the following file types. The paths listed are the default paths for these file types. Note the processes UID still need to have DAC permissions. cluster_conf_t /etc/cluster(/.*)? cluster_var_lib_t /var/lib/pcsd(/.*)? /var/lib/cluster(/.*)? /var/lib/openais(/.*)? /var/lib/pengine(/.*)? /var/lib/corosync(/.*)? /usr/lib/heartbeat(/.*)? /var/lib/heartbeat(/.*)? /var/lib/pacemaker(/.*)? cluster_var_run_t /var/run/crm(/.*)? /var/run/cman_.* /var/run/rsctmp(/.*)? /var/run/aisexec.* /var/run/heartbeat(/.*)? /var/run/cpglockd.pid /var/run/corosync.pid /var/run/rgmanager.pid /var/run/cluster/rgmanager.sk dirsrv_var_lib_t /var/lib/dirsrv(/.*)? pki_common_t /opt/nfast(/.*)? pki_tomcat_cache_t pki_tomcat_cert_t /var/lib/pki-ca/alias(/.*)? /var/lib/pki-kra/alias(/.*)? /var/lib/pki-tks/alias(/.*)? /var/lib/pki-ocsp/alias(/.*)? /etc/pki/pki-tomcat/alias(/.*)? /var/lib/ipa/pki-ca/publish(/.*)? pki_tomcat_etc_rw_t /etc/pki-ca(/.*)? /etc/pki-kra(/.*)? /etc/pki-tks(/.*)? /etc/pki-ocsp(/.*)? /etc/pki/pki-tomcat(/.*)? /etc/sysconfig/pki/tomcat(/.*)? pki_tomcat_lock_t /var/lock/subsys/pkidaemon pki_tomcat_log_t /var/log/pki-ca(/.*)? /var/log/pki-kra(/.*)? /var/log/pki-tks(/.*)? /var/log/pki-ocsp(/.*)? /var/log/pki/pki-tomcat(/.*)? pki_tomcat_tmp_t pki_tomcat_var_lib_t /var/lib/pki-ca(/.*)? /var/lib/pki-kra(/.*)? /var/lib/pki-tks(/.*)? /var/lib/pki-ocsp(/.*)? /var/lib/pki/pki-tomcat(/.*)? pki_tomcat_var_run_t /var/run/pki-ca.pid /var/run/pki-kra.pid /var/run/pki-tks.pid /var/run/pki-ocsp.pid /var/run/pki/tomcat(/.*)? root_t / /initrd user_tmp_t /var/run/user(/.*)? /tmp/hsperfdata_root /var/tmp/hsperfdata_root /tmp/gconfd-.* FILE CONTEXTS
SELinux requires files to have an extended attribute to define the file type. You can see the context of a file using the -Z option to ls Policy governs the access confined processes have to these files. SELinux pki_tomcat policy is very flexible allowing users to setup their pki_tomcat processes in as secure a method as possible. EQUIVALENCE DIRECTORIES pki_tomcat policy stores data with multiple different file context types under the /var/lib/pki-ca directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv dirctory you would execute the following command: semanage fcontext -a -e /var/lib/pki-ca /srv/pki-ca restorecon -R -v /srv/pki-ca pki_tomcat policy stores data with multiple different file context types under the /var/lib/pki-kra directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv dirctory you would execute the following command: semanage fcontext -a -e /var/lib/pki-kra /srv/pki-kra restorecon -R -v /srv/pki-kra pki_tomcat policy stores data with multiple different file context types under the /var/lib/pki-ocsp directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv dirctory you would execute the following command: semanage fcontext -a -e /var/lib/pki-ocsp /srv/pki-ocsp restorecon -R -v /srv/pki-ocsp pki_tomcat policy stores data with multiple different file context types under the /var/lib/pki-tks directory. If you would like to store the data in a different directory you can use the semanage command to create an equivalence mapping. If you wanted to store this data under the /srv dirctory you would execute the following command: semanage fcontext -a -e /var/lib/pki-tks /srv/pki-tks restorecon -R -v /srv/pki-tks STANDARD FILE CONTEXT SELinux defines the file context types for the pki_tomcat, if you wanted to store files with these types in a diffent paths, you need to execute the semanage command to sepecify alternate labeling and then use restorecon to put the labels on disk. semanage fcontext -a -t pki_tomcat_cache_t '/srv/pki_tomcat/content(/.*)?' restorecon -R -v /srv/mypki_tomcat_content Note: SELinux often uses regular expressions to specify labels that match multiple files. The following file types are defined for pki_tomcat: pki_tomcat_cache_t - Set files with the pki_tomcat_cache_t type, if you want to store the files under the /var/cache directory. pki_tomcat_cert_t - Set files with the pki_tomcat_cert_t type, if you want to treat the files as pki tomcat certificate data. Paths: /var/lib/pki-ca/alias(/.*)?, /var/lib/pki-kra/alias(/.*)?, /var/lib/pki-tks/alias(/.*)?, /var/lib/pki-ocsp/alias(/.*)?, /etc/pki/pki- tomcat/alias(/.*)?, /var/lib/ipa/pki-ca/publish(/.*)? pki_tomcat_etc_rw_t - Set files with the pki_tomcat_etc_rw_t type, if you want to treat the files as pki tomcat etc read/write content. Paths: /etc/pki-ca(/.*)?, /etc/pki-kra(/.*)?, /etc/pki-tks(/.*)?, /etc/pki-ocsp(/.*)?, /etc/pki/pki-tomcat(/.*)?, /etc/sysconfig/pki/tom- cat(/.*)? pki_tomcat_exec_t - Set files with the pki_tomcat_exec_t type, if you want to transition an executable to the pki_tomcat_t domain. pki_tomcat_lock_t - Set files with the pki_tomcat_lock_t type, if you want to treat the files as pki tomcat lock data, stored under the /var/lock directory pki_tomcat_log_t - Set files with the pki_tomcat_log_t type, if you want to treat the data as pki tomcat log data, usually stored under the /var/log direc- tory. Paths: /var/log/pki-ca(/.*)?, /var/log/pki-kra(/.*)?, /var/log/pki-tks(/.*)?, /var/log/pki-ocsp(/.*)?, /var/log/pki/pki-tomcat(/.*)? pki_tomcat_tmp_t - Set files with the pki_tomcat_tmp_t type, if you want to store pki tomcat temporary files in the /tmp directories. pki_tomcat_unit_file_t - Set files with the pki_tomcat_unit_file_t type, if you want to treat the files as pki tomcat unit content. pki_tomcat_var_lib_t - Set files with the pki_tomcat_var_lib_t type, if you want to store the pki tomcat files under the /var/lib directory. Paths: /var/lib/pki-ca(/.*)?, /var/lib/pki-kra(/.*)?, /var/lib/pki-tks(/.*)?, /var/lib/pki-ocsp(/.*)?, /var/lib/pki/pki-tomcat(/.*)? pki_tomcat_var_run_t - Set files with the pki_tomcat_var_run_t type, if you want to store the pki tomcat files under the /run or /var/run directory. Paths: /var/run/pki-ca.pid, /var/run/pki-kra.pid, /var/run/pki-tks.pid, /var/run/pki-ocsp.pid, /var/run/pki/tomcat(/.*)? Note: File context can be temporarily modified with the chcon command. If you want to permanently change the file context you need to use the semanage fcontext command. This will modify the SELinux labeling database. You will need to use restorecon to apply the labels. COMMANDS
semanage fcontext can also be used to manipulate default file context mappings. semanage permissive can also be used to manipulate whether or not a process type is permissive. semanage module can also be used to enable/disable/install/remove policy modules. semanage boolean can also be used to manipulate the booleans system-config-selinux is a GUI tool available to customize SELinux policy settings. AUTHOR
This manual page was auto-generated using sepolicy manpage . SEE ALSO
selinux(8), pki_tomcat(8), semanage(8), restorecon(8), chcon(1), sepolicy(8) , setsebool(8), pki_tomcat_script_selinux(8), pki_tom- cat_script_selinux(8) pki_tomcat 14-06-10 pki_tomcat_selinux(8)
All times are GMT -4. The time now is 02:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy