Repository navigation
apache logadm #213
Description
Activity
I'm not sure of a good fix for this. I don't want to remove it as that will just break everyone who doesn't use rotatelogs. Something we could do is add a
PKG_SKIP_LOGADMenvironment variable in a similar manner toPKG_SKIP_SMFto not do the logadm bits during install, but you may want to continue using logadm entries for other packages.Suggestions welcome here.
Adding
PKG_SKIP_LOGADMlooks nice!- added a commit that references this issue
on Aug 26, 2019 @ jperkin Any way to get PKG_SKIP_LOGADM? :)
It's unlikely that I'm going to have time to work on this, but I'd certainly be happy to review patches to accomplish something like it.
- added a commit that references this issue
on Aug 25, 2020 - added a commit that references this issue
on Nov 6, 2020 - added a commit that references this issue
on Jun 4, 2021 - added a commit that references this issue
on Jun 15, 2021 - added a commit that references this issue
on Dec 2, 2021 66 remaining items
- added 3 commits that reference this issue
on May 22, 2026 - added 3 commits that reference this issue
on Jun 1, 2026 - added a commit that references this issue
on Jul 17, 2026
Metadata
Metadata
Assignees
Labels
No labels
Would it be possible to remove the logadm stuff from the apache package?
Cause if someone uses rotatelogs, after each update of the apache package there is a new line in logadm.conf which needs to be removed...