Wolfgang,

I`ve also had this problem in the past on a couple of occasions after
previous Roo upgrades. There is a ticket in bugzilla for this already
(although it may have been closed as it was believed to have been fixed):

https://bugs.honeynet.org/show_bug.cgi?id=371

By the way, if you are interested, you can simply used "yum update" to
update Roo, rather than manually wgetting individual RPMs. This makes daily
patch management a little easier.

Thanks,

David

David Watson
UK Honeynet Project
www.ukhoneynet.org
david (at) honeynet.org (dot) uk [email concealed]

-----Original Message-----
From: wolfgang.richter (at) gmail (dot) com [email concealed] [mailto:wolfgang.richter (at) gmail (dot) com [email concealed]]
Sent: 08 January 2006 10:09
To: honeypots (at) securityfocus (dot) com [email concealed]
Subject: Applied RPM Update to Walleye

Not sure if the RPM wasn't set correctly, but when I applied the Walleye
update from
http://www.honeynet.org/tools/cdrom/roo/repo/walleye-1.1-22.i386.rpm , I got
new errors complaining that directories were not writable. I fixed this by
setting all the directories in /var/www/html/walleye/ to be owned by the
user and group apache - they had been set to root. Perhaps I did something
wrong, but I just wanted to put it out there.

My steps:

wget http://www.honeynet.org/tools/cdrom/roo/repo/walleye-1.1-22.i386.rpm

rpm -U walleye-1.1-22.i386.rpm

cd /var/www/html/

chown -R apache walleye

chgrp -R apache walleye

All of the other files within the walleye directory were already owned by
user and group apache, only the directories were set to root. Were they
supposed to be?

--
Wolfgang Richter

[ reply ]