Skip to content

Why agent requires adm group on deb package? #7005

Open
@gcb

Description

@gcb

What's wrong?

seeing #524
and the fix #737

files moved around, new location at https://github.com/rfratto/agent/blob/main/packaging/grafana-agent/deb/control/postinst#L23 still without explanation

instead of simply adding the user to the journald reader permission group systemd-journal, it is also added to adm group with no further explanation why.

adm is usually not required to read logs and can act on a lot more in regular setups.

Steps to reproduce

  1. install
  2. remove user from group
  3. nothing bad happens as far as i can tell.

System information

No response

Software version

No response

Configuration

No response

Logs

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingneeds-attentionAn issue or PR has been sitting around and needs attention.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions