David Wright wrote:
> FYI:
>
> I installed iwatch, and that immediately generated two messages from
> /etc/.etckeeper. Then I upgraded:
>
> apt apt-doc apt-utils bind9-host curl dnsutils exim4
> exim4-base exim4-config exim4-daemon-light
> firefox-esr firefox-esr-l10n-en-gb gstreamer1.0-gl
>
Jonathan Dowland wrote:
> On Wed, May 05, 2021 at 03:51:16PM +0200, Emanuel Berg wrote:
>
>> I learned something as well, how to delete mails. First see
>> how many mails there are, say there are 756, then type
>> t 1-756 RET and then hold down q :)
>
> That's a slow way. "T iwatch ; d" or "T ~b
On Wed 05 May 2021 at 07:26:34 (-0400), Greg Wooledge wrote:
> On Tue, May 04, 2021 at 09:32:49PM -0500, David Wright wrote:
> > It looks reasonable for determining whether your system files are
> > being interfered with. But you just showed one example from the
> > log, which was for the
On Wed, May 05, 2021 at 03:51:16PM +0200, Emanuel Berg wrote:
I learned something as well, how to delete mails. First see
how many mails there are, say there are 756, then type t 1-756
RET and then hold down q :)
That's a slow way. "T iwatch ; d" or "T ~b iwatch ; d" would be faster
(using ;
On Fri, May 07, 2021 at 09:46:53AM +0100, Tixy wrote:
> On Fri, 2021-05-07 at 09:39 +0200, to...@tuxteam.de wrote:
> > - 1 I don't understand (who is .pwd.lock [...])
> I thought that was explained on this list a few days ago [...]
Oh, thanks. Must have missed that part :)
Cheers
- t
On Fri, 2021-05-07 at 09:39 +0200, to...@tuxteam.de wrote:
> - 1 I don't understand (who is .pwd.lock and what is she
> doing in my /etc? [1]).
I thought that was explained on this list a few days ago (and 17 years
ago! [2]). The file is used by lckpwdf() function [3][4] which is used
to
On Thu, May 06, 2021 at 11:21:14PM -0500, David Wright wrote:
[...]
> Well, here are the files on my system:
>
> # find /etc -type f -name '.*' -ls | sort -k 11
> -rwx-- 84357 May 6 08:25 /etc/.etckeeper
> -rw--- 932 Apr 3 2020 /etc/.gitignore
> -rw-r--r-- 0 Apr 3 2020
On Thu 06 May 2021 at 10:46:03 (-0400), Greg Wooledge wrote:
> On Thu, May 06, 2021 at 02:37:17PM +, davidson wrote:
> > > $ shopt -s globstar
> > > $ ls /etc/**/.[^.]*
> >
> > It now occurs to me that this still omits files like /etc/.a and
> > /etc/..metadotfile
>
> It doesn't omit .a .
On Thu, May 06, 2021 at 02:37:17PM +, davidson wrote:
> > $ shopt -s globstar
> > $ ls /etc/**/.[^.]*
>
> It now occurs to me that this still omits files like /etc/.a and
> /etc/..metadotfile
It doesn't omit .a . The * is allowed to match the empty string.
> Instead,
>
> $ ls
On Thu, 6 May 2021 davidson wrote:
[dd]
To that end, I can occasionally do something like
$ ls -Rp | less
and make a point of examining the first couple of things that look
unfamiliar.
This misses out dotfiles.
[dd]
So when I look for what I'm missing out on, and do...
$ shopt -s globstar
On Wed, 5 May 2021 David Wright wrote:
[dd]
One thing I didn't learn is why .pwd.lock is in /etc/ rather than,
say, /run/lock/. Perhaps related, why are there dotfiles in /etc/
anyway. (.git/, .java/, .etckeeper, .gitignore are the others.)
What are they hiding from?
[dd]
I would assume that
On Wed 05 May 2021 at 12:01:07 (-0400), Greg Wooledge wrote:
> On Wed, May 05, 2021 at 10:36:53AM -0500, David Wright wrote:
> > OTOH perhaps monkeysphere has some reason to lock /etc/passwd et al
> > during operation. Running strings on its binaries might throw up
> > some 'pwd.lock' matches. Or
On Wed, 5 May 2021 10:36:53 -0500
David Wright wrote:
> [W]hy are there dotfiles in /etc/ anyway.
> (.git/, .java/, .etckeeper, .gitignore are the others.) What are they
> hiding from?
Indeed. And shouldn't one be backing them up?
I see that amanda has been backing them up and that "add *" in
David Wright wrote:
> Yes, it was an assumption, and perhaps now we shall never
> know. (Sampling the emails didn't appeasr to be an option.)
> We also were not told whether 2757 notifications came in
> over a week, a month, a year, or since openssh-client was
> installed, whenever that was
Greg Wooledge wrote:
> I interpreted it as literally being thousands of instances
> of the *same* file, the one shown in the Subject: header and
> in the original message body.
They were all from iwatch, but they were so many I don't know
if they were exactly the same, and now I don't get any
On Wed, May 05, 2021 at 10:36:53AM -0500, David Wright wrote:
> OTOH perhaps monkeysphere has some reason to lock /etc/passwd et al
> during operation. Running strings on its binaries might throw up
> some 'pwd.lock' matches. Or one could inotifywatch the program to
> see how often it is run
On Wed 05 May 2021 at 07:26:34 (-0400), Greg Wooledge wrote:
> On Tue, May 04, 2021 at 09:32:49PM -0500, David Wright wrote:
> > It looks reasonable for determining whether your system files are
> > being interfered with. But you just showed one example from the
> > log, which was for the
On Tue, May 04, 2021 at 09:32:49PM -0500, David Wright wrote:
> It looks reasonable for determining whether your system files are
> being interfered with. But you just showed one example from the
> log, which was for the /etc/.pwd.lock lockfile. I assume you don't
> have 2757 of these but, rather,
David Wright wrote:
> Myself, I find inotify-tools more useful: I use inotifywait
> in a loop, waiting for a browser to close files in its
> cache. I then examine their filetype and copy the ones
> I want, giving them sensible (timestamp) names. Very useful
> for capturing (typically, live)
David Wright wrote:
> might help determine why you installed iwatch.
Oh, so I did?
Well then, I'll just remove it!
--
underground experts united
https://dataswamp.org/~incal
David Wright wrote:
> $ aptitude why iwatch
i openssh-client Suggests monkeysphere
i A monkeysphere Suggests monkeysphere-validation-agent
i A msva-perl Provides monkeysphere-validation-agent
i A msva-perl Recommends
Kushal Kumaran wrote:
> The manpage at
> https://manpages.debian.org/buster/iwatch/iwatch.1.en.html
> shows log output similar to what you see. Check your iwatch
> configuration and see what it is doing.
Thanks, but I've never heard of iwatch, so I haven't mucked
around with its config file. But
On Wed 05 May 2021 at 04:39:21 (+0200), Emanuel Berg wrote:
> David Wright wrote:
>
> > might help determine why you installed iwatch.
>
> Oh, so I did?
>
> Well then, I'll just remove it!
Myself, I find inotify-tools more useful: I use inotifywait in a loop,
waiting for a browser to close
>> The "IN_" prefix tells you that this is an inotify event.
>> IN_CLOSE_WRITE fires when a process _had_ the specified
>> file open for writing, but has just closed it. Perhaps you
>> have an "incron" job somewhere?
>
> I have cron do two very short scripts every @midnight, these
> run fine
On Wed 05 May 2021 at 03:11:53 (+0200), Emanuel Berg wrote:
> Kushal Kumaran wrote:
>
> > The manpage at
> > https://manpages.debian.org/buster/iwatch/iwatch.1.en.html
> > shows log output similar to what you see. Check your iwatch
> > configuration and see what it is doing.
>
> Thanks, but I've
On Wed, May 05, 2021 at 03:11:53AM +0200, Emanuel Berg wrote:
> Kushal Kumaran wrote:
> > The manpage at
> > https://manpages.debian.org/buster/iwatch/iwatch.1.en.html
> > shows log output similar to what you see. Check your iwatch
> > configuration and see what it is doing.
>
> Thanks, but I've
On Tue, May 04 2021 at 11:11:02 AM, Emanuel Berg wrote:
> Darac Marjal wrote:
>
>> The "IN_" prefix tells you that this is an inotify event.
>> IN_CLOSE_WRITE fires when a process _had_ the specified file
>> open for writing, but has just closed it. Perhaps you have
>> an "incron" job somewhere?
Darac Marjal wrote:
> The "IN_" prefix tells you that this is an inotify event.
> IN_CLOSE_WRITE fires when a process _had_ the specified file
> open for writing, but has just closed it. Perhaps you have
> an "incron" job somewhere?
I have cron do two very short scripts every @midnight, these
Darac Marjal wrote:
>> I get system mail all the time - I've got 2757 at the
>> moment - that tells me that
>>
>> [ 4/Apr/2021 22:11:33]
>> IN_CLOSE_WRITE /etc/.pwd.lock
>> * /etc/.pwd.lock is closed
>>
>> Any clues what that problem might be?
>
> The "IN_" prefix tells you that this is an
I get system mail all the time - I've got 2757 at the moment -
that tells me that
[ 4/Apr/2021 22:11:33]
IN_CLOSE_WRITE /etc/.pwd.lock
* /etc/.pwd.lock is closed
Any clues what that problem might be?
TIA
--
underground experts united
https://dataswamp.org/~incal
On 04/05/2021 07:12, Emanuel Berg wrote:
> I get system mail all the time - I've got 2757 at the moment -
> that tells me that
>
> [ 4/Apr/2021 22:11:33]
> IN_CLOSE_WRITE /etc/.pwd.lock
> * /etc/.pwd.lock is closed
>
> Any clues what that problem might be?
The "IN_" prefix tells you that
31 matches
Mail list logo
