Tag Info

New answers tagged

0

Squid is a HTTP proxy (usually operated as a Forward Proxy). It does support FTP also. It does not support POP3 and SMTP. You should look at something like HAProxy if you want a Reverse Proxy for protocols other than HTTP.


1

The first step is to find where the configuration file is located. When you run exim -bV it will print out the configuration file it is using. You can also see the current (and possibly the default) for that setting by running exim -bP received_header_text. You must remember that the configuration file is likely strictly controlled by the DirectAdmin web ...


1

From the nginx documentation for ssl_protocols directive: The TLSv1.1 and TLSv1.2 parameters are supported starting from versions 1.1.13 and 1.0.12, so when the OpenSSL version 1.0.1 or higher is used on older nginx versions, these protocols work, but cannot be disabled.` On newer versions this can be verified by using the openssl commands as follows: ...


0

In Tomcat 5.5 you should use undocumented parameter protocols="TLSv1" to restrict use of excatly this protocol version.


2

Don't do it this way. Instead, use a config management system (Ansible, Saltstack, etc.). Keep those files in version control and use that the CM to deploy config changes to your servers. Doing things this way is highly beneficial in many ways: you have a full, offline backup of your server configurations, you can easily apply this configuration to ...


0

I ran into this same issue today. I was able to work around it by splitting stdout manually like this: until: sources_list.stdout.split()|length <= 5 I think this is a bug, since stdout_lines and stdout.split() are supposed to give the same result. I've filed a bug report here: https://github.com/ansible/ansible/issues/10334


0

It appears some of the other solutions won't work if the configuration files of the package are managed with ucf. In this case you can useĀ : UCF_FORCE_CONFFMISS=1 apt-get --reinstall install [pkgname]


1

I solved such issue caused by selinux. NMB reported protocol not available on port 137. SMB reported the same on port 139. I switched Selinux off on /etc/selinux/config and Samba started working fine. BTW this selinux is a great tool for peopleĀ“s patience examination ;-)


0

I've solved the problem. The problem : ServerLimit and MaxClients values higher than 256 do not take effect, they stay in 256. Each time I change things in httpd.conf and then I restart apache using the command : # httpd restart Nothing really changed. The solution : Be sure that httpd completely stops then start again. The command that worked for me ...


0

Generally speaking, even untagged ports need to be assigned a NATIVE VLAN id AND only if this is different from the default id of 1. This is to help the switch understand how to forward packets. If you do not provide a vlan and it is bridged, it's considered a routed interface. You should not generally specify subinterfaces (ie tags) on interfaces unless you ...


1

You should be able to use what you have in that config file for the launchconfiguration namespace, but you need the single quotes around the namespace and value like you have in the first 2 that are working. - namespace: 'aws:autoscaling:launchconfiguration' option_name: InstanceType value: 't2.micro' - namespace: ...


1

That's fine but why not using the apache functionality to log failed logins ? Add these lines to your Apache Config (i.e:/etc/apache2/conf.d/phpmyadmin.conf) in the according VirtualHost Section: LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %{userID}n %{userStatus}n" pma_combined CustomLog ...


0

Today's best practice is to use VPC, so, then, you will know the exact CIDR for your ELB. Then, you can add something like this to your Nginx configuration file: real_ip_header X-Forwarded-For; set_real_ip_from 10.0.0.0/8;


1

The answer your after is routing tables. At the moment you have two interfaces sharing the same routing table with two default routes (with different metric), but what you want is a completely separated second routing table for your second interface. Either that or doing source NAT to all the traffic coming in from outside, which is a very bad idea anyway. ...


5

Short Answer With modern processor, with fast C6 (core/module power gating) capabilities, the difference in power consumption between the two power profiles is negligible. On the other hand, due to how different CPUs behave in power saving mode, you can lose considerable performance using the "balanced" profile. So I advise you to use the "high performance" ...


-1

You have to play with apache conf , mpm conf . This blog resume how to do the math : https://rudd-o.com/linux-and-free-software/tuning-an-apache-server-in-5-minutes


0

The usual way to do this on any UNIX system is to use the appropriate dump/restore software. For a Centos this is xfsdump/zfsrestore for dumping/restoring XFS filesystems, dump for ext2/ext3/ext4 filesystems and restore from the dump package to restore previously taken dump. You should also recreate the fdisk/gpt/LVM/whatever layout, and format the ...


1

From a package-management standpoint, you could dump all installed packages into a file with rpm -qa > /root/packages.txt Transfer the file to the "new" machines and run: yum -y install $(cat packages.txt) Then you can just copy over your configuration files & code.


0

this may help.. https://github.com/supermasita/ufe/wiki/Installing-FFMPEG-on-CentOS-with-ATRPMS-repo rpm --import http://packages.atrpms.net/RPM-GPG-KEY.atrpms vim /etc/yum.repos.d/atrpms.repo


0

You can have a user account that requires a password for SUDO access and provide that value at run-time via the --ask-sudo-pass flag (-K) for ansible-playbook ansible-playbook -i inv/production -K playbook.yml see http://docs.ansible.com/playbooks_intro.html for more details


1

There are a lot of things it could be, so I almost commented rather than answered. I'd look at disk speed and php config. Specifically, the memory limit should be larger than your max upload size in your php config. This link is drupal-specific but may help.


1

I have found that, as of nginx 1.6.2 at least, the working syntax for me for the location block is: location ~ \.php$ { try_files $uri = 404; fastcgi_pass php fastcgi_index index.php; include fastcgi.conf; } that is: one should not specify the http:// protocol before referencing the php backend. The http://php syntax is to be used with the ...


1

First off I want to thank @MichaelHampton for his answer. It was spot on, and I would have never spotted the typo with the '$' ('OPTIONS=...' instead of '$OPTIONS=...'). Now, the problem was with the command line options. In the docker documentation the argument for changing the storage driver is given as: --storage btrfs Keep in mind that this is the ...


2

OK, I made some tweak on your playbook, and here is the revised version --- - hosts: 127.0.0.1 connection: local vars: my_users: belminf: "belminf" bob: "tmessins" tasks: - name: Retrieving all keys from GitHub shell: /usr/bin/curl https://github.com/{{ item.value }}.keys 2> /dev/null register: ssh_keys ...


1

The most elegant answer is to put thatonespecial.log in a separate directory so it wouldn't be able to match the wildcard. If that won't work, then you can use globs to narrow down your wildcard. It's messy, but if you absolutely can't move the file location then it's probably your only real option. Something like this: /var/log/mylogs/[!t][!h]*.log ...


1

You have an error in your /srv/docker/docker.conf file. $OPTIONS="--graph /srv/docker --storage btrfs" The specification of a variable should not start with a $; the $ should only be used when using the variable later. Change it to: OPTIONS="--graph /srv/docker --storage btrfs"



Top 50 recent answers are included