Posts by getName()

There are some boards, that wont post, but this is not all too common, quite rare to be honest.
Server Mainboards have gpus because sometimes its needed, thats pretty much all. Not everybody has a good ipmi or similar based workenvironment.

To start with: that you refuse to fix the cause.

Right, icinga is overkill in this case, I agree. But those cron jobs that autorestart services are stuff from my nightmares as they just dont fit into the concepts that exist and make multi admin systems a pain.

I did not quite understand the question.
If you asked if omv supports mdadm raids the answer is yes.

Actually this is a very ugly solution. If you need to monitor services, do it with existing frameworks (e. g. Icinga) but more importantly: fix the crashes instead!

You need to be really of time though for certificates to become invalid. Maybe check your cmos battery too.

If you really think, this is how containers should be you can seriously go ahead and implement it. Collecting money in this area is rather easy, 5 man dev team with good payment for 2 years should be no issue to get as Initial investment.
You dont have me convinced though. Issues I see is host/container interaction, or better put influence on the host. Issues with fdn and certificates in most currerent networks. Configurable interfaces break portability, also the dependency on the running firewall, selinux and such get more critical. You need to realize, that docker containers in professional environments mostly run in swarm or kubernetes, on inconsistent hw. Also you basically force dns for every container, nobody wants to type ipv6 adresses, so your dns proxy is needed anyways, which in the end means to me: more overhead, more host influence, less portability, higher network environment demands, conceptional issues with virtual docker nets (docker-compose files utulize it basically always), security risks (sounds like default exposing containers), zero gain.

Well, go ahead and implement an alternative or try to convince devs.

You should benchmark locally first. If anything, I would expect ext4 to have a (very slight) speed advantage.
Are caching settings the same?

This should work. However, in some cases the name of your nic changes after removing the gpu which will lead to problems.

chown works with the id, not the name. As long as you dont make sure users and groups by the same name inside and outside the container are the same (e.g. by using ldap), the chown command wont help.

Geht es um ein gemountetes Verzeichnis?

Keep in mind that altering config files by hand may be a bad idea (not in general, but with OMV) and changes may get overwritten or you may create conflictive configs.

That would be horrible.

You can create a phpinfo() file.

I would boot a live medium, dd ( dont forget to set bs, otherwhise it will be very slow), expand partition and fs, if the new disk is bigger.
Dont forget grub-install after the thing.

Looks good to me, I dont know the ssd though.

Is noise level a concern? If the nas can be loud you can consider some 2u server Rack with 12 3.5 hot swap cages. It is pretty easy to find reliable hw in those.

Ram frequency is only important for inter core communication or of course general memory dependent tasks, so I dont see high gains through faster ram.
In case of NAS or generally high uptime systems I highly recommand staying within the jedec norm! Dont use these overclocking modes (i. e. 3200MHz DDR4) !

Es gibt Nachrichten, ob diese bei omv peristiert werden weiß ich nicht auswendig. Beim boot mal quiet von den Optionen nehmen, am besten einfach per e im grub, da es besser nicht dauerhaft umgestellt sein sollte.
Sonst mal in /var/log nachsehen.