Dima Nirox

Members
  • Posts

    12
  • Joined

  • Last visited

Posts posted by Dima Nirox

  1. 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

     

  2. 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?

     

     

  3. 1 hour ago, jdrch said:

    We may just be arguing semantics here, but technically I don't think my implementation is a service in the FreeBSD sense of the word. It's a background process that starts at reboot explicitly from a crontab entry. A true service is managed by FreeBSD init, which quite honestly I've spent years trying to understand - at least for apps like Resilio Sync that are delivered as FreeBSD binaries and not packages - to no avail.

    The other problem with setting up the binary as a service is - IMO - it makes updating it a much bigger PITA, because now you have to tangle with manually stopping and starting the service instead of just killing and then launching the process.*

    I have no actual idea how to set up a FreeBSD service from scratch using only a binary; I've never been able to find any documentation that explains it fully and the FreeBSD Handbook is almost incomprehensible on the topic. Ironically, I got my method from the Handbook itself, which admits that it's easier in most cases to use crontab to get something to start at boot without user interaction. If you're able to figure it out, please by all means share it with me and I'll add it to my writeup.

    IIRC one thing you'll want to look into is your user rc.d directory. I do believe that's where services that run under users live, but I'm not 100% sure. You can also ask at r/freebsd, r/bsd, or the FreeBSD forums.

    Sorry I'm not able to be of further assistance!

    *Soapbox: This is why I laugh when folks complain about systemd on Linux. Systemd is the greatest thing to happen to Linux ever, because it makes service management much less of a barely comprehensible CF as it is with init (as you're experiencing now). Services.msc (Windows) is still the best service management system in existence, period. Click to stop, start, restart, disable, enable, set to manual or automatic, etc. all through a single UI.

    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 :)

  4. 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