Honeypots mailing list archives
RE: Applied RPM Update to Walleye
From: "David Watson" <david () honeynet org uk>
Date: Mon, 9 Jan 2006 11:57:52 -0000
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 () honeynet org uk -----Original Message----- From: wolfgang.richter () gmail com [mailto:wolfgang.richter () gmail com] Sent: 08 January 2006 10:09 To: honeypots () securityfocus com 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
Current thread:
- Applied RPM Update to Walleye wolfgang . richter (Jan 08)
- RE: Applied RPM Update to Walleye David Watson (Jan 09)
- <Possible follow-ups>
- Re: RE: Applied RPM Update to Walleye wolfgang . richter (Jan 11)