Tag Info

Hot answers tagged


Try this: 1) Create a file /usr/sbin/policy-rc.d with following content: #!/bin/sh exit 101 2) Make it executable: chmod +x /usr/sbin/policy-rc.d After this, all packages will be installed but the services will not start. Once you are done, you can remove the file: rm -f /usr/sbin/policy-rc.d


Lots of options: Move the closed source content out of /var/www Change the permissions on that content such that the apache user cannot read it Iptables to stop port 80/443 traffic Pass a runlevel environment variable to apt-get: sudo RUNLEVEL=1 apt-get install apache2


Update: As of March 2015 truncate is no longer available in Homebrew as a standalone formula. As truncate is part of GNU Coreutils you should install it on OS X with the following command: > brew install coreutils After installation truncate will be available under the name gtruncate. Note that all programs from Coreutils will be available with the ...


There is no such mechanism. This is because it is the way DNS and its caching mechanisms work. This is usually handled before the migration by setting the TTL for the A record to the minimum value possible, so that DNS servers keep the IP address cached for the least possible time. However, only in rare cases you can set the TTL to zero, which would ...


Below is link to a great article that will help determine the right settings for the mpm_prefork_module. The idea is to run a script that will show you how much memory is consumed by each Apache process, then using that information to configure the settings. http://cloudinservice.com/tune-apache-performance-using-mpm-prefork-module/ Script: ...


This is because you have alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases The hash: means, that you must have a database file containing the hashes, as described in Postfix lookup table types: An indexed file type based on hashing. This is available only on systems with support for Berkeley DB databases. Public database files are ...


You can enable IP forwarding and then do forwarding of the traffic at the IP level (see http://www.debuntu.org/how-to-redirecting-network-traffic-to-a-new-ip-using-iptables/ for an example). I believe this has a benefit over proxying because you maintain the IP address of who is connecting to the website and that's logged properly.


In your example the variables ($HOME, $USER, ...) are interpreted before the sudo command is executed. This, in contrast, should work as you'd expect it: sudo -u johnny -i env | grep HOME

Only top voted, non community-wiki answers of a minimum length are eligible