Logging level cannot be changed by SIGHUP when destination is journald #313

New Issue

Closed

opened 2024-02-16 11:18:25 +00:00 by ironbee · 2 comments

ironbee commented

2024-02-16 11:18:25 +00:00

Journald logger initialisation is broken and needs fixing.

ironbee added the

bug

label 2024-02-16 11:18:25 +00:00

ironbee self-assigned this 2024-02-16 11:18:50 +00:00

fyrchik commented

2024-02-16 11:37:31 +00:00

Owner

Is it a bug in the library or s3-gw?

alexvanin commented

2024-02-16 11:43:15 +00:00

Owner

@fyrchik s3-gw

fyrchik referenced this issue from TrueCloudLab/frostfs-node

2024-02-16 12:43:14 +00:00

SIGHUP doesn't affect logger.level when used with journald #991

ironbee referenced a pull request that will close this issue

2024-02-16 14:45:31 +00:00

Fix logging level changing for journald #315

alexvanin closed this issue

2024-02-16 15:06:01 +00:00

alexvanin referenced this issue from a commit

2024-02-16 15:06:02 +00:00

[#313] logger: Fix logging level changing for journald

alexvanin added this to the v0.29.0 milestone 2024-02-16 15:06:15 +00:00

alexvanin modified the milestone from v0.29.0 to v0.28.0

2024-05-27 10:22:16 +00:00

alexvanin modified the milestone from v0.28.0 to v0.29.0

2024-05-27 10:22:19 +00:00

No Label

No Milestone

No Assignees

3 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-s3-gw#313

There is no content yet.