Search results

It is probably a system user that some package installs. Like "sshd" or "saned".

I've been doing it wrong for 25 years then :). Having a mail alias seems better than having to log in as root to read root's mail.

Try creating an /etc/aliases file (see man aliases for the format) and then run "newaliases". ETA: I don't think .forward files ever re-wrote the To address, just the so-called "envelope sender" that it gives to the receiving server.

It does the same thing on PVE 8 if you use xterm.js as the console.

I said there were guides for Debian, not PVE. What you did allows access to the GUI, which is what most people what. If you want SSH access you need to join the server itself to your AD domain from the command line using samba/winbind or sssd. This will allow logging in to the PAM realm rather...

You will have to join your PVE server to the AD domain. There are many guides on how to do this for Debian.

Even a dedicated RT kernel won't provide real-time guarantees unless the processes that want such guarantees use the FIFO or RR schedulers, which isn't the default. Which means code changes are needed to make it work. There's also this (from the thread @insatomcat linked): for both kernel and...

Also, this link might be useful for the future: https://wiki.debian.org/DontBreakDebian

Because apt will upgrade things to the newest version it finds in the configured repositories. It can't read your mind you know. Recovery from this will be a bit difficult, might be easier to just re-install the container. Then learn about apt pinning. Or that. Or from Debian backports (which...

BIOS time should be set to UTC for Proxmox, not local time (unless your time zone is UTC). Don't know about your other issues.

That's because you have an old service unit for the one you compiled yourself (Debian never puts anything in /usr/local, that's strictly for the admin). I would uninstall both versions and reinstall the Debain one. This is why you never install things manually if it can be helped. ETA: Never...

Have you tried just hitting the ENTER key? Or just typing "root" and your password? It looks like it is actually booting and showing the login screen.

Is there a reason you can't just "apt install glances"?

Regardless of your feelings about Microsoft, they are the authority on their own licenses, not us random people on the Internet. ETA: It is Microsoft that might sue you, so you should get the answer from them or from a reseller in writing.

Yes, it sounds easy, but it complicates the logic. There are lots of ways for a network connection to fail, various cases to handle. Maybe the target is on a round-robin DNS so you _should_ do the query each time for that to work right, to give one example of a failure case you may not have...

It is absolutely completely unimportant. Even a microcontroller can handle hundreds of requests per second. The reason it looks "weird" is that your network is trivially small.

Does this mean you will be back here later asking why your graphs have 1-hour gaps?

There are 86400 seconds in a day, so that is less than one per second. One request per second is a "heavy load"? WTH?

So PVE sends 0.4 request/sec, x2 = 0.8 request/sec. If that is 40% of your DNS traffic, then we're talking 2 requests/sec in total. Truly an enterprise-grade setup. How will your server withstand the onslaught. What is it, an Altair 8080 or something? BTW, have you noticed how Windows behaves...

That file was added by the IPA tools when you joined your PVE to the IPA domain. I've got the same error on a couple of Debian machines that were upgraded to Trixie. What I did is remove the knownhostsproxy lines while keeping the rest. That's been working for months now.