Hello:

Hmm ...
Maybe it's too soon to sign the certificate?
There's still much to be said.

Many years ago (unfortunately much later than I should have) one day I realised that I could always solve any apparent confusion or contradiction by stepping back and having a close look at what was going on with the purpose of getting a grasp of who was where and why.

While the why part of the exercise many times remained (as it usually does) unknown, the who and where have always proved to be quite revealing.
The end result being that whatever confusion or contradiction I may have had cleared up very quickly.

To wit:
I realised I was definitely a Democrat by the age of 13 not because of my reading of the opinion pieces of the two newspapers I delivered every afternoon but by listening to what Mr. Davis, my next door neighbour and certified dyed in the wool Republican had to say about things in general.
I'll always be grateful to the old chap for that.

With respect to the matter of X, if Red Hat, IBM et al are attempting to sink it, don't count me in.
I have faith in the resilience of the Linux ecosystem albeit not in its constituents.

Just my 0.02.

A.

Hello:

Right.
Further thinking about it, I see it makes sense.

I recall (?) thinking about that but did not see the need for the rotated files.
I'll look into that, thanks for the heads up.

Yes, I have seen that done.
And taking into account how unintelligible they are ...

But I have found that they have been a sort of reference for comparison purposes between boots.
Not that I actually solved anything.  8^7

Thanks a lot for your input.

Best,

A.

Hello:

Yes, I'll have a look at the alternatives to *locate + the link and see what I can get.
Thanks a lot for your input.  8^)

Best,

A.

Hello:

No need for that.
There are no stupid questions, only stupid answers.

Here you go:

From https://distrowatch.com/?newsid=10901

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:

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:

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:

Tsk, tsk ...  8^D!!!

Can't do everyhting.

So it seems.

Yes.

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. (?) 

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?

Sure.

But it is live-config that is making a signifficant change.
No clean-up after use?
A notification of some sort?

eg:

Yes, it's working.

Thanks a lot for your input.

Best,

A.

Hello:

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 syslog

In 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.

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:

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:

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.