Off-and-on trying out an account over at @tal@oleo.cafe due to scraping bots bogging down lemmy.today to the point of near-unusability.

  • 31 Posts
  • 462 Comments
Joined 2 years ago
cake
Cake day: October 4th, 2023

help-circle
  • From my /etc/resolv.conf on Debian trixie, which isn’t using openresolv:

    # Third party programs should typically not access this file directly, but only
    # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
    # different way, replace this symlink by a static file or a different symlink.
    

    I mean, if you want to just write a static resolv.conf, I don’t think that you normally need to have it flagged immutable. You just put the text file you want in place of the symlink.


  • Also, when you talk about fsck, what could be good options for this to check the drive?

    I’ve never used proxmox, so I can’t advise how to do so via the UI it provides. As a general Linux approach, though, if you’re copying from a source Linux filesystem, it should be possible to unmount it — or boot from a live boot Linux CD, if that filesystem is required to run the system — and then just run fsck /dev/sda1 or whatever the filesystem device is.


  • I’d suspect that too. Try just reading from the source drive or just writing to the destination drive and see which causes the problems. Could also be a corrupt filesystem; probably not a bad idea to try to fsck it.

    IME, on a failing disk, you can get I/O blocking as the system retries, but it usually won’t freeze the system unless your swap partition/file is on that drive. Then, as soon as the kernel goes to pull something from swap on the failing drive, everything blocks. If you have a way to view the kernel log (e.g. you’re looking at a Linux console or have serial access or something else that keeps working), you’ll probably see kernel log messages. Might try swapoff -a before doing the rsync to disable swap.

    At first I was under suspicion was temperature.

    I’ve never had it happen, but it is possible for heat to cause issues for hard drives; I’m assuming that OP is checking CPU temperature. If you’ve ever copied the contents of a full disk, the case will tend to get pretty toasty. I don’t know if the firmware will slow down operation to keep temperature sane — rotational drives do normally have temperature sensors, so I’d think that it would. Could try aiming a fan at the things. I doubt that that’s it, though.













  • Valve willing to sell at a loss

    I don’t think that Valve will sell the Steam Machine at a loss.

    Closed-system console vendors often do, then jack up the prices of their games and make their money back as people buy games. So why not Valve?

    Two reasons.

    1. They sell an open system. If Valve sells a mini-PC below cost, then a number of people will just buy the thing and use it as a generic mini-PC, which doesn’t make them anything. A Nintendo Switch, in contrast, isn’t very appealing for anything than running games purchased from Nintendo.

    2. They don’t have a practical way to charge more for games for just Steam Machine users — their model is agnostic to what device you run a purchased game on. So even if they were going to do that, it’d force them to price games non-optimally for non-Steam-Machine users, charge more than would be ideal from Valve’s standpoint.






  • I found that while the lemmy_server process starts successfully and shows “Starting HTTP server at 0.0.0.0:8536” in logs, nothing is actually listening on port 8536.

    Does:

    # netstat -ntap|grep 8536
    

    …show anything bound to the port?

    I’m not sure how you determined that it’s not binding to the port, but that’s how I’d check.

    There isn’t much that should stop a process from listening on a port over 1024 unless another process is already listening on it.