On Wed, Apr 10, 2024 at 01:47:47PM -0600, Dan Nicholson wrote:
> Restarting the timer doesn't make the service run immediately. Are you
> sure logrotate.service has run again since you made this change? Just
> simulate the timer and start logrotate.service again. All the timer
> does is activate
On Wed, Apr 10, 2024 at 1:32 PM Brian Reichert wrote:
>
> On Wed, Apr 10, 2024 at 10:21:32PM +0300, Andrei Borzenkov wrote:
> > On 10.04.2024 22:04, Brian Reichert wrote:
> > > [Install]
> > > WantedBy=logrotate.service
> > >
> >
> > Links in [Install] section are created by "systemctl
On Wed, Apr 10, 2024 at 01:29:10PM -0600, Dan Nicholson wrote:
> On Wed, Apr 10, 2024 at 1:21???PM Andrei Borzenkov
> wrote:
> Just to be complete, your unit won't be triggered until you see it in
> "systemctl show -p Wants logrotate.service". With
> WantedBy=logrotate.service, you'll also find
On Wed, Apr 10, 2024 at 10:21:32PM +0300, Andrei Borzenkov wrote:
> On 10.04.2024 22:04, Brian Reichert wrote:
> > [Install]
> > WantedBy=logrotate.service
> >
>
> Links in [Install] section are created by "systemctl enable".
I could have sworn I did this, but did so (again) just to be sure:
On Wed, Apr 10, 2024 at 1:21 PM Andrei Borzenkov wrote:
>
> On 10.04.2024 22:04, Brian Reichert wrote:
> > On Wed, Apr 10, 2024 at 09:06:09AM -0600, Dan Nicholson wrote:
> >> On Wed, Apr 10, 2024 at 8:50???AM Brian Reichert
> >> wrote:
> >>>
> >>> My current service file:
> >>>
> >>>[Unit]
On 10.04.2024 22:04, Brian Reichert wrote:
On Wed, Apr 10, 2024 at 09:06:09AM -0600, Dan Nicholson wrote:
On Wed, Apr 10, 2024 at 8:50???AM Brian Reichert wrote:
My current service file:
[Unit]
Description=Activities after logrotation
Requires=logrotate.service
On Wed, Apr 10, 2024 at 09:06:09AM -0600, Dan Nicholson wrote:
> On Wed, Apr 10, 2024 at 8:50???AM Brian Reichert wrote:
> >
> > My current service file:
> >
> > [Unit]
> > Description=Activities after logrotation
> >
> > Requires=logrotate.service
> > Wants=logrotate.service
> >
On Wed, Apr 10, 2024 at 8:50 AM Brian Reichert wrote:
>
> My current service file:
>
> [Unit]
> Description=Activities after logrotation
>
> Requires=logrotate.service
> Wants=logrotate.service
> After=logrotate.service
>
> [Service]
> #Type=oneshot
> Type=simple
>
>
On Wed, Apr 10, 2024 at 5:50 PM Brian Reichert wrote:
> My goal is to implement a service that runs after logrotate.service
> completes.
>
> logrotate.service is triggered by a timer logrotate.timer.
>
> I don't want to modify either of logrotate.service or logrotate.timer,
> as they are
My goal is to implement a service that runs after logrotate.service
completes.
logrotate.service is triggered by a timer logrotate.timer.
I don't want to modify either of logrotate.service or logrotate.timer,
as they are provided by the OS vendor (SLES 12 SP5, in my case.)
I've tried to apply
Hello Mantas,
Am Wed, Apr 10, 2024 at 04:45:58PM +0300 schrieb Mantas Mikulėnas:
> On Wed, Apr 10, 2024 at 4:08 PM Alexander Dahl wrote:
>
> > Note: platform here is 32 bit arm, namely v5te on Microchip SAM9X60
> > SoC. Kernel is 6.6, maybe I did not get the kernelconfig right and
> > some
On Wed, Apr 10, 2024 at 4:08 PM Alexander Dahl wrote:
> Note: platform here is 32 bit arm, namely v5te on Microchip SAM9X60
> SoC. Kernel is 6.6, maybe I did not get the kernelconfig right and
> some options are not set correctly? Or maybe those crashes are real?
> Then I could need some help
Hello,
gave it a try and bisected systemd … see below.
Am Wed, Apr 10, 2024 at 12:37:39PM +0200 schrieb Alexander Dahl:
> Hello everone,
>
> I thought I knew how to let the kernel create coredumps … (see below).
>
> Am Tue, Apr 09, 2024 at 04:21:21PM +0200 schrieb Alexander Dahl:
> > Hello
Hello everone,
I thought I knew how to let the kernel create coredumps … (see below).
Am Tue, Apr 09, 2024 at 04:21:21PM +0200 schrieb Alexander Dahl:
> Hello Lennart,
>
> thanks for your quick reply, see below.
>
> Am Tue, Apr 09, 2024 at 03:53:24PM +0200 schrieb Lennart Poettering:
> > On
On Tue, Apr 09, 2024 at 11:37:39AM +0300, Mikko Rapeli wrote:
> Hi,
>
> On Mon, Feb 19, 2024 at 11:53:14AM +0100, Lennart Poettering wrote:
> > For your usecase the new tpm2.target available in git main is what you
> > really should focus on: all TPM using services should order themselves
> >
15 matches
Mail list logo
