Pol Isidor

I realised, that my OrangePI Plus 2E doing the logrotate of /var/log.hdd and not /var/log dir
I'm using:
 
root@orangepiplus2e:~# lsb_release -a Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster root@orangepiplus2e:~# uname -r 5.3.13-sunxi In my dir /etc/logrotate.d/ I realised that in every file standing: /var/log.hdd/.... as a path for logrotate even if I change to /var/log/... everytime when I restart my box.
Now if I understand correctly the ram part is named: /var/log/... what can I see from:
root@orangepiplus2e:~# df -h Filesystem Size Used Avail Use% Mounted on udev 939M 0 939M 0% /dev tmpfs 202M 556K 201M 1% /run /dev/mmcblk0p1 15G 4.6G 9.4G 33% / tmpfs 1007M 0 1007M 0% /dev/shm tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs 1007M 0 1007M 0% /sys/fs/cgroup tmpfs 1007M 44K 1006M 1% /tmp mrtg2ram 10M 3.4M 6.7M 34% /var/www/mrtg /dev/zram0 340M 7.1M 308M 3% /var/log tmpfs 202M 0 202M 0% /run/user/0 Here I see that /dev/zram0 is mounted as /var/log. Size I changed in /etc/default/armbian-ramlog.
I inspected and found the file: /usr/lib/armbian/armbian-hardware-optimization is responsable for changing path from /var/log to /var/log/hdd
 
Now what I do not understand is if-else-fi part of function prepare_board() from this file.
CheckDevice=$(for i in /var/log /var / ; do findmnt -n -o SOURCE $i && break ; done) # adjust logrotate configs if [[ "${CheckDevice}" == "/dev/zram0" || "${CheckDevice}" == "armbian-ramlog" ]]; then for ConfigFile in /etc/logrotate.d/* ; do sed -i -e "s/\/log\//\/log.hdd\//g" "${ConfigFile}"; done sed -i "s/\/log\//\/log.hdd\//g" /etc/logrotate.conf else for ConfigFile in /etc/logrotate.d/* ; do sed -i -e "s/\/log.hdd\//\/log\//g" "${ConfigFile}"; done sed -i "s/\/log.hdd\//\/log\//g" /etc/logrotate.conf fi First line checking is it exist the path /dev/zram0
Secod line if yes then rename in every file from /etc/logrotate.d/ pattern /var/log to /var/log.hdd
....
If not do reverse...
 
Why is implemented this?
If all my logs going to /var/log and it's raising what is the logic, if the armbian-ramlog enabled, to rotate /var/log.hdd and not the /var/log ?
Who will then rotate /var/log if it will be full let it say after 12h or 96h?
This problem I had not on Armbian with kernel v3.4.xxx (Jessie), that after every restart the content of files in logrotate.d was renamed.
Because I'm not able to understand the logic bihind this I have opinion as it is reversed this if-else-fi part.
 
Would be someone so kind to explain me the logic?
Thx

Thx mate..this is the right answer on question!

Moved to proper location.
armhf is 32bit
arm64 is 64bit.
 
There are a few other variants of arm in 32bit which you can lookup via Wikipedia for example

Huh..it seams that it is not so simple for everyone to reach this poing to have a HW acceleration on H3.
My goal is to reach transcoding from h264 full HD as input stream (satillite stream from enigma2 receivers) and lower down the resolution to SD in h264 with FFmpeg.
I compiled myself the ffmpeg with h264 and libfdk-aac.
All this working even without HW but from SD to SD.
Is there some detail tutorial how can I reach this point?
Thx!

After I set the CPU speed as described above the issue never came back

Hi everybody ! Is it possible to transfer from emmc to sd card? That is, as in the nand-sata-install script, only in the opposite direction.

Hello everyone!
I have same issue with Orange Pi Zero (Linux orangepizero 4.19.62-sunxi #5.92 SMP Wed Jul 31 22:07:23 CEST 2019 armv7l GNU/Linux)
I have running 20 devices. And now 4 devices have 1978 year and I can't connect thru ssh..
Devices sends every 30 seconds 'alive' message via MQTT, so I see this trouble but can't do anything because devices are remote and no access thru ssh.
I changed CPU speed to fixed 816 Mhz at available devices, and I will monitoring this situation and hope this help.
 
Maybe someone have any news/solutions for this trouble?
 
Founded how to remotely reboot OPi with 1978 date error using SSH:
ssh username@yourIP -p yourPort "echo 1 > /proc/sys/kern/sysrq;echo b > /proc/sysrq-trigger"

set the minimum CPU speed to 110400 and maximum speed to 110400. CPU governor = conservative (armbian config > system > CPU).
So the processor will not change the CPU clock.