Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #267663

rec recording, Re: Upgrade to Bookworm, now GNOME keyring dies …

From David Wright <deblis@lionunicorn.co.uk>
Newsgroups linux.debian.user
Subject rec recording, Re: Upgrade to Bookworm, now GNOME keyring dies …
Date 2024-02-21 19:50 +0100
Message-ID <I9ZPj-bGQP-1@gated-at.bofh.it> (permalink)
References <H2tMW-1GXx-227@gated-at.bofh.it> <I9huV-bg7b-5@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Mon 19 Feb 2024 at 13:26:17 (-0600), Nate Bargmann wrote:
> 
> After seeing this twice this morning I recalled that I have a cron entry
> to kill the 'rec' program.  This was to break up audio files into hourly
> segments when recording an amateur radio event.  This was the cron
> command:
> 
> # Rotate sound recorder files
> 00 * * * * /usr/bin/pkill -f rec > /dev/null 2> /dev/null
> 
> On a hunch I commented that line and Voila! the daemon ran through the
> next hour change and is still running as expected.  The man page states
> that the '-f' option matches against the full command line, not just the
> process name.  So, looking at the gnome-keyring-daemon command line:
> 
>    1857 ?        SLsl   0:00 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring
> 
> I see that the 'rec' in 'directory' provided the match!  Confirmed with
> pgrep:
> 
> $ pgrep -f rec
> 1857
> 
> It looks like the solution for the future will be to change the cron
> line to:
> 
> 00 * * * * /usr/bin/pkill -f /usr/bin/rec > /dev/null 2> /dev/null

I can't get that to work here. When I kill rec, it just dies. Is pkill
sending SIGTERM, which appears to be the default? Nor can I find this
documented—though the sox docs are lengthy, so I might have missed it.

I can use SIGUSR1 with arecord, and that works perfectly.

Cheers,
David.

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Upgrade to Bookworm, now GNOME keyring dies--no access to stored SSH  key passwords Nate Bargmann <n0nb@n0nb.us> - 2023-08-14 02:40 +0200
  Re: Upgrade to Bookworm, now GNOME keyring dies--no access to stored  SSH key passwords Max Nikulin <manikulin@gmail.com> - 2023-08-15 04:30 +0200
    Re: Upgrade to Bookworm, now GNOME keyring dies--no access to stored  SSH key passwords Nate Bargmann <n0nb@n0nb.us> - 2023-09-11 13:40 +0200
  Re: Upgrade to Bookworm, now GNOME keyring dies--no access to stored  SSH key passwords Nate Bargmann <n0nb@n0nb.us> - 2024-02-19 20:30 +0100
    rec recording, Re: Upgrade to Bookworm, now GNOME keyring dies … David Wright <deblis@lionunicorn.co.uk> - 2024-02-21 19:50 +0100
      Re: rec recording, Re: Upgrade to Bookworm, now GNOME keyring dies … Nate Bargmann <n0nb@n0nb.us> - 2024-02-21 20:10 +0100

csiph-web