fedora rpm doesn't log by default?

added component::core tor/rpm packaging owner::hiviah priority::medium resolution::invalid severity::normal status::closed type::defect version::0.2.1.19 labels

see https://bugzilla.redhat.com/show_bug.cgi?id=532373#c6

Trac:
Username: ensc

Enrico Scholz (the Fedora package maintainer) has stated that he will not fix this (https://bugzilla.redhat.com/show_bug.cgi?id=532373#c6). arma's response (https://bugzilla.redhat.com/show_bug.cgi?id=532373#c19) has received no reply, and the Fedora bug (#532373) has been closed.

Trac:
Username: katmagic
Actualpointsdone: N/A to N/A
Resolution: None to wontfix
Milestone: N/A to N/A
Status: assigned to closed
Parent: N/A to N/A
Points: N/A to N/A
Actualpoints: N/A to N/A
Pointsdone: N/A to N/A
Keywords: N/A deleted, N/A added

Trac:
Description: It looks like the fedora rpm doesn't set any Log lines in the torrc, but it does set RunAsDaemon 1 so it forks into the background. If you don't set any Log lines in the torrc file, then Tor will log to stdout by default. And the fork will close that log.

Are all the rpm users supposed to know to uncomment a Log line?

The deb patches the Tor code so Tor defaults to logging to a file rather than stdout: https://git.torproject.org/checkout/tor/master/debian/patches/07_log_to_file_by_default.dpatch

Or maybe the torrc on fedora rpm should just uncomment the 'log notice file ...' line?

[Automatically added by flyspray2trac: Operating System: All]

to

It looks like the fedora rpm doesn't set any Log lines in the torrc, but it does set RunAsDaemon 1 so it forks into the background. If you don't set any Log lines in the torrc file, then Tor will log to stdout by default. And the fork will close that log.

Are all the rpm users supposed to know to uncomment a Log line?

The deb patches the Tor code so Tor defaults to logging to a file rather than stdout: https://git.torproject.org/checkout/tor/master/debian/patches/07_log_to_file_by_default.dpatch

Or maybe the torrc on fedora rpm should just uncomment the 'log notice file ...' line?

[Automatically added by flyspray2trac: Operating System: All]
Resolution: wontfix to N/A
Status: closed to reopened

This sucks. The packager for Fedora breaks our recommendations for no good reason?

He doesn't have to deal with users who don't have logs and don't realize that it's Fedora's fault, not our fault, that they don't have logs.

I guess we should add another clause to https://www.torproject.org/docs/faq#Logs saying "if you're using Fedora's RPM, you will have to set up your logs manually because the package doesn't do it for you"?

Bleah.

Trac:
Priority: minor to normal

Trac:
Component: Tor bundles/installation to RPM packaging

Trac:
Status: reopened to assigned
Owner: erinn to hiviah

The line is still (0.2.3.22rc) commented out in rpm's torrc, but it currently has identical effect to:

Log notice file /var/log/tor/notices.log

I.e. logging of recommended "notice" level is on. Should the logging be explicitly enabled by uncommenting the line?

This ticket is also about the RPM shipped by Fedora, which no one who would look at this bugtracker has any control over.

Is it still the case that the tor rpm that fedora ships is broken in this way? (Should we send fedora a cease-and-desist notice telling them to quit shipping broken tor rpms?)

The torproject does not longer provide RPMs.

Trac:
Severity: N/A to Normal
Status: assigned to closed
Cc: arma,erinn to arma, erinn
Sponsor: N/A to N/A
Resolution: N/A to invalid
Reviewer: N/A to N/A

closed

moved to tpo/core/rpm-package#1133 (closed)

fedora rpm doesn't log by default?

Child items 0

Activity