conorab

joined 1 year ago
[–] conorab@lemmy.conorab.com 1 points 2 weeks ago

Last time they’ll ever do that! Pass the buck of hosting web-facing Plex servers onto somebody else.

[–] conorab@lemmy.conorab.com 1 points 1 month ago

Adding to this: doesn’t CAD usually want 3D acceleration? I would definitely try running the CAD software with the same VM configuration you plan to use in your Proxmox VPS first before progressing to make sure it (a works at all and b) is responsive enough. You could even try nesting Proxmox in Proxmox to emulate the kind of performance you’d had on a VPS.

[–] conorab@lemmy.conorab.com 4 points 1 month ago

SnipeIT just cares about serial numbers, models and manufacturers (you can just use a serial number in the asset tag section) for assets and I think consumables drop a bunch of those requirements. You might be able to put groceries under consumables? I’m less familiar with consumables in SnipeIT to be honest.

[–] conorab@lemmy.conorab.com 6 points 1 month ago* (last edited 1 month ago) (2 children)

SnipeIT is really good and supports SSO including via LDAP.

[–] conorab@lemmy.conorab.com 1 points 1 month ago

They don’t need to be interested though. You could conceivably dump all the password you collect in an attack and just start trying them automatically like you would any other breach. Find a bunch of bank accounts and your chances you getting away with millions are high. Not to mention: a breach like this means changing all your saved passwords to re-secure them which is a multi-day affair.

[–] conorab@lemmy.conorab.com 1 points 1 month ago (2 children)

Self-hosting removes the risk of somebody compromising Bitwarden’s servers and adding malicious javascript to send off your master password to a bad actor instead of just processing it locally like it’s designed to.

[–] conorab@lemmy.conorab.com 1 points 1 month ago

I don’t think ZFS can do anything for you if you have bad memory other than help in diagnosing. I’ve had two machines running ZFS where they had memory go bad and every disk in the pool showed data corruption errors for that write and so the data was unrecoverable. Memory was later confirmed to be the problem with a Memtest run.

[–] conorab@lemmy.conorab.com 0 points 1 month ago

What distro and version of that distro are you using? Did you install gpg from the repository or elsewhere? What version of gpg are you running?

[–] conorab@lemmy.conorab.com 8 points 3 months ago

The OOM killer is particularly bad with ZFS since the kernel doesn’t by default (at least on Ubuntu 22.04 and Debian 12 where I use it) see the ZFS as cache and so thinks its out of memory when really ZFS just needs to free up some of its cache, which happens after the OOM killer has already killed my most important VM. So I’m left running swap to avoid the OOM killer going around causing chaos.

[–] conorab@lemmy.conorab.com 3 points 4 months ago

I think that also causes issues for roaming profiles and folder redirection. If roaming is turned on then everything in the %appdata%\roaming folder is synced to a server. %AppData%\Local is not. So if your app is using %AppData%\Roaming for temporary data then you are causing a whole bunch on unnecessary IO. Same for using Documents since that if often synced.

[–] conorab@lemmy.conorab.com 2 points 4 months ago

So much better than my FunnelWAP. Best it can do is 100 KillerBytes. :(

view more: next ›