You are not logged in.
Hello:
Since I discovered it long ago, locate has been one of my favourite tools.
But (as far as I know) it only works on the system drive.
ie: where / lives.
Is there a way to be able to use this tool in other drives?
I find myself searching to files/documents in other drives and have a hard time.
Thanks in advance,
A.
Hello:
... arrange the icons manually on the grid ...
... my order is spoiled, not always ...
I know exactly how you feel.
Desktop configuration and icon management have been a major issue ie: PITA for me ever since I abandoned MSOSs and adopted Linux definitely.
Not only Cinammon, but also Mate and Xfce.
If there is one (yes, there is one) thing I have a certain longing for is the way Microsoft managed to work out desktop configuration and icon arrangement.
At least up to XPSP3 which was the last MSOs I was involved with.
ie: Right click -> Arrange Icons By -> a drop down menu which had these options:
Name
Type
Size
Modified
-----------
Show in Groups
Auto arrange
Align to grid
-----------
Show Desktop Icons
Lock Web Icons on Desktop
Run Desktop Cleanup Wizard
In spite of the crap Wizard which could be removed/switched off, I have yet to find a Linux desktop that can do the same thing and do it well.
Incredible ...
I've already gone through Cinammon, Mate and now Xfce and I have found them all to be severely lacking in almost every aspect.
To the extent that my next desktop will probably be Openbox with whatever enhancements I may need to be comfortable enough.
Along the lines of what #! Linux (Waldorf) was.
[rant]
All the Linux desktops I have seen are crap.
With all this Windows <-> Linux shit going on lately ...
Why can't we get a decently working Linux desktop?
ie: easy to configure and with icons that do whatever the fuck I want them to do.
[/rant]
Have to go take my pill.
Cheers,
A.
Hello:
... great fear and trepidation ...
No need for that.
There are no stupid questions, only stupid answers.
Simplicity Linux ...
Here you go:
From https://distrowatch.com/?newsid=10901
Simplicity Linux is a Devuan-based distribution with Cinnamon as the default desktop environment (prior to 2020 it was based on Puppy Linux and Xfce). It comes in three editions: Mini, Desktop and Gaming. The Mini edition features cloud-based software, the Desktop flavour offers a collection of general-purpose software, and the Gaming variant includes a launcher for Steam games.
Download links:
All files: https://sourceforge.net/projects/simplicitylinux/files/
Desktop: https://sourceforge.net/projects/simpli … iles/20.4/
Mini iso: http://downloads.sourceforge.net/simpli … ini204.iso
Just X: http://downloads.sourceforge.net/simpli … x/X204.iso
General discussion: https://sourceforge.net/p/simplicitylinux/discussion/
Installation should be straightforward but I'd look to use for something else.
ie; not an apparently abandoned project.
Cheers,
A.
Hello:
While having a look at the list of services I have on my Devuan Beowulf, I saw a couple that called my attention:
groucho@devuan:~$ sudo service --status-all
[sudo] password for groucho:
--- snip ---
[ - ] brightness
--- snip ---
[ - ] gdomap
--- snip ---
groucho@devuan:~$ Granted, they are not running.
I understand that brightness is for a laptop or portable and could be removed.
But what use is gdomap?
Thanks in advance.
Best,
A.
Hello:
... can't load pcc_cpufreq unless acpi_cpufreq is also loaded ...
I've been trying to find something about the use of pcc_cpufreq and how to load it but nothing so far.
I found this:
groucho@devuan:~$ sudo modprobe -c | grep -i pcc_cpufreq
alias acpi*:ACPI0007:* pcc_cpufreq
alias acpi*:LNXCPU:* pcc_cpufreq
groucho@devuan:~$ I don't get the whole alias idea but lsmod says this ...
groucho@devuan:~$ lsmod | grep -i _cpufreq
pcc_cpufreq 16384 0
acpi_cpufreq 24576 1
groucho@devuan:~$ Is it that loading pcc_cpufreq will always load acpi_cpufreq and not pcc_cpufreq?
The driver is a kernel module:
groucho@devuan:~$ grep -i _cpufreq /boot/config-4.19.0-16-amd64
CONFIG_X86_PCC_CPUFREQ=m
CONFIG_X86_ACPI_CPUFREQ=m
CONFIG_X86_ACPI_CPUFREQ_CPB=y
groucho@devuan:~$ I've read that the pcc-cpufreq driver doesn't scale with > 4 CPUs and the ondemand governor.
But my Sun Ultra 24 box uses the Intel Core2 Q9550 processor which has just 4 CPUs and I am quite willing to dispense with the scaling if I can use the pcc-cpufreq driver to troubleshoot the shudown problem in my system.
Thanks in advance.
Best,
A.
Hello:
That was a miyolinux system ...
Indeed ...
I did not install any live-config packages, so they must have come with Miyo.
The poster was right.
I didn't now about refractainstaller being used by Miyo.
... the live-config change should not need to be undone as it only exists in the running live system.
Now it's fixed.
Thanks for your input.
Best,
A.
Hello:
... linux-image-amd64 metapackage installed ...
Indeed.
That was it. 8^)
Happens when you install from the ground up with a skinny net-install.
Forget lots of things.
Thanks a lot for your input.
Best,
A.
Hello:
I run a parallel Devuan Beowulf installation in my box, on another separate drive.
Yesterday I updated/upgraded my regular/daily installation, 30+ files which included 4.19.0-16-amd64.
I was wanting to the same with this other installation but it did not list the 4.19.0-16-amd64 upgrade.
apt update && upgrade does not list it.
My /etc/sources/list is this:
## package repositories
# -------------------------------------------------------------------------------
# Changed - 20210401 - from Beowulf installation
# -------------------------------------------------------------------------------
# beowulf stable
deb http://deb.devuan.org/merged beowulf main contrib non-free
deb http://deb.devuan.org/merged beowulf-security main contrib non-free
deb http://deb.devuan.org/merged beowulf-updates main contrib non-free
# needed x virtualbox backport - enable to update package
# deb http://deb.devuan.org/merged beowulf-backports main contrib non-free
# needed x nvidia non-free drivers installation
# deb http://deb.devuan.org/merged/ beowulf contrib
# deb http://deb.devuan.org/merged/ beowulf non-free
# virtual box repository x installation
# deb http://download.virtualbox.org/virtualbox/debian/ buster non-free contrib
# deb http://deb.devuan.org/merged/ beowulf main
# deb http://deb.devuan.org/merged/ beowulf-security main
# deb http://deb.devuan.org/merged/ beowulf-updates main
# deb http://deb.devuan.org/devuan/ beowulf-proposed main
# deb http://deb.devuan.org/merged/ beowulf non-free contrib main
# deb http://deb.devuan.org/merged/ beowulf-security non-free contrib main
# deb http://deb.devuan.org/merged/ beowulf-updates non-free contrib main How can I troubleshoot this?
Edit:
root@devuan3:~# aptitude why-not linux-headers-4.19.0-16-amd64
Not currently installed
The candidate version 4.19.181-1 has priority optional
No dependencies require to remove linux-headers-4.19.0-16-amd64
root@devuan3:~# My main installation does not have this optional priority.
Why is it here?
Thanks in advance,
A.
Hello:
uh-oh...
I haven't been paying close attention to this thread.
Tsk, tsk ... 8^D!!!
Can't do everyhting.
live-config messes with anacron via the live-config script ...
So it seems.
... useful in a live-CD where everything is read-only.
... only activates when you boot into a live system, not an installed system.
Yes.
Refractainstaller copies the RUNNING live system to hard drive.
The post at Dev1 that I linked to, which had the same /usr/sbin/anacron --> /bin/true and deviations apparently was not/had not been using Refractainstaller.
So something other used live-config and generated the same problem.
https://dev1galaxy.org/viewtopic.php?id=1901
ie: this would not be specific to the refractainstaller but to how live-config is used by any application. (?)
You just uncovered a 10-year-old bug ...
No.
It was ralph.ronnquist who saw it and pointed it out to me while helping me sort out the problem I was having with anacron.
https://dev1galaxy.org/viewtopic.php?pid=28663#p28663
I just observed and tried to pay attention.
A question just occurred to me: in 10 years, no one else using refractainstaller had a problem/issue with anacron?
Maybe there's something that's not working right.
ie:
I realised what was going on when I saw that my fstrim script was not logging.
If not for that, I would have never known about what was going on with anacron.
And I don't recall any system notifications warning me of anacron failures.
Not good, no?
The installer needs to undo this during the installation.
Sure.
But it is live-config that is making a signifficant change.
No clean-up after use?
A notification of some sort?
eg:
Don't forget to clean up /usr/sbin/anacron --> /bin/true afterwards.
I see this in syslog for the first time after reboot.
... it's working now.Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.daily' in 5 min. Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.weekly' in 10 min. Apr 1 15:44:42 localhost anacron[1828]: Will run job `cron.monthly' in 15 min.
Yes, it's working.
Thanks a lot for your input.
Best,
A.
Hello:
Why not?
What happens when you comment-out the wtmp & btmp stanzas?
Don't know.
I did not edit anything, I just renamed the original as logrotate.old and copied the new one in.
Altoid wrote:What does your logrotate.conf look like?
My Devuan Beowulf has logrotate 3.14.0:
groucho@devuan:~$ sudo logrotate --version
logrotate 3.14.0
Default mail command: /usr/bin/mail
Default compress command: /bin/gzip
Default uncompress command: /bin/gunzip
Default compress extension: .gz
Default state file path: /var/lib/logrotate/status
ACL support: yes
SELinux support: yes
groucho@devuan:~$ But for some strange reason, the logrotate.conf file I have is the logrotate.conf file packaged with logrotate 3.13.0, without this line:
--- snip ---
# use date as a suffix of the rotated file <---- | x |
dateext
--- snip ---The rest is the same.
See: https://github.com/logrotate/logrotate/ … 3.0.tar.gz
I'll get the .*conf file from logrotate 3.14.0 and use that.
Will report back once done.
Edit:
Works, no errors.
But my logrotate.conf file was the wrong version.
Thanks for your input.
Best,
A.
Hello:
Have you actually tried ...
Yes.
At least in my system it is not a drop-in replacement.
There is at least one thing I noticed.
And the fixed logrotate.conf has this:
# use the syslog group by default, since this is the owning group
# of /var/log/syslog.
su root syslogIn Devuan Beowulf there is not syslog group (at least I can't find it).
groucho@devuan:~$ grep syslog /etc/group
groucho@devuan:~$ Also, syslog is owned by root but belongs to the adm group:
groucho@devuan:~$ ls -l /var/log/syslog
-rw-r----- 1 root adm 4816 Apr 1 13:30 /var/log/syslog
groucho@devuan:~$ That's why I think someone esle with proper skills has to have a look.
... don't have any wtmp lines in /etc/logrotate.conf in my bullseye ...
My Devuan Beowulf has it:
roucho@devuan:~$ cat /etc/logrotate.conf
# see "man logrotate" for details
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log files after rotating old ones
create
# uncomment this if you want your log files compressed
compress
# packages drop log rotation information into this directory
include /etc/logrotate.d
# no packages own wtmp, or btmp -- we'll rotate them here
/var/log/wtmp { <----- | x |
missingok
monthly
create 0664 root utmp
rotate 1
}
/var/log/btmp { <----- | x |
missingok
monthly
create 0660 root utmp
rotate 1
}
# system-specific logs may be configured here
groucho@devuan:~$ So apparently that is why we get the mail I posted.
What does your logrotate.conf look like?
Thanks for your input.
Best,
A.
Hello:
There is a bug in the logrotate.conf configuration.
See here: https://bugs.launchpad.net/ubuntu/+sour … ug/1915759
ralph.ronnquist pointed it out to me here: https://dev1galaxy.org/viewtopic.php?pid=28663#p28663 while helping me with an anacron problem caused (probably) live-config.
The error shows up when logrotate is run in /etc/cron.whatever and then you get notifocaton from the system:
From root@devuan Thu Apr 01 11:31:07 2021
Envelope-to: root@devuan
Delivery-date: Thu, 01 Apr 2021 11:31:07 -0300
From: Anacron <root@devuan>
To: root@devuan
Subject: Anacron job 'cron.daily' on devuan
Content-Type: text/plain; charset=US-ASCII
Date: Thu, 01 Apr 2021 11:31:07 -0300
/etc/cron.daily/logrotate:
error: /etc/logrotate.conf:18 duplicate log entry for /var/log/wtmp
error: /etc/logrotate.conf:25 duplicate log entry for /var/log/btmp
run-parts: /etc/cron.daily/logrotate exited with return code 1The problem is that the fix posted is an Ubuntu fix.
ie: probably will not run properly in Devuan without adjusting it
Anyone know how to edit it so it will run?
Thanks in advance.
Cheers,
A.
Hello:
One confirmation would be that your fstrim logging shows up.
... manual forced test would be like before, i.e. if live-config is uninstalled, then ...sudo /usr/sbin/anacron -s -d -n -f... should be telling about running the cron.{daily,weekly,monthly} jobs.
Right.
I'll do all that and report back, hopefully marking this long thread as [Solved].
----
Edit:
Done.
No more /usr/sbin/anacron --> /bin/true
groucho@devuan:~$ ls -l /usr/sbin/anacron.orig.anacron
-rwxr-xr-x 1 root root 34832 May 19 2019 /usr/sbin/anacron.orig.anacron
groucho@devuan:~$groucho@devuan:~$
dpkg -S anacron.orig.anacron
diversion by live-config from: /usr/sbin/anacron
diversion by live-config to: /usr/sbin/anacron.orig.anacron
groucho@devuan:~$ groucho@devuan:~$ ls -l /usr/sbin/anacron
lrwxrwxrwx 1 root root 20 Apr 1 11:06 /usr/sbin/anacron -> anacron.orig.anacron
groucho@devuan:~$ groucho@devuan:~$ dpkg -S /usr/sbin/anacron
diversion by live-config from: /usr/sbin/anacron
diversion by live-config to: /usr/sbin/anacron.orig.anacron
anacron: /usr/sbin/anacron
groucho@devuan:~$ I have purged it but I see that the diversion by live-config is still there.
How to go back to the 'original' pre-live-config configuration?
It seems to be working. 8^D!
groucho@devuan:~$
groucho@devuan:~$ sudo /usr/sbin/anacron -s -d -n -f
[sudo] password for groucho:
Anacron 2.3 started on 2021-04-01
Job `cron.daily' locked by another anacron - skipping
Job `cron.weekly' locked by another anacron - skipping
Job `cron.monthly' locked by another anacron - skipping
Normal exit (0 jobs run)
groucho@devuan:~$
groucho@devuan:~$ ----
Once done, who/where would I have to report this problem to?
Does not seem to originate inrefractainstaller-base, more like in the required live-config.
Or is it related to the bug report I linked to?
Don't think is would be a good thing just to leave it be. (?)
Thank you very much for the time and effort you put into solving this problem for me.
Really appreciate it.
Best,
A.
Hello:
Good.
So when the start script runs /usr/sbin/anacron it actuallly runs /bin/true which is doing bugger all...
So ...
That's where things get screwed up?
Possibly @fsmithred (who's doing refracta-base) knows something ...
.. in any case it's wrong for your purpose.
I see.
... two options:
... change the link by:sudo ln -sTf anacron.orig.anacron /usr/sbin/anacron... will undo the redirect, but this then runs the risk of being undone ...
... if the live-config package is updated.
I could eventually pin it ...
... change /etc/init.d/anacron to use /usr/sbin/anacron.orig.anacron as binary;
... change start-stop-daemon --start command line to be
start-stop-daemon --start --exec /usr/sbin/anacron.orig.anacron -- $ANACRON_ARGS... more sticky fix than changing the link ...
... probably breaks if the live-config package is uninstalled.
Hmm ...
I think I can uninstall refracta-base as I have only ever used it from my ascii/Beowulf VM.
That would take care of live-config and the redirection for good.
Unless live-config comes back with something else.
I think I'll do that and then use the first option you have advised.
Think that would do well as a long term solution?
Once done, how should I test that everything is working properly?
Thanks in advance,
A.
Hello:
Over here it's 04/01 ...
This "new" implementation sounds like it might be a useful addition ...
With the obvious proviso that your opinion with respect to this has much more weight that mine, I just see it as yet another one of systemd tentacles.
Reminds me so much of the MS registry.
Thanks for your input.
Best,
A.
Hello:
I know that it's 01/04 today (at least here) but ...
Version 248 of systemd, a widely used system and service manager for Linux, adds a feature called system extension images, designed to allow system files to be added, or appear to be added, even on read-only file systems.
https://www.theregister.com/2021/04/01/systemd_248/
For fuck's sake, does the shit never stop flowing?
Best,
A.
Hello:
All this time I searching ...
How is it that things could get this way?
Poking around the system I found this file: /usr/sbin/anacron.orig.anacron.
Original anacron?
Is there any other? 8^D
For /usr/sbin/anacron.orig.anacron
groucho@devuan:~$ ls -l /usr/sbin/anacron.orig.anacron
-rwxr-xr-x 1 root root 34832 May 19 2019 /usr/sbin/anacron.orig.anacron
groucho@devuan:~$ groucho@devuan:~$ dpkg -S anacron.orig.anacron
diversion by live-config from: /usr/sbin/anacron
diversion by live-config to: /usr/sbin/anacron.orig.anacron
groucho@devuan:~$ For /usr/sbin/anacron
groucho@devuan:~$ ls -l /usr/sbin/anacron
lrwxrwxrwx 1 root root 9 Dec 8 2017 /usr/sbin/anacron -> /bin/true
groucho@devuan:~$ groucho@devuan:~$ dpkg -S /usr/sbin/anacron
diversion by live-config from: /usr/sbin/anacron
diversion by live-config to: /usr/sbin/anacron.orig.anacron
anacron: /usr/sbin/anacron
groucho@devuan:~$ Then I came across this post:
https://dev1galaxy.org/viewtopic.php?id=1901
In that case (non-working anacron in ascii), the diversions by live-config from: /usr/sbin/anacron and to: /usr/sbin/anacron.orig.anacron were also present.
And /usr/bin/anacron was also a link to /bin/true.
I have live-config because of refractasnapshot-base so that is needed.
groucho@devuan:~$ aptitude why live-config
i refractasnapshot-base Depends live-config (>= 2.0.15)
groucho@devuan:~$ From what I understand, it seems that either the /usr/bin/anacron link to /bin/true or the diversions could be related to a non-working anacron.
I also found this from 2013: https://bugs.launchpad.net/ubuntu/+sour … ug/1254614
Confirmed/unassigned.
What do you think?
Thanks in advance,
A.
Hello:
The warning can be ignored.
I see.
... expected to see the output "Anacron 2.3 started on 2021-04-01" after the "transferring control" ...
So like you said, it is not starting.
... which architecture do you have?
groucho@devuan:~$ uname -a
Linux devuan 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux
groucho@devuan:~$
groucho@devuan:~$ file /usr/sbin/anacron
/usr/sbin/anacron: symbolic link to /bin/true
groucho@devuan:~$ groucho@devuan:~$ file $(readlink -f /lib64/ld-linux-x86-64.so.2)
/lib/x86_64-linux-gnu/ld-2.28.so: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=f25dfd7b95be4ba386fd71080accae8c0732b711, stripped
groucho@devuan:~$ This is all rather puzzling.
All this time I searchig, I have seen quite a few cron/crotab issues posted.
But this one takes the prize.
How is it that things could get this way?
BTW: yesterday there was a huge file update which included the kernel. Apparently no issues.
Thanks so much for your help.
Best,
A.
Hello:
Right; that's the right one...
Good thing.
... verify that the problem is with anacron, by seeing ...
sudo /usr/sbin/anacron -s -d -n -f[... report nothing.
groucho@devuan:~$ sudo /usr/sbin/anacron -s -d -n -f
[sudo] password for groucho:
groucho@devuan:~$ Reports nothing, so it would seem to be anacron.
... try the following:
sudo env LD_DEBUG=libs,files /usr/sbin/anacron -s -d -n -f >& /tmp/strace.log... and paste somewhere
It's very short:
groucho@devuan:~$ cat /tmp/strace.log
32311:
32311: WARNING: Unsupported flag value(s) of 0x8000000 in DT_FLAGS_1.
32311:
32311: file=libc.so.6 [0]; needed by /usr/sbin/anacron [0]
32311: find library=libc.so.6 [0]; searching
32311: search cache=/etc/ld.so.cache
32311: trying file=/lib/x86_64-linux-gnu/libc.so.6
32311:
32311: file=libc.so.6 [0]; generating link map
32311: dynamic: 0x00007feb40805b80 base: 0x00007feb4064b000 size: 0x00000000001c0800
32311: entry: 0x00007feb4066f1b0 phdr: 0x00007feb4064b040 phnum: 12
32311:
32311:
32311: calling init: /lib/x86_64-linux-gnu/libc.so.6
32311:
32311:
32311: initialize program: /usr/sbin/anacron
32311:
32311:
32311: transferring control: /usr/sbin/anacron
32311:
32311:
32311: calling fini: /usr/sbin/anacron [0]
32311:
groucho@devuan:~$ ... debug listing of the loading of dynamic libraries including how they are looked up in the file system.
Looks for just one library and cache tells it where to find it.
ie: /lib/x86_64-linux-gnu/libc.so.6
groucho@devuan:~$ locate libc.so.6
/lib/i386-linux-gnu/libc.so.6
/lib/x86_64-linux-gnu/libc.so.6
groucho@devuan:~$ Must be the warning?
Thanks.
Best,
A.
Hello:
... your /usr/sbin/anacron dies before it starts ...
I'll take your word for that.
I can't make heads or tails of it.
... at the point where it should allocate memory.
With 8Gb at hand, I never see the swap file get used.
... premature exiting, and that suggests borked linking rather than out of memory; i.e., a technological mismatch with the dynamic libraries ...
Which libc6 do you have?
ls -l /lib*/ld-linux-*
Here it is:
groucho@devuan:~$ ls -l /lib*/ld-linux-*
lrwxrwxrwx 1 root root 32 May 1 2019 /lib64/ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-2.28.so
groucho@devuan:~$ Thanks.
Best,
A.
Hello:
| | |-grep,13714 --color=always -A 3 anacron
that was the grepping itself ...
Try again with
sudo start-stop-daemon -v --start --exec /usr/sbin/anacron -- -s -d -n -f
Hmm ...
I think you are on to something here:
groucho@devuan:~$ sudo start-stop-daemon -v --start --exec /usr/sbin/anacron -- -s -d -n -f
[sudo] password for groucho:
Starting /usr/sbin/anacron...
groucho@devuan:~$ ... and verify that that only gives that same one line of output...
It doesn't.
Check then at end of /var/log/syslog to see if there's an explanation.
Let's see:
groucho@devuan:~$ tail -7 /var/log/syslog
Mar 31 20:35:01 devuan CRON[15101]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 31 20:45:01 devuan CRON[16636]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 31 20:55:01 devuan CRON[18468]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 31 21:00:01 devuan CRON[19233]: (root) CMD (timeshift --check --scripted)
Mar 31 21:00:01 devuan crontab[19266]: (root) LIST (root)
Mar 31 21:00:01 devuan crontab[19267]: (root) LIST (root)
Mar 31 21:05:01 devuan CRON[20031]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
groucho@devuan:~$ Following that we'll need to go deep diving ...
Right.
groucho@devuan:~$ sudo strace -f start-stop-daemon -v --start --exec /usr/sbin/anacron -- -s -d -n -f >& /tmp/strace.log
groucho@devuan:~$ Done.
... will be long as it includes all the system calls by the execution, so the best is if you can paste it ...
Done: -> https://pastebin.com/5Mry6Pm7
... there's something just a little bit off on your system and this will give as a haystack to look in.
It was ascii and I think I upgraded when Beowulf a day or two after 3.1.0 was announced.
Let me know if you need more data/tests.
Thanks in advance.
Best,
A.
Hello:
My test showed nothing ...
Thanks for the effort.
... realized that your forced running only resulted in a "Starting..." message, and not like the expected
$ sudo start-stop-daemon -v --start --exec /usr/sbin/anacron -- -s -d -n -f [sudo] password for ralph: Starting /usr/sbin/anacron... Anacron 2.3 started on 2021-04-01 Will run job `cron.daily' Will run job `cron.weekly' Will run job `cron.monthly' Jobs will be executed sequentially Job `cron.daily' started Job `cron.daily' terminated Job `cron.weekly' started Job `cron.weekly' terminated Job `cron.monthly' started Job `cron.monthly' terminated Normal exit (3 jobs run)
Which package version do you have?
apt-cache policy anacron |& grep Installed
groucho@devuan:~$ apt-cache policy anacron |& grep Installed
Installed: 2.3-28
groucho@devuan:~$Is there an anacron running?
pstree -ap | grep -A 3 anacron
Yes.
groucho@devuan:~$ pstree -ap | grep -A 3 anacron
| | |-grep,13714 --color=always -A 3 anacron
| | `-pstree,13713 -ap
| |-{xfce4-terminal},13572
| `-{xfce4-terminal},13573
groucho@devuan:~$ Thanks,
A.
Hello:
... re logrotate.conf since 18 and 25 are duplicates you might want to compare with the lines before those.
Let's see:
groucho@devuan:~$ cat /etc/logrotate.conf
1 # see "man logrotate" for details
2 # rotate log files weekly
3 weekly
4
5 # keep 4 weeks worth of backlogs
6 rotate 4
7
8 # create new (empty) log files after rotating old ones
9 create
10
11 # uncomment this if you want your log files compressed
12 compress
13
14 # packages drop log rotation information into this directory
15 include /etc/logrotate.d
16
17 # no packages own wtmp, or btmp -- we'll rotate them here
18 /var/log/wtmp {
19 missingok
20 monthly
21 create 0664 root utmp <--- | x |
22 rotate 1
23 }
24
25 /var/log/btmp {
26 missingok
27 monthly
28 create 0660 root utmp <--- | x |
29 rotate 1
30 }
31
32 # system-specific logs may be configured here
groucho@devuan:~$ Line 21 -> create 0664 root utmp
Line 28 -> create 0660 root utmp
These two lines are identical save for the permissions the files are assigned when created.
Can't create two files with the same name, no?
man utmp indicates that these are use and login records.
From what I understand, wtmp has information about who is using the systen and wtmp records all login and logouts.
groucho@devuan:~$ less /var/log/wtmp
"/var/log/wtmp" may be a binary file. See it anyway?
groucho@devuan:~$ groucho@devuan:~$ less /var/log/btmp
/var/log/btmp: Permission denied
groucho@devuan:~$ groucho@devuan:~$ sudo less /var/log/btmp
[sudo] password for groucho:
"/var/log/btmp" may be a binary file. See it anyway?
groucho@devuan:~$ Thanks for your input.
Best,
A.
Hello:
You seem to mix up non-root and root user ...
Not surprised.
Sorry.
... the user's cron jobs ar run as that user ...
I see ...
... only root's cron jobs are run as root.
The anacron problem is not that problem, since it gets run by root.
Right.
Any tests I could run to help?
Thank you for your input.
Best,
A.
Hello:
But the problem is that /etc/cron.whatever is not running the scripts as expected.
Maybe not?
Maybe it is just not getting logged?
To try to understand a bit more, I tried this:
Instead of a script to run and log fstrim I tried to run and log something much simpler and (in principle) fool proof.
This is the script:
groucho@devuan:/etc/cron.daily$ cat testing
#!/bin/sh
# test to write to /var/log
# called from crontab
#
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
LOG=/var/log/testing.log
echo "On $(date -R):" >> $LOG
/bin/uname -a >> "$LOG" 2>&1
groucho@devuan:/etc/cron.daily$ [root@devuan ~]# /etc/cron.daily/testing
[root@devuan ~]# Runs as root and logs as expected.
groucho@devuan:/var/log$ cat /var/log/testing.log
On Wed, 31 Mar 2021 18:25:00 -0300:
Linux devuan 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19) x86_64 GNU/Linux
groucho@devuan:/var/log$ The I opened crontab and added an entry to run that same script once a minute:
groucho@devuan:/var/log$ crontab -l
--- snip ---
SHELL=/bin/sh
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
# ---
# test
# ---
* * * * * /etc/cron.daily/testing
# ---
--- snip ---This probably gets executed but it does not get logged:
From groucho@devuan Wed Mar 31 18:32:01 2021
Envelope-to: groucho@devuan
Delivery-date: Wed, 31 Mar 2021 18:32:01 -0300
From: root@devuan (Cron Daemon)
To: groucho@devuan
Subject: Cron <groucho@devuan> /etc/cron.daily/testing
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 8bit
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <HOME=/home/groucho>
X-Cron-Env: <LOGNAME=groucho>
Date: Wed, 31 Mar 2021 18:32:01 -0300
/etc/cron.daily/testing: 7: /etc/cron.daily/testing: cannot create /var/log/testing.log: Permission denied
/etc/cron.daily/testing: 8: /etc/cron.daily/testing: cannot create /var/log/testing.log: Permission deniedI think there is a reason that prevents writing to /var/log.
Don't have a clue as to what it can be.
/var/log/testing.log is under root ownership, just like /var/log/trim.log
groucho@devuan:/var/log$ ls -l /var/log | grep testing
-rw-r--r-- 1 root root 120 Mar 31 18:25 testing.log
groucho@devuan:/var/log$
groucho@devuan:/var/log$ ls -l /var/log | grep trim.log
-rw-r--r-- 1 root root 0 Mar 31 16:56 trim.log
groucho@devuan:/var/log$ Any idea?
Thanks in advance,
A.