CentOS

Sorry, I meant /etc/httpd/conf.d/vhost2.example.com.conf. I doubt I am going to get any help on this problem beyond being told to RTFM, but I thought it was worth a try.

I am trying to run /srv/vhost2.example.com/scripts/hello_world.py at http://vhost2.example.com/webapp/hello_world.py, but I am getting the 404 error. I have this in /etc/httpd/conf.d/vhost2.example.com.conf. <Directory /srv/vhost2.example.com/www> Require all granted </Directory> <Directory /srv/vho...

I am trying to run /srv/vhost2.example.com/scripts/hello_world.py at http://vhost2.example.com/webapp/hello_world.py, but I am getting the 404 error. I have this in /etc/httpd/conf.d/vhost2.example.com.conf <Directory /srv/vhost2.example.com/www> Require all granted </Directory> <Directory /srv/vho...

I am trying to run /srv/vhost2.example.com/scripts/hello_world.py at http://vhost2.example.com/webapp/hello_world.py, but I am getting the 404 error. I have this in /etc/httpd/conf.d/vhost2.example.com. <Directory /srv/vhost2.example.com/www> Require all granted </Directory> <Directory /srv/vhost2.e...

I am following an example in a book and I am trying to display sar information from 9:00 AM to 5:00 PM on January 15. I entered sadf -s 9:00:00 -e 17:00:00 /var/log/sa/sa15 like it says in the book but the sadf just displays "Usage: sadf" and the options for sadf. The /var/log/sa/sa15 file exists on...

I have 2 virtual interfaces, virbr0 and virbr1 on the 192.168.122.0/24 and 192.168.100.0/24 subents respectively. I configured iptables to allow hosts on both subnets to communicate with eachother and with the 192.168.1.0/24 which my physical host is part of so the VMs can access the Internet. Whene...

192.168.100.100 on virbr1 cannot ping my Internet gateway at 192.168.1.1 but 192.168.122.50 can. [code] # Firewall configuration written by system-config-firewall # Manual customization of this file is not recommended. *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -...

I spoke too soon. Once I rebooted my physical machine my VM at 192.168.122.50 could not ping 192.168.100.100. I discovered that I also needed [code] -A FORWARD -i virbr0 -j ACCEPT [/code] in iptables. The strange thing is that when I rebooted my physical machine again after adding the virbr0 forward...

Someone on linuxquestions.org answered my question. The command I entered to solve my problem is

[code]
iptables -I FORWARD 1 -s 192.168.122.0/24 -d 192.168.100.0/24 -j ACCEPT
[/code]

I have 2 virtual networks set up with Virtual Machine Manager as virbr0 and virbr1 that are the 192.168.122.0/24 and 192.168.100.0/24 subnets, respectively. My physical eth1 interface is 192.168.1.100. I have net.ipv4.ip_forward = 1 in /etc/sysctl.conf and I entered sysctl -p. I can ping my VMs at 1...