Dima Nirox

Hello! Any news?

that will be fine )

Unfortunately not. This is a problem in openSUSE itself but the guru do not consider this a as problem, I have not received an answer or a solution to fix it. I'm back on Kubuntu and I'm thinking of staying on it like I did 14 years before...

I think I found my problem.... chkconfig command is gone

Hello dear team! I'm trying to install Resilio Sync in openSUSE Tumbleweed it according to the instructions. I've done this a million times before, everything was perfect. But I did it on debian-like systems. Now there is a task to install the service on openSUSE tumbleweed and I can not force it to run at system startup. The error description is below. I will be very grateful for any help, I am a complete beginner in openSUSE. XXX:~> sudo systemctl enable resilio-sync [sudo] password for root: Synchronizing state of resilio-sync.service with SysV service script with /usr/lib/systemd/systemd-sysv-install. Executing: /usr/lib/systemd/systemd-sysv-install enable resilio-sync /usr/lib/systemd/systemd-sysv-install: line 31: chkconfig: command not found If I try to start service by manual like: sudo systemctl start resilio-sync all fine, but after reboot need to start it again... it's bad practices. Thanks! It's asap question for me. Operating System: openSUSE Tumbleweed 20210505 KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.12.0-2-default OS Type: 64-bit Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 PRO 4750U with Radeon Graphics Memory: 22.7 GiB of RAM Graphics Processor: AMD RENOIR

Hello team! My task is: sync data to the /media/username/DATA256 directory. The user rslsync is added to the group and everything works perfectly with main system SSD. The laptop has 3 physical SSD. System and two extra. Extra SSD mounted (allowed to do this to a user without root rights) in /media/username/DATA256 Problem: in WebUI Resilio, when I try to go to the /media/username/DATA256 directory, only /media/username/ opens, then the subdirectories are not displayed. What am I doing wrong?

Intel 1000

Yes I did it I reinstalled my old server and now it runs Proxmox and it already runs Ubuntu 20.04.1 and FreeBSD 12.2 Surprisingly, the network speed test shows a big difference. FreeBSD does not hang 500-600mb/s at the same time in Ubuntu the speed is not lower than 800-900mb/s all this on one server, in one data center but I'm still working on it.

All fine. You've already helped me. For me, it is more an experiment to understand from personal experience whether FreeBSD is really so "good and reliable" for my purposes. So far, I doubt it very much. The documentation does not correspond to reality, most of the applications that I use in Linux are just not available for FreeBSD, there is no virtualization as a guest system (qemu agent is absent in nature, not counting the ported version with limited functionality). Something tells me that I will play with this system for a while and go back to Linux, because everything just works there. And I do not want to start swearing about Linux vs FreeBSD, but to study the problem for more than two weeks.... It's not even funny

yes, the problem is in autostart of the service on load like user, not root. I added this and other strings (options for running the script) to the user crontab and system, even tried options with sudo username but the service does not start at system startup.

Hello! I can't say that your instruction works for me, but I still have a question, how do I run resilio as a user at system startup? I've tried system crontab, user crontab and it's not working. Only placing the script with the command in /etc/rc.d / solves my problem, but running as root is not what I need. Thanks. P.S. I want to build a very reliable backup server for myself, because FreeBSD + is a new experience for me, it is still very different from Linux, at least in the examples of documentation of real cases. And yes, I am studying the handbook for the second day, but there are no examples that I need. More precisely they do not work in FreeBSD 12.2

Yes, same problem.