runtime16

## python27_on_centos65.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                runtime16
                / python27_on_centos65.md
            
            
              Created
              August 1, 2018 08:36
                — forked from dalegaspi/python27_on_centos65.md
            
              
                Installing Python 2.7 on CentOS 6.5
              
          
    Installing Python 2.7 on Centos 6.5

Centos 6.* comes with Python 2.6, but we can't just replace it with v2.7 because it's used by the OS internally (apparently) so you will need to install v2.7 (or 3.x, for that matter) along with it.  Fortunately, CentOS made this quite painless with their Software Collections Repository
sudo yum update # update yum
sudo yum install centos-release-scl # install SCL 
sudo yum install python27 # install Python 2.7

To use it, you essentially spawn another shell (or script) while enabling the newer version of Python:

  
## kerberos_setup.md

      
              2 files
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                runtime16
                / kerberos_setup.md
            
            
              Created
              March 12, 2019 09:20
                — forked from ashrithr/kerberos_setup.md
            
              
                Set up kerberos on Redhat/CentOS 7
              
          
    Installing Kerberos on Redhat 7

This installation is going to require 2 servers one acts as kerberos KDC server
and the other machine is going to be client. Lets assume the FQDN's are (here
cw.com is the domain name, make a note of the domain name here):

Kerberos KDC Server: kdc.cw.com
Kerberos Client: kclient.cw.com


Important: Make sure that both systems have their hostnames properly set and
both systems have the hostnames and IP addresses of both systems in


## build.gradle
apply plugin: 'groovy'
apply plugin: 'application'

startScripts.deleteAllActions()

jar {
    manifest {
        // Make sure the app's jar can be used with a simple -cp
        attributes 'Class-Path': configurations.runtime.collect { "${it.getName()}" }.join(' ')
    }
	apply plugin: 'groovy'
	apply plugin: 'application'

	startScripts.deleteAllActions()

	jar {
	manifest {
	// Make sure the app's jar can be used with a simple -cp
	attributes 'Class-Path': configurations.runtime.collect { "${it.getName()}" }.join(' ')
	}