Summary: | sys-process/cronie segfaults in libpthread | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | David Mohr <bugs> |
Component: | [OLD] Core system | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cron-bugs+disabled |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
David Mohr
2015-08-12 20:43:47 UTC
You really need to more clearly define the steps to reproduce this. What exactly did you do before crond started segfaulting? Was it an upgrade? Between what versions? In any case, ebuilds do not typically restart daemons. That becomes especially tricky since we now support multiple init systems. I think the best you are going to get here is a pkg_posinst message. I apologize, I can't describe the steps well because the updates on this machine had been stuck for a little while. Then I fixed the issues preventing a successful emerge run and just did an "emerge -vuND world" (which updated many many packages). But if you google for cronie segfault libpthread then this seems to not be uncommon, and restarting the daemon is the default recommendation (heck, Debian does that by default even). There's no abstractions for the multiple init systems yet? That seems a pitty. But yeah, a notice would be a big improvement IMHO. commit b96a43b993a5bd442127e2e5d495fbbdc7a1e674 Author: Lars Wendler <polynomial-c@gentoo.org> Date: Sun Aug 30 15:09:46 2015 sys-process/cronie: Warn on update to restart daemon (bug #557406). Package-Manager: portage-2.2.20.1 https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b96a43b993a5bd442127e2e5d495fbbdc7a1e674 |