Package Details: asf-plugin-itemsmatcher 6.1.0.3-1

Git Clone URL: https://aur.archlinux.org/asf.git (read-only, click to copy)
Package Base: asf
Description: ItemsMatcher plugin for ArchiSteamFarm.
Upstream URL: https://github.com/JustArchiNET/ArchiSteamFarm
Licenses: Apache-2.0
Submitter: Gilrain
Maintainer: Gilrain
Last Packager: Gilrain
Votes: 24
Popularity: 0.51
First Submitted: 2016-04-02 13:31 (UTC)
Last Updated: 2024-12-06 20:21 (UTC)

Pinned Comments

Gilrain commented on 2022-11-03 08:45 (UTC)

Potential breaking change: the service file security has been tightened. If you altered it any way on your machine, you might not be able to start ASF.

You can debug the problem introduced with SystemCallFilter, by following https://unix.stackexchange.com/a/681075

Gilrain commented on 2021-10-02 14:02 (UTC)

Starting with 5.1.4.0-1, the custom service files provided with this package have been replaced with the one upstream.

It uses a EnvironmentFile in /etc/asf to point to the right dir (remember, you want n-1 from asf config folder).

It also serves to populate the user and home folder for the daemon.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »

Gilrain commented on 2017-10-16 18:17 (UTC)

@charlesmilette. I can't reproduce this behavior. Please check that you have all three .NET packages installed (dotnet-sdk-2.0, dotnet-runtime-2.0 and dotnet-host).

sylveon commented on 2017-10-15 17:59 (UTC)

Having issues with systemd when starting the service: $ sudo systemctl restart asf $ systemctl status asf ● asf.service - ArchiSteamFarm Service Loaded: loaded (/usr/lib/systemd/system/asf.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2017-10-15 13:53:54 EDT; 2s ago Docs: https://github.com/JustArchi/ArchiSteamFarm/wiki https://justarchi.github.io/ArchiSteamFarm/ Process: 20635 ExecStart=/usr/bin/dotnet /usr/lib/asf/ArchiSteamFarm.dll --server --path=/var/lib/asf (code=exited, status=226/NAMESPACE) Main PID: 20635 (code=exited, status=226/NAMESPACE) Oct 15 13:53:54 Humble-Huckleberry systemd[1]: Started ArchiSteamFarm Service. Oct 15 13:53:54 Humble-Huckleberry systemd[20635]: asf.service: Failed to set up mount namespacing: No such file or directory Oct 15 13:53:54 Humble-Huckleberry systemd[20635]: asf.service: Failed at step NAMESPACE spawning /usr/bin/dotnet: No such file or directory Oct 15 13:53:54 Humble-Huckleberry systemd[1]: asf.service: Main process exited, code=exited, status=226/NAMESPACE Oct 15 13:53:54 Humble-Huckleberry systemd[1]: asf.service: Failed with result 'exit-code'. But which tells me that in fact, /usr/bin/dotnet does exist.

Gilrain commented on 2017-07-09 10:23 (UTC)

@thefallenrat Empty trailing line removed. Will update shortly. Thanks for reporting it.

thefallenrat commented on 2017-07-07 23:30 (UTC) (edited on 2017-07-07 23:37 (UTC) by thefallenrat)

Please remove the added empty line in '/usr/lib/sysusers.d/asf.conf'. Without this sysusers failed to set up the entry ....

miguelangellv commented on 2017-01-11 15:09 (UTC) (edited on 2017-01-11 15:09 (UTC) by miguelangellv)

Throw error that config folder does not exists. I make a /opt/asf/config and set 666 permision and works fine.

benutzer193 commented on 2016-11-06 15:01 (UTC) (edited on 2016-11-06 15:07 (UTC) by benutzer193)

I'd like to make a suggestion: If you add a custom NLog.config file you could specify a custom folder for the log file. This would allow to set the path for the log file to /var/... and the config path (--path=) to /etc/asf/ or ~/.asf. For information on NLog, see here: https://github.com/JustArchi/ArchiSteamFarm/wiki/Logging. You can specify the folder with the fileName option, e.g.: <target xsi:type="File" [...] fileName="/var/log/asf_log.txt" layout="..." />

Gilrain commented on 2016-08-05 16:30 (UTC)

WARNING: For the next update (v2.1.3.9-1), the package expected path for the config folder will be /var/lib/asf/config instead of /opt/asf/config. The move will be handled automatically and a warning displayed after the upgrade. The systemd services will be modified as such, but /usr/bin/asf will not include the --path argument (as before), hence you will need to launch asf with the correct argument(s) to suit your needs (e.g. 'asf --path=/var/lib/asf'). Please adjust your habits accordingly. (/var was chosen because the --path argument includes dynamic files.)

JustArchi commented on 2016-07-24 21:28 (UTC)

@sud_crow It should be done on package level. ASF as a program is flexible and possible to adapt to user environment and needs, but those needs should be specified above - in script, systemd file, or by yourself. I'm not trying to outsmart you in the code and guess better what you want - because I don't know better what you want. @Gilrain already added a script which runs ASF - it's enough to do "mkdir -p $HOME/.asf" and append "--path=$HOME/.asf" to it. Mkdir could be done even in post-install script, and config could be put there out-of-the-box after installation. It's really easy to implement with switch that exists now. I'm always happy to add extra code that makes it possible for users and package maintainers to integrate ASF with their OS and needs better, but the actual logic of where you want to keep your configs should be implemented on higher level - ASF's job is to accept --path parameter and search for config directory in that place.

Gilrain commented on 2016-07-24 18:50 (UTC)

It would be simpler to just extract the archive to your home folder and run it from there or use symlinks…

« First ‹ Previous 1 2 3 4 5 6 7 8 Next › Last »