Autorun Yandex.Disk as systemd service in Fedora 19

I wanted to make backups on Yandex.Disk. My operating system is Russian Fedora 19 x64. The launch via rc.local was removed from previous releases of Fedora as outdated, and I decided to do everything in my mind — run Yandex.Disk as a system service. The standard launch of services in Fedora 19 is systemd, we are starting to move in this direction. I use the official console client of Yandex.Disk (yes, the code is closed, but it works much faster than webdav, and you don’t have to wrestle with synchronization).

So let's get started:

• I become root

  su 

• I create a local Yandex.Disk directory

   mkdir /mnt/yandex-disk 

• Change directory to download package

   cd /usr/src 

• Downloading 64-bit rpm package

   wget http://repo.yandex.ru/yandex-disk/yandex-disk-latest.x86_64.rpm 

• I install the package

   rpm -ivh yandex-disk-latest.x86_64.rpm 

• I run the initial setting of Yandex.Disk

   yandex-disk setup 

• I answer Yandex.Disk questions
  

    -? [y/N]: N         ,      https://passport.yandex.ru/passport?mode=register  : username  : *******    /root/.config/yandex-disk/passwd  .     . (     '/root/Yandex.Disk'): /mnt/yandex-disk  .    ? [Y/n]: n 

  
  
• I copy the configuration folder in / etc (I think all files should be in standard places)

   cp -r /root/.config/yandex-disk /etc 

• I correct the paths in the /etc/yandex-disk/config.cfg file

   nano /etc/yandex-disk/config.cfg 

• And bring the file /etc/yandex-disk/config.cfg to the following form

   auth="/etc/yandex-disk/passwd" dir="/mnt/yandex-disk" 

• I create the file /usr/lib/systemd/system/yandex-disk.service

   nano /usr/lib/systemd/system/yandex-disk.service 

• With the following content

   [Unit] Description=Yandex Disk console client Requires=network.target [Service] Type=forking User=root Group=root ExecStart=/usr/bin/yandex-disk start -c /etc/yandex-disk/config.cfg #    , ..      ,  : ":      ". #     -  "Requires=",     - ,      #          RestartSec=60 Restart=always [Install] WantedBy=multi-user.target 

• Restart systemd

   systemctl --system daemon-reload 

• I start the yandex-disk.service service

   systemctl start yandex-disk.service 

• Checks service start by command

   systemctl status yandex-disk.service 

• And we get something like this.

   [root@localhost .config]# systemctl status yandex-disk.service yandex-disk.service - Yandex Disk console client Loaded: loaded (/usr/lib/systemd/system/yandex-disk.service; disabled) Active: active (running) since  2013-11-08 23:11:15 MSK; 1s ago Process: 31601 ExecStart=/usr/bin/yandex-disk start -c /etc/yandex-disk/config.cfg (code=exited, status=0/SUCCESS) Main PID: 31638 (yandex-disk) CGroup: name=systemd:/system/yandex-disk.service └─31638 /usr/bin/yandex-disk --tag="1 7 8 9 15 16" --no-daemon="true" --dir="/mnt/yandex-disk" --config="/etc/yandex-disk/config.cfg" --...  08 23:11:15 localhost.localdomain systemd[1]: Started Yandex Disk console client. 

• Or check the service start command

   yandex-disk status -c /etc/yandex-disk/config.cfg 

• And we get this answer

   [root@localhost ~]# yandex-disk status -c /etc/yandex-disk/config.cfg  : 47.1 KB/ 3.3 GB (0 %)   :     .: '/mnt/yandex-disk'  : : 5.2 GB : 4.8 GB   : 10 GB  : 1.9 GB   : : 'TEST/testfile.txt' 

• Adding service yandex-disk.service to startup

   systemctl enable yandex-disk.service 

Everything works after a reboot.

I back up local copies of backups with a local copy of Yandex.Disk by a team in crobtabʻe

 /usr/bin/rsync -rc --delete /mnt/500gb/backups/ /mnt/yandex-disk/backups/ 

Also found the ability to run multiple copies of Yandex.Disk with different accounts. For example:

 /usr/bin/yandex-disk start -c /etc/yandex-disk1/config.cfg /usr/bin/yandex-disk start -c /etc/yandex-disk2/config.cfg /usr/bin/yandex-disk start -c /etc/yandex-disk3/config.cfg 

')
When debugging, I encountered a problem: the service did not start at boot. Issued an error: "Error: the path to the folder is used by another user." But then without any errors, the systemctl start yandex-disk.service was started manually.
It was solved with a crutch with RestartSec = 60 and Restart = always. But I think this is not entirely correct, because the service starts 2 times - what the log section says:

 tail -1000 /var/log/messages | grep 'yandex' Nov 8 19:34:19 sharov yandex-disk[514]: :      : /mnt/yandex-disk Nov 8 19:34:48 sharov systemd[1]: yandex-disk.service holdoff time over, scheduling restart. Nov 8 19:34:49 sharov yandex-disk[1816]:  ... 

PS: My decision does not claim absolute correctness. But it works.
PPS: Something tells me that the Yandex.Disk cart will not allow it to be used normally for backups, since when deleting files from a local copy of Yandex.Disk, they are moved to the basket, and the basket cannot be empty from the console client, only from the web interface. This reduces the size of the disk to the size of the files in the basket. And when it is full, the backups will no longer be copied to it. Or manually press a button to empty the basket from the web interface, which is a crutch. I'll wait until Yandex.Disk is full and see what happens.