Package Details: asf

Git Clone URL: (read-only, click to copy)
Package Base: asf
Description: Steam cards farmer.
Upstream URL:
Licenses: Apache
Submitter: Gilrain
Maintainer: Gilrain
Last Packager: Gilrain
Votes: 17
Popularity: 1.77
First Submitted: 2016-04-02 13:31
Last Updated: 2020-01-16 08:59

Dependencies (6)

Required by (1)

Sources (6)

Latest Comments

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

sylveon commented on 2017-10-15 17:59

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

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

thefallenrat commented on 2017-07-07 23:30

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

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

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:
You can specify the folder with the fileName option, e.g.:
<target xsi:type="File" [...] fileName="/var/log/asf_log.txt" layout="..." />

JustArchi commented on 2016-07-24 21:28


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

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

sud_crow commented on 2016-07-24 16:53

@JustArchi thank you for taking the time to answer here. I was the one who asked about the path setting in Github by the way.

I was going to post a few extra suggestions in Github regarding this, maybe having the default behaviour to be compliant with XDG specification[1], I don't really know if this should be implemented at package level or the application level. Probably for the package level the application should have a few parameters to allow for it (maybe with --path is enough).

I do think that running the application (if it is installed at system level) should check for the ~/.config/asf/config folder of the user running it, if its not found, fallback to the $INSTALLED_DIR/config, which might or might not work. The --path flag should be specified at runlevel when you want an exception (for ex. to run a profile found in another folder than the default in your home). Please tell me if this makes sense.

Example with user bob.

bob@archlinux ]$ asf

Should search for the config files in:


I rather run it as my own user, I don't like having services running in the background unless needed, and as I'm not a "24/7 farmer", I didn't think of making a systemd unit. I understand the reason to do it though. Thanks for the heads up.

Anyway, I didn't like the service saving user data to /opt/asf/config (particularly if you are in a multi user environment), that's why I asked about the config path. It would be great if you continue the issue to allow for the changes needed for the application to be package-friendly.

Thanks to both of you for the attention to the issue.

ps. forgot links:

Gilrain commented on 2016-07-24 08:08

Your workaround is valid, though not recommended. I would advise "sudo -u asf -g asf -H /usr/bin/asf" for interactive operations.

For now the package default mode of operation is to execute asf as a --server through a systemd service. Since farming takes hours, I thought it was sensible to set it and forget its existence. Any other way requires some expertise on the part of the end user (which should not blindly install AUR packages anyway).

Thank you for the explanation. I missed that issue during my cursory look at the repo.

JustArchi commented on 2016-07-24 00:35

It was retroactively changed to not raise false-positive for Windows users due to including ASF-Service.exe in the zip that uses different repacking method to stay compatible with being run via service. For some reason Windows Defender doesn't like ILRepack that is being used, hence I had to remove the service from default zip. See:

Starting with ASF there will be special --path argument supported by ASF that will tell it where to look for config directory. This will allow package maintainer (Gilrain) to use it by executing ASF.exe with --path=/home/current_user/.asf, --path=$HOME/.asf (if $HOME is supported) or similar. That part is up to package maintainer though and how he wants to use ASF in AUR, I can only implement extra features to make it easier for you.