Search results

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.

Debian 13 isn't even released yet. Magic 8-ball says try again later.

Just to elaborate a bit, I've been pretty pleased with the Linux support on the FW 13 laptop. I've got the AMD one and they officially support a number of distros on it, which I took as a good sign. Debian Bookworm isn't one of them but I've been running it for a year with good success. I used...

I'll let you know when I get mine. I don't think any been delivered to customers yet. They are saying Q3, which just started a few days ago.

That's what Stop is for.

If the guest is Linux you probably can just change it. If it is Windows you may need to repair afterward. Why do you think you need to change them?

Is hard because of compression. It is difficult to know up-front how big the final archive will be. Making assumptions will lead to wrong answers and user grief (in both directions). Is unsafe because if the new backup fails you are down by one. Best practice is for the administrator to make...

A stop + start will do that.

Probably. I guess that depends on whether you are comfortable allowing anyone, anywhere, to try to hack your server. Putting your server's management interface on the public internet with no firewall is very far from best practices in regard to security. Why do you want this? That is the...

Unless this is a business connection his provider almost certainly does not want him to set a static IP. In the case he has done that (rather than DHCP), the provider is going to block him.

Or you could look at the logs and try to reason it out. That's work, I know, but it might actually help you find a solution.

Did ChatGPT advise you to look at the syslog (journalctl -b0) or the task log (in the GUI) around the time of the stoppage?

Two IP's on the same subnet is usually a recipe for trouble. It does odd things you might not expect. What kind of software is this? Some kind of proxy? If so, it is likely expecting two different subnets so that packets can be sent between them. ETA: Depending on why you are doing this there...

So it seems to be specific to a particular Ethernet driver used by RPi4 boards. Which explains why I have never seen this problem, as my OpenWRT is running on a Celeron J1900 with Intel Ethernet. Nice find! ETA: On the other hand, the #1 cause of "temporary failure in name resolution" is a bad...