Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#17294 - [privoxy] can't access files from /var/log/privoxy/

Attached to Project: Arch Linux
Opened by kat bessie (basementcat) - Thursday, 26 November 2009, 20:53 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 28 November 2009, 00:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After rebooting the computer, one cannot start privoxy properly.

Error message:
touch: cannot touch `/var/log/privoxy/logfile': No such file or directory
chgrp: cannot access `/var/log/privoxy/logfile': No such file or directory
chmod: cannot access `/var/log/privoxy/logfile': No such file or directory
touch: cannot touch `/var/log/privoxy/jarfile': No such file or directory
chgrp: cannot access `/var/log/privoxy/jarfile': No such file or directory
chmod: cannot access `/var/log/privoxy/jarfile': No such file or directory


This task depends upon

Closed by  Andrea Scarpino (BaSh)
Saturday, 28 November 2009, 00:59 GMT
Reason for closing:  Not a bug
Additional comments about closing:  see comments
Comment by Andrea Scarpino (BaSh) - Thursday, 26 November 2009, 21:29 GMT
try reinstalling privoxy 3.0.12-3, pacman -Ql privoxy says:
privoxy /var/
privoxy /var/log/
privoxy /var/log/privoxy/
Comment by kat bessie (basementcat) - Friday, 27 November 2009, 02:38 GMT
Reinstalling can't help. As I have mentioned in the report, after rebooting the machine, privoxy can't start.

Indeed, I have written the following in the Arch-wikipedia,

User needs to add the following code after '/bin/bash' in /etc/rc.d/privoxy

if [ ! -d /var/log/privoxy ]
then
mkdir /var/log/privoxy
touch /var/log/privoxy/errorfile
touch /var/log/privoxy/logfile
chown -R privoxy:adm /var/log/privoxy
fi

http://wiki.archlinux.org/index.php/Proxy_routing_with_Tor_and_Privoxy#Installation_and_setup

I hope the updated package can handle the issue and users don't need to do any modifications themselves.
Comment by Nezmer (Nezmer) - Friday, 27 November 2009, 17:09 GMT
Creating unowned dir and files is your solution?

"/var/log/privoxy/" is a part of the package privoxy. If It doesn't exist even after package reinstallation(make sure you're not passing --needed), then something is messed up in your setup.

I use privoxy in both x86_64 and i686 with no problems. I think privoxy is quite popular and nobody else seems to have had issues with the package.
Comment by kat bessie (basementcat) - Saturday, 28 November 2009, 00:09 GMT
Thanks. I take a look of my setup and find that you're right. I am using a netbook and certain hacks needed to be made to prolong the life of the SSD.

In /etc/fstab, it contains:

none /var/log tmpfs size=10M 0 0

Source: http://wiki.archlinux.org/index.php/Acer_Aspire_One#Mounting_Options

The issue I've mentioned is just related to peoele who use a SSD hard drive with the above modification. So, it shouldn't be a bug. Well, somebody may google to come here and find out what they need.

Thanks again.

Loading...