Bug #4592
closed
- Status changed from New to Feedback
- Target version set to 2.2.2
- % Done changed from 0 to 100
2.2.2 is going to p9, what will have the fix
I don't see where that got committed to RELENG_10_1 Renato, you sure that's in there?
- Target version changed from 2.2.2 to 2.2.3
So, no chance for a patch until 2.2.3? I'd like to contribute on the squid package for pfSense, but we can't rely on service squid stop until this signal problem is fixed.
yes, 2.2.2-RELEASE is already built. we can get that patch into 2.2.3 snapshots at some point after 2.2.2, probably within a few days.
Okay, great! Will you be referencing this bug in the changelog so I'll know when it goes into the 2.2.3 snapshots?
- Affected Version changed from 2.2.1 to 2.2
Yeah, we'll update this ticket then. If you could help confirm the issue fixed at that point, that'd be appreciated.
Chris Buechler wrote:
I don't see where that got committed to RELENG_10_1 Renato, you sure that's in there?
You are right, I misread it. We need to apply the patch on our kernel to get it done on 10.1
I just wanted to bump this bug report: I tested with 2.2.2, and it still dumps core (as Chris mentioned above).
I'm happy to test 2.2.3 dailies as soon as they're available.
- Category set to Operating System
- Status changed from Feedback to Confirmed
- Assignee set to Renato Botelho
- Status changed from Confirmed to Feedback
I've backported revisions from stable/10 and applied on 2.2.x snapshots
Just did a firmware update to the latest 2.2.3 snapshot and shutdown works. Looking forward to the full 2.2.3 release.
- Status changed from Feedback to Resolved
Also available in: Atom
PDF