Re: door bell like sound effect

[songbird]

Karl Vogel wrote:
> On Wed, Aug 30, 2023 at 07:55:14AM -0400, songbird wrote:
>> Karl Vogel wrote:
>> ...
>> > If nothing else, it's faster to run "locate" and look for file extensions;
>> > running "file" on that much crap took nearly 9 hours.
>> 
>> do you have SSDs or spinning rust?
>
>   I have a 256-Gb SSD and two mirrored Western Digital Blue 1.8-Tb drives.
>   About 2 million files are on SSD and the rest are on rust.
>
>   I used "file" v5.45 built from source, which does a nice job but is IO-
>   and CPU-intensive.

  mirroring is going to be quite a difference, especially 
if you are updating each file's access time (see below).


>> when i just did this:
>> # find / -type f | wc -l
>> it took all of 24 seconds for the 2.4 million files found.
>
>   Generating hashes for SSD files is faster than getting the filetype;
>   it takes about 17 minutes for 3.6 million files (153 Gbytes).  I like
>   the Blake-2 hash cuz it's fast as hell, among other things:
>
> #!/bin/ksh
> #
> export PATH=/usr/local/bin:/bin:/usr/bin
> tag=${0##*/}
> set -o nounset
> umask 022
>
> logmsg () { logger -t "$tag" "$@"; }
> die (){ logmsg "FATAL: $@"; exit 1; }
>
> work=$(mktemp -q "/tmp/$tag.work.XX")
> case "$?" in
> 0)  test -f "$work" || die "$work: tmp list file not found" ;;
> *)  die "can't create work file" ;;
> esac
>
> # Get a list of all regular files on SSD.
>
> mount | grep '^zroot' | awk '{print $3}' |
>   while read dataset
>   do
>   logmsg "listing $dataset"
>   find "$dataset" -xdev -type f -print0 >> $work
>   done
>
> # Store hashes for SSD datasets.
> # The hash file is sorted by filename to make comparisons easier.
>
> logmsg "running b2sum"
> fdbdir=$(date '+/var/fdb/%Y/%m%d')
> sort -z $work | xargs -0r b2sum -l 128 > "$fdbdir/zroot.sum"
> rm $work
> exit 0
>
>   Useful for finding changed files -- security, backups, etc.
>
>> what script did you use?
>
> #!/bin/ksh
> #
> export PATH=/usr/local/bin:/bin:/usr/bin
> set -o nounset
> tag=${0##*/}
> umask 022
>
> logmsg () { logger -t "$tag" "$@"; }
>
> work="/tmp/$tag.$$"
> fsys="/ /doc /home /usr/local /search /usr/src /dist /src"
>
> logmsg start
> find $fsys -xdev -print0 | xargs -0 file -N --mime-type > $work
> logmsg finish
>
> mv $work filetypes
> exit 0

  interesting and thanks for that.  :)

  my comments that follow are geared towards finding the
files that have been referenced and changed only in recent
times so that you are not having to process the entire 
file system.

  so the find statement would be adjusted to use -cmin or 
-amin (depending upon if i want to find changes or accessed 
files) and the file command would include the parameter 
flag -p to avoid updating the access time.


  as for the other topic of finding changed files and using
hashes is a whole different topic and one that i don't need.
this is the sort of thing that git can do so i would not
want to reinvent that if i don't really need to (which at
present i don't).  i keep track of certain directories and
that's all i need.  for directories or file systems that i
need read only i use the read only mount feature or set
permissions.


  songbird

Re: door bell like sound effect

[Michel Verdier]

On 2023-08-30, Karl Vogel wrote:

> logmsg "running b2sum"
> fdbdir=$(date '+/var/fdb/%Y/%m%d')
> sort -z $work | xargs -0r b2sum -l 128 > "$fdbdir/zroot.sum"
> rm $work
> exit 0
>
>   Useful for finding changed files -- security, backups, etc.

tripwire from local host and stealth from remote host do this more
securely. Both are packaged.

Re: door bell like sound effect

[Karl Vogel]

On Wed, Aug 30, 2023 at 07:55:14AM -0400, songbird wrote:
> Karl Vogel wrote:
> ...
> > If nothing else, it's faster to run "locate" and look for file extensions;
> > running "file" on that much crap took nearly 9 hours.
> 
> do you have SSDs or spinning rust?

  I have a 256-Gb SSD and two mirrored Western Digital Blue 1.8-Tb drives.
  About 2 million files are on SSD and the rest are on rust.

  I used "file" v5.45 built from source, which does a nice job but is IO-
  and CPU-intensive.

> when i just did this:
> # find / -type f | wc -l
> it took all of 24 seconds for the 2.4 million files found.

  Generating hashes for SSD files is faster than getting the filetype;
  it takes about 17 minutes for 3.6 million files (153 Gbytes).  I like
  the Blake-2 hash cuz it's fast as hell, among other things:

#!/bin/ksh
#> $work
  done

# Store hashes for SSD datasets.
# The hash file is sorted by filename to make comparisons easier.

logmsg "running b2sum"
fdbdir=$(date '+/var/fdb/%Y/%m%d')
sort -z $work | xargs -0r b2sum -l 128 > "$fdbdir/zroot.sum"
rm $work
exit 0

  Useful for finding changed files -- security, backups, etc.

> what script did you use?

#!/bin/ksh
# $work
logmsg finish

mv $work filetypes
exit 0

-- 
Karl Vogel  I don't speak for the USAF or my company

Assisted in daily preparation of large quantities of consumable items
in a fast-paced setting.  (Translation: Short-order cook)
--from a list of resume' blunders

Re: door bell like sound effect

[Anders Andersson]

On Wed, Aug 30, 2023 at 12:50 PM Karl Vogel  wrote:
>
> Out of morbid curiosity (and boredom), I started wondering what types of
> audio files I had on my systems.  I ran "file --mime-type" on 6.8 million
> files, looked for "audio/whatever" and got the file extensions.
>
> Extension  MIME-type
> ---
> .8svx  audio/x-aiff
> .aif   audio/x-aiff
> .aifc  audio/x-aiff
> .aiff  audio/x-aiff
> .ape   audio/x-ape
> .arm   audio/amr
> .auaudio/basic
> .flac  audio/flac
> .m4a   audio/x-m4a
> .mp3   audio/mpeg
> .mpc   audio/x-musepack
> .oga   audio/ogg
> .ogg   audio/ogg
> .opus  audio/ogg
> .raaudio/x-pn-realaudio
> .voc   audio/x-unknown
> .wav   audio/x-wav
>
> If nothing else, it's faster to run "locate" and look for file extensions;
> running "file" on that much crap took nearly 9 hours.

I got curious so I performed the same exercise on 2737754 files (18
TB) taking over 2.5 hours:

real159m40.601s
user38m47.758s
sys16m34.408s

I realized that it did it twice because of a snapshot so it's only
half the files, but here's the result:

1 ft audio/x-mod
1 mid audio/midi
2 ac3 audio/vnd.dolby.dd-raw
2 data audio/mpeg
2 opus audio/ogg
4 3gp audio/x-m4a
4 ape audio/x-ape
4 it audio/x-mod
5 m4a audio/x-m4a
16 snd audio/x-aiff
20 t audio/x-aiff
25 mp3 audio/x-wav
84 wav audio/x-wav
104 s audio/x-aiff
115 ogg audio/ogg
248 xm audio/x-mod
768 b audio/x-aiff
916 a audio/x-aiff
11805 flac audio/flac
26521 mp3 audio/mpeg
74874 mod audio/x-mod

Notably it's missing 52884 .sid files which 'file' did not recognize,
and a number of NES and SNES audio files.

Re: door bell like sound effect

[gene heskett]

On 8/30/23 10:48, Greg Wooledge wrote:

On Wed, Aug 30, 2023 at 10:15:50AM -0400, gene heskett wrote:

On 8/29/23 15:59, Greg Wooledge wrote:

find . -name '*.snd' -print

many definitions, tell me about it. I made a command line to aplay anything
it found, but so far only ogg's and wav's, neither of which aplay can do
anything with except digital noise. Says raw file and does not
adequately/automatically decode it.


aplay should work with .wav files, if they are properly created and
not corrupted.  I think.  (It gets ugly because I think there are
big-endian and little-endian variants, and possibly sampling rate
variants)


So that is not working. The theory is that whatever format it is, is very
well supported by the player it is using.


Which leads to the obvious question -- what player(s) are you using?
You seem to have a desktop environment installed on this machine, right?
Which desktop is it?  What audio players does this come with?  Which
ones do you normally use?


Is there another "player" that
might understand and properly decode whatever its fed?


Are you saying you've never actually PLAYED AN AUDIO FILE before?  At all?
I know you're old enough to have lived through the Napster period of
history.  You never once downloaded and played an MP3 file?

If you're looking to add a player to your repertoire, and if you don't
like whatever your desktop environment supplied, I would suggest starting
with mpv.


And is installed by a
default bookworm install?


There is no such animal.  There's just whatever package suites you chose
during installation, and whatever you added afterward.


Or, ugly thought, I need to tell aplay what it is.


aplay is fairly low level.  It doesn't handle decoding things like FLAC,
Ogg Vorbis, MP3, etc.  It only plays straight digital audio files, like
.wav.

If 'aplay myfile.wav' doesn't work, just forget it, and move on to a
more full-featured audio player.


And I've not paid much attention to the audio since the original vorbis/ogg
development so I know zip about the current details.


My knowledge pretty much ends with "mpv has replaced mplayer as the
go-to choice for command line users".  This is because mpv hasn't ever
failed me in a way that would require me to learn more things.


That too is helpful, Greg, msg tagged

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/30/23 09:32, zithro wrote:

On 30 Aug 2023 04:52, gene heskett wrote:

man systemctl ; look for "timer" (in vi(m) use "/" to search) ?

$ systemctl list-timers


Tried this one ?


Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could 
also have used xmms, audacity, VLC, mpv, etc.


tried aplay, got server dead response. htop cannot find aplay,


The application playing the sound is most probably dead when you check 
for it ! Read below.



?!
I think you didn't understand what I meant.
To play a sound, there needs to be an app launching it.
So I suggested than instead of "find"ing the sound itself, you try 
to "grep" the application/executable name.
Agreed this could be long, as you don't know where that sound is 
played from.


And that is the problem, and why I read thru all those man pages 
trying to find a way to make it log what it did. Sadly no.


So, let me show you what I was thinking about.

I show you commands which will "find" for executable files which are not 
shared libraries, and for each file found, will "grep" for application 
names.
This approach will not try to find the sound(s) themselves, but the 
"applications which can play sounds".


First, make sure to have a list of ALL the audio apps installed on your 
system. From this list, you will just need the executable NAME, not the 
full path.

Examples: aplay, vlc, audacity, mplayer, mpv, ...

Then, run either the SHORT or LONG FORM of these find commands as root 
(or with sudo), but add your own applications from your app list above.

Warning: commands are both on one line !

++ FIND - LONG FORM

find -P / \! -iname "*.so" -type f -executable -exec grep --color 
--binary-files=without-match --with-filename --line-number -E 
'aplay|vlc|audacity' '{}' \;


++ FIND - SHORT FORM

find -P / \! -iname "*.so" -type f -executable -exec grep --color -IHnE 
'aplay|vlc|audacity' '{}' \;


++ APP LIST

As said above, you will have to change :
     'aplay|vlc|audacity'
with the application names you have on your computer, for example :
     'aplay|vlc|audacity|mpv|mplayer'

++ PARAMETERS EXPLANATIONS

-P : never follow symlinks (we going to check the whole FS, so no point)
\! -iname "*.so" : dont include shared libs
-type f : files only (no directory, etc)
-executable : executable file
-exec : run a command for each file found. Here the command is GREP,
     which scans for application names inside the executable files
     The grep options used are almost self-explanatory, I showed the
     long form on purpose.

++ SAMPLE OUTPUT

Instead of "/", I used "/usr" :

     # find -P / \! -iname "*.so" -type f -executable -exec grep --color 
-IHnE 'aplay|vlc|audacity' '{}' \;


     /usr/bin/rvlc:2:exec /usr/bin/vlc -I "rc" "$@"
     /usr/bin/pa-info:83:    'aplay -L'
     /usr/bin/cvlc:2:exec /usr/bin/vlc -I "dummy" "$@"
     /usr/sbin/alsa-info:110:withaplay() {
     /usr/sbin/alsa-info:116:    aplay -l >> $FILE 2>&1
     [OUTPUT TRUNCATED]

HTH


This looks to be useful also. Thank you zithro.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/30/23 04:21, Karl Vogel wrote:

Out of morbid curiosity (and boredom), I started wondering what types of
audio files I had on my systems.  I ran "file --mime-type" on 6.8 million
files, looked for "audio/whatever" and got the file extensions.

 Extension  MIME-type
 ---
 .8svx  audio/x-aiff
 .aif   audio/x-aiff
 .aifc  audio/x-aiff
 .aiff  audio/x-aiff
 .ape   audio/x-ape
 .arm   audio/amr
 .auaudio/basic
 .flac  audio/flac
 .m4a   audio/x-m4a
 .mp3   audio/mpeg
 .mpc   audio/x-musepack
 .oga   audio/ogg
 .ogg   audio/ogg
 .opus  audio/ogg
 .raaudio/x-pn-realaudio
 .voc   audio/x-unknown
 .wav   audio/x-wav

If nothing else, it's faster to run "locate" and look for file extensions;
running "file" on that much crap took nearly 9 hours.


Probably 2 to 4x that here...

Thank you Karl. You and David have given me a couple tagged posts that I 
can explore when I get out of a pool full of unrelated alligators. It 
appears I will have to break down and get a hot box for at least one of 
my 3d printers.


Thank you

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/29/23 22:12, Max Nikulin wrote:

On 30/08/2023 01:58, gene heskett wrote:

bash: pactl: command not found
gene@coyote:~$ sudo apt install pactl

...

E: Unable to locate package pactl

Next?


Either apt-file suggested earlier or if you are using it rarely and 
prefer to avoid downloading of file lists for all packages then


https://packages.debian.org/file:pactl

Thunderbird calendar, korganizer, alarm applets or applications may 
be suspected as well.


Those would all be under /home/me/.local? FWIW I am the only live user. 


At least thunderbird keeps its files in ~/.thunderbird by default. 
Perhaps KDE application might continue using legacy ~/.kde if the 
directory already contains their files. My idea is to check if you have 
accidentally scheduled events without waiting a next alarm.


I'm using t-bird but its quite buggy, filters only work if the moon is 
in a certain phase, its unread mail counter is a semi-random number 
generator. Because I don't thinks its at all trustworthy, I have not 
setup any scheduled actions.  And in this case, I had this problem way 
way back up the log 15 years ago running TDE for a desktop and the old 
3.5 TDE's kmail... I'd like to run it again, but since the end of wheezy 
support, dependency hell has prevented that.


I've now installed apt-file, updated it, and pulseaudio.utils. 
Somewhere here there should be something that can keep a log. That would 
be immensely helpful.


Thanks.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[Curt]

On 2023-08-29, Larry Martell  wrote:
> On Tue, Aug 29, 2023 at 12:59 PM Greg Wooledge  wrote:
>>
>> On Tue, Aug 29, 2023 at 09:29:35AM -0700, Larry Martell wrote:
>> > find . -regex '.*\.snd$' -print
>>
>> That is an incredibly silly way to write
>>
>> find . -name '*.snd' -print
>
> Gene said that was finding many files that had snd in their name and
> not just as the terminal extension. So I gave a command that would
> only find files that ended with .snd.

That's not how it's supposed to work, though, I wouldn't think.

>> But the bigger issue is that audio files may have MANY different
>> extensions, with .snd being only one of them.
>
> Yes, I know that - I was showing an example using what was previously posted.
>
>


-- 

Re: door bell like sound effect

[Greg Wooledge]

On Wed, Aug 30, 2023 at 10:15:50AM -0400, gene heskett wrote:
> On 8/29/23 15:59, Greg Wooledge wrote:
> > find . -name '*.snd' -print
> many definitions, tell me about it. I made a command line to aplay anything
> it found, but so far only ogg's and wav's, neither of which aplay can do
> anything with except digital noise. Says raw file and does not
> adequately/automatically decode it.

aplay should work with .wav files, if they are properly created and
not corrupted.  I think.  (It gets ugly because I think there are
big-endian and little-endian variants, and possibly sampling rate
variants)

> So that is not working. The theory is that whatever format it is, is very
> well supported by the player it is using.

Which leads to the obvious question -- what player(s) are you using?
You seem to have a desktop environment installed on this machine, right?
Which desktop is it?  What audio players does this come with?  Which
ones do you normally use?

> Is there another "player" that
> might understand and properly decode whatever its fed?

Are you saying you've never actually PLAYED AN AUDIO FILE before?  At all?
I know you're old enough to have lived through the Napster period of
history.  You never once downloaded and played an MP3 file?

If you're looking to add a player to your repertoire, and if you don't
like whatever your desktop environment supplied, I would suggest starting
with mpv.

> And is installed by a
> default bookworm install?

There is no such animal.  There's just whatever package suites you chose
during installation, and whatever you added afterward.

> Or, ugly thought, I need to tell aplay what it is.

aplay is fairly low level.  It doesn't handle decoding things like FLAC,
Ogg Vorbis, MP3, etc.  It only plays straight digital audio files, like
.wav.

If 'aplay myfile.wav' doesn't work, just forget it, and move on to a
more full-featured audio player.

> And I've not paid much attention to the audio since the original vorbis/ogg
> development so I know zip about the current details.

My knowledge pretty much ends with "mpv has replaced mplayer as the
go-to choice for command line users".  This is because mpv hasn't ever
failed me in a way that would require me to learn more things.

Re: door bell like sound effect

[gene heskett]

On 8/29/23 15:59, Greg Wooledge wrote:

find . -name '*.snd' -print
many definitions, tell me about it. I made a command line to aplay 
anything it found, but so far only ogg's and wav's, neither of which 
aplay can do anything with except digital noise. Says raw file and does 
not adequately/automatically decode it.


So that is not working. The theory is that whatever format it is, is 
very well supported by the player it is using. Is there another "player" 
that might understand and properly decode whatever its fed? And is 
installed by a default bookworm install? Or, ugly thought, I need to 
tell aplay what it is.  And I've not paid much attention to the audio 
since the original vorbis/ogg development so I know zip about the 
current details.


Thanks.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[tomas]

On Wed, Aug 30, 2023 at 09:23:24AM -0400, Greg Wooledge wrote:

[...]

> For the record, "-exec file {} +" isn't a GNU extension.  That's actually
> portable (it's in POSIX).

Thanks... I stand corrected :)

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: door bell like sound effect

[zithro]

On 30 Aug 2023 04:52, gene heskett wrote:

man systemctl ; look for "timer" (in vi(m) use "/" to search) ?

$ systemctl list-timers


Tried this one ?


Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also 
have used xmms, audacity, VLC, mpv, etc.


tried aplay, got server dead response. htop cannot find aplay,


The application playing the sound is most probably dead when you check 
for it ! Read below.



?!
I think you didn't understand what I meant.
To play a sound, there needs to be an app launching it.
So I suggested than instead of "find"ing the sound itself, you try to 
"grep" the application/executable name.
Agreed this could be long, as you don't know where that sound is 
played from.


And that is the problem, and why I read thru all those man pages trying 
to find a way to make it log what it did. Sadly no.


So, let me show you what I was thinking about.

I show you commands which will "find" for executable files which are not 
shared libraries, and for each file found, will "grep" for application 
names.
This approach will not try to find the sound(s) themselves, but the 
"applications which can play sounds".


First, make sure to have a list of ALL the audio apps installed on your 
system. From this list, you will just need the executable NAME, not the 
full path.

Examples: aplay, vlc, audacity, mplayer, mpv, ...

Then, run either the SHORT or LONG FORM of these find commands as root 
(or with sudo), but add your own applications from your app list above.

Warning: commands are both on one line !

++ FIND - LONG FORM

find -P / \! -iname "*.so" -type f -executable -exec grep --color 
--binary-files=without-match --with-filename --line-number -E 
'aplay|vlc|audacity' '{}' \;


++ FIND - SHORT FORM

find -P / \! -iname "*.so" -type f -executable -exec grep --color -IHnE 
'aplay|vlc|audacity' '{}' \;


++ APP LIST

As said above, you will have to change :
'aplay|vlc|audacity'
with the application names you have on your computer, for example :
'aplay|vlc|audacity|mpv|mplayer'

++ PARAMETERS EXPLANATIONS

-P : never follow symlinks (we going to check the whole FS, so no point)
\! -iname "*.so" : dont include shared libs
-type f : files only (no directory, etc)
-executable : executable file
-exec : run a command for each file found. Here the command is GREP,
which scans for application names inside the executable files
The grep options used are almost self-explanatory, I showed the
long form on purpose.

++ SAMPLE OUTPUT

Instead of "/", I used "/usr" :

# find -P / \! -iname "*.so" -type f -executable -exec grep --color 
-IHnE 'aplay|vlc|audacity' '{}' \;


/usr/bin/rvlc:2:exec /usr/bin/vlc -I "rc" "$@"
/usr/bin/pa-info:83:'aplay -L'
/usr/bin/cvlc:2:exec /usr/bin/vlc -I "dummy" "$@"
/usr/sbin/alsa-info:110:withaplay() {
/usr/sbin/alsa-info:116:aplay -l >> $FILE 2>&1
[OUTPUT TRUNCATED]

HTH

--
++
zithro / Cyril

Re: door bell like sound effect

[songbird]

 wrote:
...
> Yours just sailed through the directory structures.

  yes, i know that, which is why i asked.  ;)


  songbird

Re: door bell like sound effect

[Greg Wooledge]

On Wed, Aug 30, 2023 at 02:57:35PM +0200, to...@tuxteam.de wrote:
> Karl ran (probably -exec) "file --mimetype" on each one, which at
> least involves opening each of the files once and reading a few
> (tens of) bytes off it.
> 
> Depending on how he invoked it (with a \; at the end of find or
> with GNU find's extension +, that could means starting `file'
> for each found ummm... file, which also takes time.

For the record, "-exec file {} +" isn't a GNU extension.  That's actually
portable (it's in POSIX).

The other way, "find ... -print0 | xargs -0 file", *is* a GNU extension.

Re: door bell like sound effect

[tomas]

On Wed, Aug 30, 2023 at 07:43:51AM -0400, songbird wrote:
> Karl Vogel wrote:
> ...
> > If nothing else, it's faster to run "locate" and look for file extensions;
> > running "file" on that much crap took nearly 9 hours.
> 
>   do you have SSDs or spinning rust?
> 
>   when i just did this:
> 
> # find / -type f | wc -l
> 
>   it took all of 24 seconds for the 2.4 million files found.
> what script did you use?

Karl ran (probably -exec) "file --mimetype" on each one, which at
least involves opening each of the files once and reading a few
(tens of) bytes off it.

Depending on how he invoked it (with a \; at the end of find or
with GNU find's extension +, that could means starting `file'
for each found ummm... file, which also takes time.

Yours just sailed through the directory structures.

Cheers
-- 
t


signature.asc
Description: PGP signature

Re: door bell like sound effect

[songbird]

Karl Vogel wrote:
...
> If nothing else, it's faster to run "locate" and look for file extensions;
> running "file" on that much crap took nearly 9 hours.

  do you have SSDs or spinning rust?

  when i just did this:

# find / -type f | wc -l

  it took all of 24 seconds for the 2.4 million files found.
what script did you use?


  songbird

Re: door bell like sound effect

[Karl Vogel]

Out of morbid curiosity (and boredom), I started wondering what types of
audio files I had on my systems.  I ran "file --mime-type" on 6.8 million
files, looked for "audio/whatever" and got the file extensions.

Extension  MIME-type
---
.8svx  audio/x-aiff
.aif   audio/x-aiff
.aifc  audio/x-aiff
.aiff  audio/x-aiff
.ape   audio/x-ape
.arm   audio/amr
.auaudio/basic
.flac  audio/flac
.m4a   audio/x-m4a
.mp3   audio/mpeg
.mpc   audio/x-musepack
.oga   audio/ogg
.ogg   audio/ogg
.opus  audio/ogg
.raaudio/x-pn-realaudio
.voc   audio/x-unknown
.wav   audio/x-wav

If nothing else, it's faster to run "locate" and look for file extensions;
running "file" on that much crap took nearly 9 hours.

-- 
Karl Vogel  I don't speak for anyone but myself

My doctor told me to stop having intimate dinners for four,
unless there are three other people.--Orson Welles

Re: door bell like sound effect

[David Wright]

On Tue 29 Aug 2023 at 23:54:41 (-0400), Karl Vogel wrote:
> On Tue, Aug 29, 2023 at 10:53:39PM -0400, gene heskett wrote:
> > And that is the problem, and why I read thru all those man ages trying to
> > find a way to make it log what it did. Sadly no.
> 
>   Install and configure file auditing on Debian:
> https://www.daemon.be/maarten/auditd.html
> 
>   Auditing can help you find anything trying to write to your sound device.
>   Look at these manpages:
> auditd.conf (5)
> audit.rules (7)
> audispd (8)
> ausearch (8)
> aureport (8)
> auditctl (8)
> augenrules (8)
> 
>   To find your sound cards and/or devices:
> https://wiki.debian.org/Sound
> https://wiki.debian.org/SoundCard
> https://wiki.debian.org/PulseAudio
> 
>   I don't have a Debian system to play with, but in the (good|bad) old
>   days, we had a /devices directory with all sorts of weirdness inside.
>   If you have one of those, try
> find /devices -print | grep sound
> 
>   That might point you to an actual device name.

As Gene has the habit of thoughtlessly pasting commands posted here,
it might be better instead to try:

  $ find /dev | grep snd
  /dev/snd
  /dev/snd/controlC0
  /dev/snd/hwC0D0
  /dev/snd/pcmC0D2c
  /dev/snd/pcmC0D2p
  /dev/snd/pcmC0D0c
  /dev/snd/pcmC0D0p
  /dev/snd/by-path
  /dev/snd/by-path/pci-:00:1b.0
  /dev/snd/by-path/pci-:02:00.1
  /dev/snd/controlC1
  /dev/snd/hwC1D0
  /dev/snd/pcmC1D3p
  /dev/snd/seq
  /dev/snd/timer
  $ 

Cheers,
David.

Re: door bell like sound effect

[Karl Vogel]

On Tue, Aug 29, 2023 at 10:53:39PM -0400, gene heskett wrote:
> And that is the problem, and why I read thru all those man ages trying to
> find a way to make it log what it did. Sadly no.

  Install and configure file auditing on Debian:
https://www.daemon.be/maarten/auditd.html

  Auditing can help you find anything trying to write to your sound device.
  Look at these manpages:
auditd.conf (5)
audit.rules (7)
audispd (8)
ausearch (8)
aureport (8)
auditctl (8)
augenrules (8)

  To find your sound cards and/or devices:
https://wiki.debian.org/Sound
https://wiki.debian.org/SoundCard
https://wiki.debian.org/PulseAudio

  I don't have a Debian system to play with, but in the (good|bad) old
  days, we had a /devices directory with all sorts of weirdness inside.
  If you have one of those, try
find /devices -print | grep sound

  That might point you to an actual device name.

-- 
Karl Vogel  I don't speak for anyone but myself.

Comment: One of my friends drank half a bottle of rum and refilled it
 with a bodily fluid of similar color.
Reply:   Your friend should see a doctor and drink more water.
   --seen on Reddit, 27 Aug 2023

Re: door bell like sound effect

[gene heskett]

On 8/29/23 14:54, gene heskett wrote:

On 8/29/23 12:50, zithro wrote:

On 29 Aug 2023 18:19, gene heskett wrote:

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:



Have you checked all the cron files and the systemd timers ?


cron yes, systemd timers no, don't know how.


man systemctl ; look for "timer" (in vi(m) use "/" to search) ?

$ systemctl list-timers



Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also 
have used xmms, audacity, VLC, mpv, etc.


tried aplay, got server dead response. htop cannot find aplay,

Its usually in the middle of the night, waking me up because it is as 
loud as the real door bell would be. Last Saturday was unusual as it 
sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting 
here. Most of the noises it makes are 30 db quieter.


?!
I think you didn't understand what I meant.
To play a sound, there needs to be an app launching it.
So I suggested than instead of "find"ing the sound itself, you try to 
"grep" the application/executable name.
Agreed this could be long, as you don't know where that sound is 
played from.


And that is the problem, and why I read thru all those man ages trying 
to find a way to make it log what it did. Sadly no.


Cheers, Gene Heskett.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[Max Nikulin]

On 30/08/2023 01:58, gene heskett wrote:

bash: pactl: command not found
gene@coyote:~$ sudo apt install pactl

...

E: Unable to locate package pactl

Next?


Either apt-file suggested earlier or if you are using it rarely and 
prefer to avoid downloading of file lists for all packages then


https://packages.debian.org/file:pactl


Thunderbird calendar, korganizer, alarm applets or applications may be 
suspected as well.

Those would all be under /home/me/.local? FWIW I am the only live user. 


At least thunderbird keeps its files in ~/.thunderbird by default. 
Perhaps KDE application might continue using legacy ~/.kde if the 
directory already contains their files. My idea is to check if you have 
accidentally scheduled events without waiting a next alarm.

Re: door bell like sound effect

[zithro]

On 29 Aug 2023 21:55, Greg Wooledge wrote:

On Tue, Aug 29, 2023 at 02:58:44PM -0400, gene heskett wrote:

E: Unable to locate package pactl


unicorn:~$ type pactl
pactl is /usr/bin/pactl
unicorn:~$ dpkg -S /usr/bin/pactl
pulseaudio-utils: /usr/bin/pactl



Or :

$ apt-file search pactl
[...]
pulseaudio-utils: /usr/bin/pactl
pulseaudio-utils: /usr/share/bash-completion/completions/pactl
pulseaudio-utils: /usr/share/man/man1/pactl.1.gz
[...]

It's useful when you don't have the full path of the file.
Downside, you need to install "apt-file" first.
Run "apt-file update" before using it, but iirc it warns you to do it if 
you forget.



--
++
zithro / Cyril

Re: door bell like sound effect

[Larry Martell]

On Tue, Aug 29, 2023 at 12:59 PM Greg Wooledge  wrote:
>
> On Tue, Aug 29, 2023 at 09:29:35AM -0700, Larry Martell wrote:
> > find . -regex '.*\.snd$' -print
>
> That is an incredibly silly way to write
>
> find . -name '*.snd' -print

Gene said that was finding many files that had snd in their name and
not just as the terminal extension. So I gave a command that would
only find files that ended with .snd.

> But the bigger issue is that audio files may have MANY different
> extensions, with .snd being only one of them.

Yes, I know that - I was showing an example using what was previously posted.

Re: door bell like sound effect

[Greg Wooledge]

On Tue, Aug 29, 2023 at 09:29:35AM -0700, Larry Martell wrote:
> find . -regex '.*\.snd$' -print

That is an incredibly silly way to write

find . -name '*.snd' -print

But the bigger issue is that audio files may have MANY different
extensions, with .snd being only one of them.

Re: door bell like sound effect

[Greg Wooledge]

On Tue, Aug 29, 2023 at 02:58:44PM -0400, gene heskett wrote:
> E: Unable to locate package pactl

unicorn:~$ type pactl
pactl is /usr/bin/pactl
unicorn:~$ dpkg -S /usr/bin/pactl
pulseaudio-utils: /usr/bin/pactl

Re: door bell like sound effect

[gene heskett]

On 8/29/23 14:48, gene heskett wrote:

On 8/29/23 12:50, Max Nikulin wrote:

On 29/08/2023 22:41, Curt wrote:


You'd think it'd be simpler to write a script that runs overnight
checking for active audio sources (using maybe 'pacmd list-sink-inputs'
or similar) and logging them to a file when detected.


Is it possible to increase verbosity of logs of some pulseaudio module?

An attempt to react to events:

pactl subscribe  | while read -r v ; do [[ "$v" == *client* ]] && 
continue ; date; echo "$v" ; pacmd list-sink-inputs ; done


gene@coyote:~$ pactl subscribe  | while read -r v ; do [[ "$v" == 
*client* ]] && continue ; date; echo "$v" ; pacmd list-sink-inputs ; done

bash: pactl: command not found
gene@coyote:~$ sudo apt install pactl
[sudo] password for gene:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package pactl

Next?

I would not be surprised if some web application tries to notify about 
e.g. birthdays or some other events. Unsure if it is possible to do 
from a service worker or the site must be opened in a tab. The audio 
file may exist in browser cache only this case.


Thunderbird calendar, korganizer, alarm applets or applications may be 
suspected as well.



Those would all be under /home/me/.local? FWIW I am the only live user.

.


Cheers, Gene Heskett.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/29/23 12:50, zithro wrote:

On 29 Aug 2023 18:19, gene heskett wrote:

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:



Have you checked all the cron files and the systemd timers ?


cron yes, systemd timers no, don't know how.


man systemctl ; look for "timer" (in vi(m) use "/" to search) ?

$ systemctl list-timers



Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also 
have used xmms, audacity, VLC, mpv, etc.


tried aplay, got server dead response. htop cannot find aplay,

Its usually in the middle of the night, waking me up because it is as 
loud as the real door bell would be. Last Saturday was unusual as it 
sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting 
here. Most of the noises it makes are 30 db quieter.


?!
I think you didn't understand what I meant.
To play a sound, there needs to be an app launching it.
So I suggested than instead of "find"ing the sound itself, you try to 
"grep" the application/executable name.
Agreed this could be long, as you don't know where that sound is played 
from.




Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/29/23 12:50, Max Nikulin wrote:

On 29/08/2023 22:41, Curt wrote:


You'd think it'd be simpler to write a script that runs overnight
checking for active audio sources (using maybe 'pacmd list-sink-inputs'
or similar) and logging them to a file when detected.


Is it possible to increase verbosity of logs of some pulseaudio module?

An attempt to react to events:

pactl subscribe  | while read -r v ; do [[ "$v" == *client* ]] && 
continue ; date; echo "$v" ; pacmd list-sink-inputs ; done


I would not be surprised if some web application tries to notify about 
e.g. birthdays or some other events. Unsure if it is possible to do from 
a service worker or the site must be opened in a tab. The audio file may 
exist in browser cache only this case.


Thunderbird calendar, korganizer, alarm applets or applications may be 
suspected as well.



Those would all be under /home/me/.local? FWIW I am the only live user.

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/29/23 12:46, debian-u...@howorth.org.uk wrote:

gene heskett  wrote:

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:

Greetings;

odd request:


Yeah, almost unreal ^^
   


Somewhere, for some unk reason, there is a sound file file that
plays at max volume, usually around 2 AM or slightly later, that
is very similar to the 40 yo doorbell in this house. A bing-bong
sound that differs from the real doorbell by maybe 5hz in pitch.
Wakes me up, spoiling a good nights sleep, maybe a dozen times a
year an apparently random dates.


Have you checked all the cron files and the systemd timers ?


cron yes, systemd timers no, don't know how.


To aid in finding it, what extension might that file be carrying
to indicate its a .snd fle, which according to grep on ls -lR's
output, does not exist in the thousands of files under hundreds of
random names.


The keyword above is extension, the find/grep tools seem to find a
match anywhere in a filename. getting a thousand hits, none of which
are the last 4 chars of a name.


RTFM? Or Larry's email :) And look for all the 'extensions' people have
mentioned.
  

What if you didn't use an extension when you created the audio
file ?

This file that sounds exactly like my doorbell has existed on my
24/7/365.25 on main system for at least 20 years. I'd like to A.
find it, B. find what condition uses it, fix the condition, or
even delete it.


Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which
application. With ALSA, you could have used "aplay FILE.wav", but
you could also have used xmms, audacity, VLC, mpv, etc.


Its usually in the middle of the night, waking me up because it is as
loud as the real door bell would be. Last Saturday was unusual as it
sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting
here. Most of the noises it makes are 30 db quieter.


So don't try to find it when it happens. Just make a note of the exact
time and look in the morning after breakfast and coffee!

.
Now there's an idea. With macular degeneration setting in, night time is 
not an ideal time to search a hi res screen for me.


Thanks

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/29/23 12:30, Larry Martell wrote:

On Tue, Aug 29, 2023 at 9:19 AM gene heskett  wrote:


On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:

To aid in finding it, what extension might that file be carrying to
indicate its a .snd fle, which according to grep on ls -lR's output,
does not exist in the thousands of files under hundreds of random names.


The keyword above is extension, the find/grep tools seem to find a match
anywhere in a filename. getting a thousand hits, none of which are the
last 4 chars of a name.


find . -regex '.*\.snd$' -print
.
which returns nothing unless I start it at / then I get about a dozen no 
permissions because I don't allow root and ssh in the same building. 
All my other machines are mounted as me using sshfs.

And does not find anything when invoked in a suspected path.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/29/23 07:22, Greg Wooledge wrote:

On Tue, Aug 29, 2023 at 11:10:17AM +0200, Michael wrote:

On Tuesday, 29 August 2023 03:56:55 CEST, Greg Wooledge wrote:


The problem is, most Debian systems are set up to mount the core file
systems with "relatime".  This means you don't have a record of the
last time each file was accessed, so you can't ask the computer which
files were most recently opened.


hm...

i was curious about that and read the man page for 'mount(8)', in section
FILESYSTEM-INDEPENDENT MOUNT OPTIONS i found the following:

relatime
  Update inode access times relative to modify or change time.
  Access time is only updated if the previous access time was
  earlier than the current modify or change time. [...]

so my understanding is, that access time is indeed updated if 'relatime' is
used as a mount option. to prevent updating access times 'noatime' should be
used.


It's changed *only* under the specific circumstance where the file has
been modified since it was last read.  If the file hasn't been written to
(or metadata changed), atime isn't updated.

So, imagine there's a doorbell.au file somewhere in Gene's file system,
and that this file has been played, once in a while, for several years.
It hasn't been *modified* in all that time.  It's a very static file.
But every once in a while, something opens it and reads it.

In that situation, the mtime on the file is going to be "whenever it
was created" (close enough for this discussion), and the atime is going
to be "whenever it was first played", perhaps 5 or 10 or 20 years ago.
Even though it was just played a few days ago.

Long story short, sorting files by atime isn't going to reveal it.
Unless of course Gene's file systems are mounted with an overriding
option, and he's getting full historic atime behavior.


That would be nice, but I expect it would also be quite speed damaging...

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/28/23 23:44, Greg Wooledge wrote:

On Mon, Aug 28, 2023 at 11:32:25PM -0400, songbird wrote:

Greg Wooledge wrote:

The problem is, most Debian systems are set up to mount the core file
systems with "relatime".  This means you don't have a record of the
last time each file was accessed, so you can't ask the computer which
files were most recently opened.


   i don't have that one set at all in my fstab.


It's a default option.  It doesn't have to be visible in fstab.
Look at the *output of mount* instead.

unicorn:~$ cat /etc/fstab
[...]
# / was on /dev/sda7 during installation
UUID=c4691ccb-2090-491e-8e82-d7cc822db04a /   ext4
errors=remount-ro 0   1
[...]

unicorn:~$ mount | grep 'on / '
/dev/sda7 on / type ext4 (rw,relatime,errors=remount-ro)

.

And that's pretty universal here.  My listing is considerably longer.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/28/23 21:32, songbird wrote:

Cindy Sue Causey wrote:
...

That triggered yet another thought: What about some kind of a file
search that narrows down "Last Accessed" data for all the various
sound file types?


   most recently accessed files could be located via find
command.  i assumed Gene would know how to do that...



Wrong.


Personal experience is that manually viewing e.g. /usr/share isn't
100% perfect. It's been a couple years, but I've also seen sound files
stored more locally within some given package's own parent/child file
hierarchy. That helps make our favorite file search programs
priceless.

Cindy :)


   if the system can't tell you what's been recently
accessed and you are on-line then you need to go
off-line until you've figured it out.

   if Gene leaves his network up and accessible to
others all night when he's sleeping then perhaps he
needs to bring it down and that will slay the
gremlins...


   songbird

.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[zithro]

On 29 Aug 2023 18:35, gene heskett wrote:

I have no known enemies left, I've outlived them all. And there is a PIR 
facing out that see's a 34 yo pin oak moving in the wind many times a day.


What about their families ? ^^

Joke aside, trees don't produce heat themselves (AFAIK ...), so the only 
way is to reflect the IR from the sun.

Or there is some animal walking the tree.

So your PIR is either broken or way too sensitive.
Some provide a sensitivity setting via a potentiometer, but YMMV.
Usually, sensitivity is correlated to the range (ie. meters) of the IR 
sensor.



--
++
zithro / Cyril

Re: door bell like sound effect

[zithro]

On 29 Aug 2023 18:19, gene heskett wrote:

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:



Have you checked all the cron files and the systemd timers ?


cron yes, systemd timers no, don't know how.


man systemctl ; look for "timer" (in vi(m) use "/" to search) ?

$ systemctl list-timers



Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also 
have used xmms, audacity, VLC, mpv, etc.


Its usually in the middle of the night, waking me up because it is as 
loud as the real door bell would be. Last Saturday was unusual as it 
sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting 
here. Most of the noises it makes are 30 db quieter.


?!
I think you didn't understand what I meant.
To play a sound, there needs to be an app launching it.
So I suggested than instead of "find"ing the sound itself, you try to 
"grep" the application/executable name.
Agreed this could be long, as you don't know where that sound is played 
from.


--
++
zithro / Cyril

Re: door bell like sound effect

[Max Nikulin]

On 29/08/2023 22:41, Curt wrote:


You'd think it'd be simpler to write a script that runs overnight
checking for active audio sources (using maybe 'pacmd list-sink-inputs'
or similar) and logging them to a file when detected.


Is it possible to increase verbosity of logs of some pulseaudio module?

An attempt to react to events:

pactl subscribe  | while read -r v ; do [[ "$v" == *client* ]] && 
continue ; date; echo "$v" ; pacmd list-sink-inputs ; done


I would not be surprised if some web application tries to notify about 
e.g. birthdays or some other events. Unsure if it is possible to do from 
a service worker or the site must be opened in a tab. The audio file may 
exist in browser cache only this case.


Thunderbird calendar, korganizer, alarm applets or applications may be 
suspected as well.

Re: door bell like sound effect

[debian-user]

gene heskett  wrote:
> On 8/28/23 12:20, zithro wrote:
> > On 28 Aug 2023 09:29, gene heskett wrote:  
> >> Greetings;
> >>
> >> odd request:  
> > 
> > Yeah, almost unreal ^^
> >   
> >>
> >> Somewhere, for some unk reason, there is a sound file file that
> >> plays at max volume, usually around 2 AM or slightly later, that
> >> is very similar to the 40 yo doorbell in this house. A bing-bong
> >> sound that differs from the real doorbell by maybe 5hz in pitch.
> >> Wakes me up, spoiling a good nights sleep, maybe a dozen times a
> >> year an apparently random dates.  
> > 
> > Have you checked all the cron files and the systemd timers ?  
> 
> cron yes, systemd timers no, don't know how.
> 
> >> To aid in finding it, what extension might that file be carrying
> >> to indicate its a .snd fle, which according to grep on ls -lR's
> >> output, does not exist in the thousands of files under hundreds of
> >> random names.  
> 
> The keyword above is extension, the find/grep tools seem to find a
> match anywhere in a filename. getting a thousand hits, none of which
> are the last 4 chars of a name.

RTFM? Or Larry's email :) And look for all the 'extensions' people have
mentioned.
 
> > What if you didn't use an extension when you created the audio
> > file ? 
> >> This file that sounds exactly like my doorbell has existed on my 
> >> 24/7/365.25 on main system for at least 20 years. I'd like to A.
> >> find it, B. find what condition uses it, fix the condition, or
> >> even delete it.  
> > 
> > Maybe find the script(s) where you use this sound ?
> > I mean to find HOW you played this sound, ie. with which
> > application. With ALSA, you could have used "aplay FILE.wav", but
> > you could also have used xmms, audacity, VLC, mpv, etc.  
> 
> Its usually in the middle of the night, waking me up because it is as 
> loud as the real door bell would be. Last Saturday was unusual as it 
> sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting 
> here. Most of the noises it makes are 30 db quieter.

So don't try to find it when it happens. Just make a note of the exact
time and look in the morning after breakfast and coffee!

Re: door bell like sound effect

[gene heskett]

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:

Greetings;

odd request:


Yeah, almost unreal ^^



Somewhere, for some unk reason, there is a sound file file that plays 
at max volume, usually around 2 AM or slightly later, that is very 
similar to the 40 yo doorbell in this house. A bing-bong sound that 
differs from the real doorbell by maybe 5hz in pitch. Wakes me up, 
spoiling a good nights sleep, maybe a dozen times a year an apparently 
random dates.


Have you checked all the cron files and the systemd timers ?

To aid in finding it, what extension might that file be carrying to 
indicate its a .snd fle, which according to grep on ls -lR's output, 
does not exist in the thousands of files under hundreds of random names.


What if you didn't use an extension when you created the audio file ?

This file that sounds exactly like my doorbell has existed on my 
24/7/365.25 on main system for at least 20 years. I'd like to A. find 
it, B. find what condition uses it, fix the condition, or even delete it.


Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also have 
used xmms, audacity, VLC, mpv, etc.


How can I best do that? updatedb, followed by locate door or locate 
bell reports nothing.


locate bing ; locate bong ; locate gong ? You wrote the sound was like 
"bing-bong" ^^
In this case, I would recommend to use "find" as root, rather than 
"locate", just to prevent the fact the file could not be indexed by 
updatedb for whatever reason, and as root in case you put the script 
and/or sound in a folder only accessible by root.
PS: last I used locate was on Slackware 13.37, so others may point 
errors in that thinking.


There are now 2 different PIR based devices watching that doorbell 
button, which trigger on the neighbors cat walking by but remain 
silent when this sound jacks me up in the middle of the night.


If you have ennemies, they can use a long stick to ring the bell to 
evade PIR detection ^^


I have no known enemies left, I've outlived them all. And there is a PIR 
facing out that see's a 34 yo pin oak moving in the wind many times a day.


Any help in finding this will be hugely appreciated.

Cheers, Gene Heskett.




Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[Larry Martell]

On Tue, Aug 29, 2023 at 9:19 AM gene heskett  wrote:
>
> On 8/28/23 12:20, zithro wrote:
> > On 28 Aug 2023 09:29, gene heskett wrote:
> >> To aid in finding it, what extension might that file be carrying to
> >> indicate its a .snd fle, which according to grep on ls -lR's output,
> >> does not exist in the thousands of files under hundreds of random names.
>
> The keyword above is extension, the find/grep tools seem to find a match
> anywhere in a filename. getting a thousand hits, none of which are the
> last 4 chars of a name.

find . -regex '.*\.snd$' -print

Re: door bell like sound effect

[gene heskett]

On 8/28/23 12:20, zithro wrote:

On 28 Aug 2023 09:29, gene heskett wrote:

Greetings;

odd request:


Yeah, almost unreal ^^



Somewhere, for some unk reason, there is a sound file file that plays 
at max volume, usually around 2 AM or slightly later, that is very 
similar to the 40 yo doorbell in this house. A bing-bong sound that 
differs from the real doorbell by maybe 5hz in pitch. Wakes me up, 
spoiling a good nights sleep, maybe a dozen times a year an apparently 
random dates.


Have you checked all the cron files and the systemd timers ?


cron yes, systemd timers no, don't know how.

To aid in finding it, what extension might that file be carrying to 
indicate its a .snd fle, which according to grep on ls -lR's output, 
does not exist in the thousands of files under hundreds of random names.


The keyword above is extension, the find/grep tools seem to find a match 
anywhere in a filename. getting a thousand hits, none of which are the 
last 4 chars of a name.



What if you didn't use an extension when you created the audio file ?

This file that sounds exactly like my doorbell has existed on my 
24/7/365.25 on main system for at least 20 years. I'd like to A. find 
it, B. find what condition uses it, fix the condition, or even delete it.


Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also have 
used xmms, audacity, VLC, mpv, etc.


Its usually in the middle of the night, waking me up because it is as 
loud as the real door bell would be. Last Saturday was unusual as it 
sounded off at 2:06 and 6:58 EDT.  Never occurred while I'm sitting 
here. Most of the noises it makes are 30 db quieter.




How can I best do that? updatedb, followed by locate door or locate 
bell reports nothing.


locate bing ; locate bong ; locate gong ? You wrote the sound was like 
"bing-bong" ^^
In this case, I would recommend to use "find" as root, rather than 
"locate", just to prevent the fact the file could not be indexed by 
updatedb for whatever reason, and as root in case you put the script 
and/or sound in a folder only accessible by root.
PS: last I used locate was on Slackware 13.37, so others may point 
errors in that thinking.


There are now 2 different PIR based devices watching that doorbell 
button, which trigger on the neighbors cat walking by but remain 
silent when this sound jacks me up in the middle of the night.


If you have ennemies, they can use a long stick to ring the bell to 
evade PIR detection ^^




Any help in finding this will be hugely appreciated.

Cheers, Gene Heskett.




Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[gene heskett]

On 8/28/23 05:26, Michel Verdier wrote:

On 2023-08-28, gene heskett wrote:


Any help in finding this will be hugely appreciated.


As you are awake and know the time of ringing do you check the logs
around that time ?

.
I checked them a couple minutes after the last time but nothing stood 
out as a likely suspect. Mostly cups related traffic. It has to update 
the list of available printers every 5 or so minutes.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

Re: door bell like sound effect

[Curt]

On 2023-08-29, Greg Wooledge  wrote:
>
> There's still going to be a whole lotta searching through the haystack
> to find the needle.  Obviously, knowing the approximate date and time
> the file was last read would be of tremendous help, as you can zoom in
> on that part of the results.
>
>

You'd think it'd be simpler to write a script that runs overnight
checking for active audio sources (using maybe 'pacmd list-sink-inputs'
or similar) and logging them to a file when detected.

Easier said than done, I guess!

Re: door bell like sound effect

[David Wright]

On Tue 29 Aug 2023 at 08:37:00 (-0400), Greg Wooledge wrote:
> On Tue, Aug 29, 2023 at 07:46:16AM -0400, songbird wrote:
> >   ok, i understand that but my command 
> > 
> > $ alias aq='find . -amin -30'
> > $ aq 
> > 
> > works as it should.
> 
> Oh.  I guess I should have read the *entire* section of the man page.
> 
>relatime
>[...]
>Since Linux 2.6.30, the kernel defaults to the behavior provided by
>this option (unless noatime was specified), and the strictatime
>option is required to obtain traditional semantics. In addition,
>since Linux 2.6.30, the file’s last access time is always updated
>if it is more than 1 day old.
> 
> It's that last sentence that changes everything.  So then, I guess in
> theory Gene *could* search for all of the most recently used files on
> his system, and have a snowball's chance in hell of finding the doorbell
> audio file that way.

IIRC, the d-i by default adds noatime to entries in /etc/fstab for SSDs,
which I thought Gene had now converted to. However, Gene's entries may
have been inherited from older installations, so all this might work.

> Actually doing that could be trickier than you might guess.  If we
> limit ourselves to searching one file system (or partial file system,
> e.g. the /usr directory) at a time, and therefore don't need to supply
> exclude patterns, here's a bash function that might be helpful:
> 
> rlartu() {
> local day time path
> find "${1:-.}" -type f -printf '%A@/%AY-%Am-%Ad/%AT/%p\0' | sort -zn |
> while IFS=/ read -rd '' _ day time path; do
> printf '%s %s %s\n' "$day" "${time%.*}" "$path"
> done
> }
> 
> I would suggest using this in /home and /usr first, unless Gene can
> think of more appropriate starting points.
> 
> There's still going to be a whole lotta searching through the haystack
> to find the needle.  Obviously, knowing the approximate date and time
> the file was last read would be of tremendous help, as you can zoom in
> on that part of the results.

Cheers,
David.

Re: door bell like sound effect

[Greg Wooledge]

On Tue, Aug 29, 2023 at 07:46:16AM -0400, songbird wrote:
>   ok, i understand that but my command 
> 
> $ alias aq='find . -amin -30'
> $ aq 
> 
> works as it should.

Oh.  I guess I should have read the *entire* section of the man page.

   relatime
   [...]
   Since Linux 2.6.30, the kernel defaults to the behavior provided by
   this option (unless noatime was specified), and the strictatime
   option is required to obtain traditional semantics. In addition,
   since Linux 2.6.30, the file’s last access time is always updated
   if it is more than 1 day old.

It's that last sentence that changes everything.  So then, I guess in
theory Gene *could* search for all of the most recently used files on
his system, and have a snowball's chance in hell of finding the doorbell
audio file that way.

Actually doing that could be trickier than you might guess.  If we
limit ourselves to searching one file system (or partial file system,
e.g. the /usr directory) at a time, and therefore don't need to supply
exclude patterns, here's a bash function that might be helpful:

rlartu() {
local day time path
find "${1:-.}" -type f -printf '%A@/%AY-%Am-%Ad/%AT/%p\0' | sort -zn |
while IFS=/ read -rd '' _ day time path; do
printf '%s %s %s\n' "$day" "${time%.*}" "$path"
done
}

I would suggest using this in /home and /usr first, unless Gene can
think of more appropriate starting points.

There's still going to be a whole lotta searching through the haystack
to find the needle.  Obviously, knowing the approximate date and time
the file was last read would be of tremendous help, as you can zoom in
on that part of the results.

Re: door bell like sound effect

[Michel Verdier]

On 2023-08-29, Greg Wooledge wrote:

> It's changed *only* under the specific circumstance where the file has
> been modified since it was last read.  If the file hasn't been written to
> (or metadata changed), atime isn't updated.

Michael is right : atime is modified if it's "ealier" so you always get
the latest access time as modify and create obviously need access.
Here I set noatime to disable access time and also lazytime to speed
writes.

Re: door bell like sound effect

[songbird]

Greg Wooledge wrote:
> On Mon, Aug 28, 2023 at 11:32:25PM -0400, songbird wrote:
>> Greg Wooledge wrote:
>> > The problem is, most Debian systems are set up to mount the core file
>> > systems with "relatime".  This means you don't have a record of the
>> > last time each file was accessed, so you can't ask the computer which
>> > files were most recently opened.
>> 
>>   i don't have that one set at all in my fstab.
>
> It's a default option.  It doesn't have to be visible in fstab.
> Look at the *output of mount* instead.
>
> unicorn:~$ cat /etc/fstab
> [...]
> # / was on /dev/sda7 during installation
> UUID=c4691ccb-2090-491e-8e82-d7cc822db04a /   ext4
> errors=remount-ro 0   1
> [...]
>
> unicorn:~$ mount | grep 'on / '
> /dev/sda7 on / type ext4 (rw,relatime,errors=remount-ro)

  ok, i understand that but my command 

$ alias aq='find . -amin -30'
$ aq 

works as it should.


  songbird

Re: door bell like sound effect

[Greg Wooledge]

On Tue, Aug 29, 2023 at 11:10:17AM +0200, Michael wrote:
> On Tuesday, 29 August 2023 03:56:55 CEST, Greg Wooledge wrote:
> 
> > The problem is, most Debian systems are set up to mount the core file
> > systems with "relatime".  This means you don't have a record of the
> > last time each file was accessed, so you can't ask the computer which
> > files were most recently opened.
> 
> hm...
> 
> i was curious about that and read the man page for 'mount(8)', in section
> FILESYSTEM-INDEPENDENT MOUNT OPTIONS i found the following:
> 
> relatime
>  Update inode access times relative to modify or change time.
>  Access time is only updated if the previous access time was
>  earlier than the current modify or change time. [...]
> 
> so my understanding is, that access time is indeed updated if 'relatime' is
> used as a mount option. to prevent updating access times 'noatime' should be
> used.

It's changed *only* under the specific circumstance where the file has
been modified since it was last read.  If the file hasn't been written to
(or metadata changed), atime isn't updated.

So, imagine there's a doorbell.au file somewhere in Gene's file system,
and that this file has been played, once in a while, for several years.
It hasn't been *modified* in all that time.  It's a very static file.
But every once in a while, something opens it and reads it.

In that situation, the mtime on the file is going to be "whenever it
was created" (close enough for this discussion), and the atime is going
to be "whenever it was first played", perhaps 5 or 10 or 20 years ago.
Even though it was just played a few days ago.

Long story short, sorting files by atime isn't going to reveal it.
Unless of course Gene's file systems are mounted with an overriding
option, and he's getting full historic atime behavior.

Re: door bell like sound effect

[Michael]

On Tuesday, 29 August 2023 03:56:55 CEST, Greg Wooledge wrote:


The problem is, most Debian systems are set up to mount the core file
systems with "relatime".  This means you don't have a record of the
last time each file was accessed, so you can't ask the computer which
files were most recently opened.


hm...

i was curious about that and read the man page for 'mount(8)', in section 
FILESYSTEM-INDEPENDENT MOUNT OPTIONS i found the following:


relatime
 Update inode access times relative to modify or change time.
 Access time is only updated if the previous access time was
 earlier than the current modify or change time. [...]

so my understanding is, that access time is indeed updated if 'relatime' is 
used as a mount option. to prevent updating access times 'noatime' should 
be used.


i am happy to be corrected if i should be wrong...

Re: door bell like sound effect

[Greg Wooledge]

On Mon, Aug 28, 2023 at 11:32:25PM -0400, songbird wrote:
> Greg Wooledge wrote:
> > The problem is, most Debian systems are set up to mount the core file
> > systems with "relatime".  This means you don't have a record of the
> > last time each file was accessed, so you can't ask the computer which
> > files were most recently opened.
> 
>   i don't have that one set at all in my fstab.

It's a default option.  It doesn't have to be visible in fstab.
Look at the *output of mount* instead.

unicorn:~$ cat /etc/fstab
[...]
# / was on /dev/sda7 during installation
UUID=c4691ccb-2090-491e-8e82-d7cc822db04a /   ext4
errors=remount-ro 0   1
[...]

unicorn:~$ mount | grep 'on / '
/dev/sda7 on / type ext4 (rw,relatime,errors=remount-ro)

Re: door bell like sound effect

[songbird]

Greg Wooledge wrote:
> On Mon, Aug 28, 2023 at 09:21:11PM -0400, songbird wrote:
>> Cindy Sue Causey wrote:
>> ...
>> > That triggered yet another thought: What about some kind of a file
>> > search that narrows down "Last Accessed" data for all the various
>> > sound file types?
>> 
>>   most recently accessed files could be located via find
>> command.  i assumed Gene would know how to do that...
>
> The problem is, most Debian systems are set up to mount the core file
> systems with "relatime".  This means you don't have a record of the
> last time each file was accessed, so you can't ask the computer which
> files were most recently opened.

  i don't have that one set at all in my fstab.


> At that point, Gene's knowledge (or lack thereof) isn't relevant.

  can't say...


  songbird

Re: door bell like sound effect

[Greg Wooledge]

On Tue, Aug 29, 2023 at 04:02:03AM +0100, mick.crane wrote:
> On 2023-08-28 08:29, gene heskett wrote:
> > Somewhere, for some unk reason, there is a sound file file that plays
> > at max volume, usually around 2 AM or slightly later, that is very
> > similar to the 40 yo doorbell in this house. A bing-bong sound that
> > differs from the real doorbell by maybe 5hz in pitch. Wakes me up,
> > spoiling a good nights sleep, maybe a dozen times a year an apparently
> > random dates.
> > 
> As this happens when you are asleep it could be in your head.
> You'd need to have a sound activated recorder on for a year to find out.

It would be easier to set up cron jobs that mute the outgoing audio
channels at bed time, and unmute them at wake-up time.

Of course, figuring out which of your desktop environment's features
is doing this, and stopping it, would be greatly preferred.  And let's
face it, this is almost 100% guaranteed to be some kind of DE alarm
clock feature or something similar.

I'm inclined to think that it actually happens *every* night, but it
only wakes him up a few times a year.  But that's a guess.

Re: door bell like sound effect

[mick.crane]

On 2023-08-28 08:29, gene heskett wrote:

Greetings;

odd request:

Somewhere, for some unk reason, there is a sound file file that plays
at max volume, usually around 2 AM or slightly later, that is very
similar to the 40 yo doorbell in this house. A bing-bong sound that
differs from the real doorbell by maybe 5hz in pitch. Wakes me up,
spoiling a good nights sleep, maybe a dozen times a year an apparently
random dates.


As this happens when you are asleep it could be in your head.
You'd need to have a sound activated recorder on for a year to find out.

mick

Re: door bell like sound effect

[Greg Wooledge]

On Mon, Aug 28, 2023 at 09:21:11PM -0400, songbird wrote:
> Cindy Sue Causey wrote:
> ...
> > That triggered yet another thought: What about some kind of a file
> > search that narrows down "Last Accessed" data for all the various
> > sound file types?
> 
>   most recently accessed files could be located via find
> command.  i assumed Gene would know how to do that...

The problem is, most Debian systems are set up to mount the core file
systems with "relatime".  This means you don't have a record of the
last time each file was accessed, so you can't ask the computer which
files were most recently opened.

At that point, Gene's knowledge (or lack thereof) isn't relevant.

Re: door bell like sound effect

[songbird]

Cindy Sue Causey wrote:
...
> That triggered yet another thought: What about some kind of a file
> search that narrows down "Last Accessed" data for all the various
> sound file types?

  most recently accessed files could be located via find
command.  i assumed Gene would know how to do that...


> Personal experience is that manually viewing e.g. /usr/share isn't
> 100% perfect. It's been a couple years, but I've also seen sound files
> stored more locally within some given package's own parent/child file
> hierarchy. That helps make our favorite file search programs
> priceless.
>
> Cindy :)

  if the system can't tell you what's been recently 
accessed and you are on-line then you need to go
off-line until you've figured it out.

  if Gene leaves his network up and accessible to
others all night when he's sleeping then perhaps he
needs to bring it down and that will slay the 
gremlins...


  songbird

Re: door bell like sound effect

[fxkl47BF]

On Mon, 28 Aug 2023, Cindy Sue Causey wrote:

> On 8/28/23, songbird  wrote:
>> gene heskett wrote:
>>> Greetings;
>>>
>>> odd request:
>>>
>>> Somewhere, for some unk reason, there is a sound file file that plays at
>>> max volume, usually around 2 AM or slightly later, that is very similar
>>> to the 40 yo doorbell in this house. A bing-bong sound that differs from
>>> the real doorbell by maybe 5hz in pitch. Wakes me up, spoiling a good
>>> nights sleep, maybe a dozen times a year an apparently random dates.

have you checked your browser history
in my house gremlins love surf in those early hours :)

Re: door bell like sound effect

[Cindy Sue Causey]

On 8/28/23, songbird  wrote:
> gene heskett wrote:
>> Greetings;
>>
>> odd request:
>>
>> Somewhere, for some unk reason, there is a sound file file that plays at
>> max volume, usually around 2 AM or slightly later, that is very similar
>> to the 40 yo doorbell in this house. A bing-bong sound that differs from
>> the real doorbell by maybe 5hz in pitch. Wakes me up, spoiling a good
>> nights sleep, maybe a dozen times a year an apparently random dates.


>   perhaps a desktop sound?  i hate noises so i turn them
> off.
>
>   see if you have any enabled and if so check them all to see
> what they sound like.

That's a good one. It triggered the thought that pavucontrol(-qt)
sometimes will rat out what is playing any given sound. I see it most
often with browser tabs. Pavucontrol will name the title of the tab
that's presenting sound.

Just tried pavucontrol-qt for alarm-clock-applet, too. It says,"Alarm
Clock : Playback Stream."


>   if a file does not have an extension you can still use the
> file command to see if it can figure out what it is.


I just tried a "locate" search for "bell" and "door" on my setup.
There were "a few" files returned, but they were visibly searchable
fairly quickly.

That triggered yet another thought: What about some kind of a file
search that narrows down "Last Accessed" data for all the various
sound file types?

Personal experience is that manually viewing e.g. /usr/share isn't
100% perfect. It's been a couple years, but I've also seen sound files
stored more locally within some given package's own parent/child file
hierarchy. That helps make our favorite file search programs
priceless.

Cindy :)
-- 
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: door bell like sound effect

[songbird]

gene heskett wrote:
> Greetings;
>
> odd request:
>
> Somewhere, for some unk reason, there is a sound file file that plays at 
> max volume, usually around 2 AM or slightly later, that is very similar 
> to the 40 yo doorbell in this house. A bing-bong sound that differs from 
> the real doorbell by maybe 5hz in pitch. Wakes me up, spoiling a good 
> nights sleep, maybe a dozen times a year an apparently random dates.
>
> To aid in finding it, what extension might that file be carrying to 
> indicate its a .snd fle, which according to grep on ls -lR's output, 
> does not exist in the thousands of files under hundreds of random names.
>
> This file that sounds exactly like my doorbell has existed on my 
> 24/7/365.25 on main system for at least 20 years. I'd like to A. find 
> it, B. find what condition uses it, fix the condition, or even delete it.
>
> How can I best do that? updatedb, followed by locate door or locate bell 
> reports nothing.
>
> There are now 2 different PIR based devices watching that doorbell 
> button, which trigger on the neighbors cat walking by but remain silent 
> when this sound jacks me up in the middle of the night.
>
> Any help in finding this will be hugely appreciated.

  perhaps a desktop sound?  i hate noises so i turn them
off.

  see if you have any enabled and if so check them all to see 
what they sound like.

  if a file does not have an extension you can still use the
file command to see if it can figure out what it is.


  good luck,


  songbird

Re: door bell like sound effect

[zithro]

On 28 Aug 2023 09:29, gene heskett wrote:

Greetings;

odd request:


Yeah, almost unreal ^^



Somewhere, for some unk reason, there is a sound file file that plays at 
max volume, usually around 2 AM or slightly later, that is very similar 
to the 40 yo doorbell in this house. A bing-bong sound that differs from 
the real doorbell by maybe 5hz in pitch. Wakes me up, spoiling a good 
nights sleep, maybe a dozen times a year an apparently random dates.


Have you checked all the cron files and the systemd timers ?

To aid in finding it, what extension might that file be carrying to 
indicate its a .snd fle, which according to grep on ls -lR's output, 
does not exist in the thousands of files under hundreds of random names.


What if you didn't use an extension when you created the audio file ?

This file that sounds exactly like my doorbell has existed on my 
24/7/365.25 on main system for at least 20 years. I'd like to A. find 
it, B. find what condition uses it, fix the condition, or even delete it.


Maybe find the script(s) where you use this sound ?
I mean to find HOW you played this sound, ie. with which application.
With ALSA, you could have used "aplay FILE.wav", but you could also have 
used xmms, audacity, VLC, mpv, etc.


How can I best do that? updatedb, followed by locate door or locate bell 
reports nothing.


locate bing ; locate bong ; locate gong ? You wrote the sound was like 
"bing-bong" ^^
In this case, I would recommend to use "find" as root, rather than 
"locate", just to prevent the fact the file could not be indexed by 
updatedb for whatever reason, and as root in case you put the script 
and/or sound in a folder only accessible by root.
PS: last I used locate was on Slackware 13.37, so others may point 
errors in that thinking.


There are now 2 different PIR based devices watching that doorbell 
button, which trigger on the neighbors cat walking by but remain silent 
when this sound jacks me up in the middle of the night.


If you have ennemies, they can use a long stick to ring the bell to 
evade PIR detection ^^




Any help in finding this will be hugely appreciated.

Cheers, Gene Heskett.


--
++
zithro / Cyril

Re: door bell like sound effect

[ghe2001]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256







--- Original Message ---
On Monday, August 28th, 2023 at 1:47 AM, jeremy ardley 
 wrote:


> On 28/8/23 15:29, gene heskett wrote:
> 
> > what extension might that file be carrying to indicate its a .snd fle
> 
> 
> Try
> 
> 
> .wav

I use .flac a lot.

> .mp3
> 
...

--
Glenn English

-BEGIN PGP SIGNATURE-
Version: ProtonMail

wsBzBAEBCAAnBYJk7L5UCZCf14YxgqyMMhYhBCyicw9CUnAlY0ANl5/XhjGC
rIwyAABmDAgAucbolCPMqKH9qDMeXjf3mgx+t7O3ytzgR0YrXfRJRdQpfzdM
xVjpEiV5++F1rjYQZlJNiVFs88y/k1LM4ZUWsoyhNjAiUl6E3VICeTmSbrnn
33N9SZlslcJMyMqc4S9Zg8rjPJUhmTlc425QXt2fi1E/WXQDYiW1SOwUbQLX
HUY5Xsx+3jaWJeYATqHNJwuJxKKltbT1Wvu8Nm9UOAiymnefgO8si1BDVLy4
PoXz2RqAp0D8pmIjxQFnUltVWDObwBSvpP5EUB8AsXdpebh1bcOIlHkEbH2C
lo/hg3vvnjgyM/vEE3d38sJqoc6VZiL2AVtW4IR3uZl3agvzx98RCg==
=MhI7
-END PGP SIGNATURE-

Re: door bell like sound effect

[Michel Verdier]

On 2023-08-28, gene heskett wrote:

> Any help in finding this will be hugely appreciated.

As you are awake and know the time of ringing do you check the logs
around that time ?

Re: door bell like sound effect

[jeremy ardley]

On 28/8/23 15:29, gene heskett wrote:

what extension might that file be carrying to indicate its a .snd fle


Try


.wav

.mp3

.aac

.oga

 .m4a

 .ogg

.m4b

 .opus

 .ra

 .rm

.mid

 .midi

 .ac3

 .dts