Opened 3 years ago

Last modified 14 months ago

#16350 new defect

tor.pid should be deleted on exit in every case possible, like assert termination, and catchable signals

Reported by: yurivict271 Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-relay cleanup
Cc: Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor:

Description

I had tor fail with assertion, printing message into log and exiting, yet it left tor.pid. It could have easily delete it, since this wasn't the non-catchable signal.

It doesn't make sense to leave tor.pid when tor exited.

0.2.6.7 on FreeBSD

Child Tickets

Change History (6)

comment:1 Changed 3 years ago by gk

Component: - Select a componentTor

comment:2 Changed 3 years ago by teor

Milestone: Tor: 0.2.???
Points: small

comment:3 Changed 21 months ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:4 Changed 20 months ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:5 Changed 15 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:6 Changed 14 months ago by nickm

Keywords: tor-relay cleanup added
Points: small3
Severity: Normal
Note: See TracTickets for help on using tickets.