Werner changed the topic of #armbian to: armbian - Linux for ARM development boards | www.armbian.com | Github: github.com/armbian | Announcements: #armbian-announcements | Developer talk: #armbian-devel | Off-Topic: #armbian-offtopic | Logs: -> irc.armbian.com
RoyK has joined #armbian
<RoyK>
any idea why armbian won't /root/.bashrc when I login with ssh?
Ntemis has quit [Read error: Connection reset by peer]
lyri has quit [Remote host closed the connection]
Dex_2x93 has joined #armbian
Dex_2x has quit [Quit: Client closed]
Dex_2x has joined #armbian
Dex_2x93 has quit [Quit: Client closed]
Dex_2x has quit [Ping timeout: 256 seconds]
<DC-IRC>
[Discord] <menu> proxmox, logging to `/var/log/pve`, wouldn't be an issue if i wasn't churning through VMs
<DC-IRC>
[Discord] <menu> i don't really know what i'm doing to disable it, and don't want to break anything permanently
Dex_2x has joined #armbian
Dex_2x51 has joined #armbian
Dex_2x has quit [Quit: Client closed]
Dex_2x has joined #armbian
Dex_2x51 has quit [Quit: Client closed]
alekksander has joined #armbian
buzzmarshall has joined #armbian
LanDi has joined #armbian
<DC-IRC>
[Discord] <Werner> There should be two files, one is ramlog and one is zram or something. you want to set enabled=false in ramlog. If you don't want to use compressed swap in memory you can disable zram as well. Generated a standard swapfile on your nvme and use that instread.
<DC-IRC>
[Discord] <menu> with ramlog `enabled=false` will it just log to disk as i'd normally expect? the VM is on an NVME that's capable of handling it, although it makes sense why it's the default to protect the SD card
LanDi has quit [Quit: LanDi]
<DC-IRC>
[Discord] <menu> i don't really understand having swap in memory, my understanding of swap is that it's for swapping data in an out of memory
<DC-IRC>
[Discord] <Werner> You are correct. However sdcard are no good for having swap on. Wearing out quickly and are way too slow to be effective. So armbian takes half of available memory, compresses it and adds it as swap to get a little more out of it. Back in the days when SBCs had 256 or 512M only this way very helpful. Does not make much sense with 4G and more devices though. Depends on user scenario though
<DC-IRC>
[Discord] <Werner> Yes, every 10 minutes if you did not adjust fstab as well. By default armbian writes changes every 10 minutes (or 600 seconds) to sd to expand its lifetime. Not needed for nvme of course
<DC-IRC>
[Discord] <menu> so it's running a ramdisk, compressing the ramdisk, then running swap in the compressed ramdisk? that's... actually genius
<DC-IRC>
[Discord] <Werner> Yes
<DC-IRC>
[Discord] <menu> i'll turn both off then, ty @werner, you're incredibly helpful <3
<DC-IRC>
[Discord] <Werner> Welcome
<RoyK>
I have another suggestion
<RoyK>
First, what you see in df, isn't compressed - I just doublechecked
<RoyK>
it's the raw data - compression happens after that, apparently
<RoyK>
otherwise you'd see difference between du -sch /var/log and du -sch --apparent-size /var/log
<RoyK>
which you don't
<RoyK>
second, keeping the logs small, is prime for having them on zram, so I'd suggest setting up a syslog host to receive the data and configure rsyslogd to log everything to @mylogserver.my.tld
<RoyK>
third, change logrotate, at least for proxmox, to rotate the local logs frequently, a lot more than the defaults. You'll have a copy of them on the loghost anyway
<DC-IRC>
[Discord] <rkarlsba> …and there I was on discord too 🙂
<DC-IRC>
[Discord] <rkarlsba> @menu those above were for you, sir
<DC-IRC>
[Discord] <rkarlsba> @menu those above were for you, madame
<DC-IRC>
[Discord] <menu> unfortunately most of that's gone straight over my head, logging isn't something i've ever actually bothered with, because i usually know what the problem is already (it's PEBCAK, always PEBCAK)
<DC-IRC>
[Discord] <menu> huh, there's a `./armbian-allwinner-battery` in the generic UEFI build
<DC-IRC>
[Discord] <Werner> never seen that before
<DC-IRC>
[Discord] <menu> oop wait no i was in the wrong machien 🤣
<DC-IRC>
[Discord] <menu> ~~huh, there's a `./armbian-allwinner-battery` in the generic UEFI build~~
alekksander has quit [Remote host closed the connection]
archetech has joined #armbian
Dex_2x has quit [Quit: Client closed]
alekksander has joined #armbian
LanDi has joined #armbian
alekksander has quit [Remote host closed the connection]
alekksander has joined #armbian
LanDi has quit [Quit: LanDi]
archetech has quit [Quit: Konversation terminated!]
archetech has joined #armbian
jantones has joined #armbian
jantones_ has quit [Ping timeout: 260 seconds]
lyri has joined #armbian
sally has quit [Remote host closed the connection]
alekksander has quit [Read error: Connection reset by peer]
Herc has quit [Read error: Connection reset by peer]
Herc has joined #armbian
<DC-IRC>
[Discord] <lanefu> the UEFI ARM64 image would be best. mainline because proxmox is providing a generic UEFI for grub to boot from. The opi5 image wouldn't work because it's uboot and needs to boot real hardware
<DC-IRC>
[Discord] <lanefu> the armbian qemu image is unique iirc and actually is for an edge case for using qemu uboot rather than UEFI (if its the same one that i setup years ago)
<DC-IRC>
[Discord] <lanefu> the UEFI ARM64 image would be best. mainly because proxmox is providing a generic UEFI for grub to boot from. The opi5 image wouldn't work because it's uboot and needs to boot real hardware
<DC-IRC>
[Discord] <lanefu> the armbian qemu image is unique iirc and actually is for an edge case for using qemu uboot rather than UEFI (if its the same one that i setup years ago)
<DC-IRC>
[Discord] <menu> i've got *one of them* (i don't remember which, but it boots, which is the main thing)
<DC-IRC>
[Discord] <menu> iirc it was the generic UEFI, would rather something bootable with SeaBIOS but it *works* and that's what matters
lyri has quit [Remote host closed the connection]
zeemate has quit [Ping timeout: 248 seconds]
jantones_ has joined #armbian
jantones has quit [Remote host closed the connection]
danilogondolfo has quit [Remote host closed the connection]