All my ducks seem to be in order and the correct configs in the right place. But i keep getting this message. As you can see the file exists. It is not empty, but systemctl cannot find it. Any help would be very very appreciated.

•fedora 40 xfce spin •kernel 6.9.9.200 •fucking chromebook

0 points

I think you need to set the execute bit on your service file.

sudo chmod +x <your service file>

permalink
report
reply
5 points

Nope, they should not be executable.

permalink
report
parent
reply
-15 points

Lennart’s Cancer strikes again.

permalink
report
reply
-5 points

Take my upvote.

permalink
report
parent
reply
2 points

?

permalink
report
parent
reply
5 points

It’s just an old rant, some people can’t get over the fact systemd exists

permalink
report
parent
reply
3 points

I don’t know much about systemd, but i assume the file should be owned by root? It looks like it isn’t, so try chown root:root spotifyd.service

permalink
report
reply
2 points

Nope, don’t run Spotify as root. That’s a bad idea.

permalink
report
parent
reply
2 points
*

I’m not sure spotifyd is just spotify (Edit: I checked, its some kind of spotify client meant to be run as a daemon? No idea what permissions that needs)

And the user that executes a service isn’t determined by who owns the service file, there is a user option in the service config

permalink
report
parent
reply
2 points

I’ll try that when i get back to it.

permalink
report
parent
reply
18 points

Why are you running Spotify as a service? I don’t think that’s what they mean by SaaS!

permalink
report
reply
3 points
*

Where is the service file located on your system?

Did you create it with sudo systemctl edit --force --full, or did you use a text editor (or was it automatically generated by an installer)?

permalink
report
reply
2 points
*

I made the file this way.

Cd /etc/systemd/system && touch spotifyd.service

Sudo nano -l spotifyd.service

Wrote, saved and quit. Then the commands above. I havent tried sudo systemctl edit —force —full

permalink
report
parent
reply
3 points

My knowledge is limited, but you should be using that command to create service files, from what I understand. There’s some extra stuff that happens in the background (like putting symlinks in the correct places) after you write out the changes using that command.

permalink
report
parent
reply
11 points
*

You surely need to explicitly cause systemd to process changes after writing to a file. I would be very surprised if it reacted to file system changes automatically.

For example, I recall that I need to execute a command like systemctl daemon-reload after editing a service file: https://unix.stackexchange.com/questions/364782/what-does-systemctl-daemon-reload-do

You might get more useful information from resources like https://www.man7.org/linux/man-pages/man1/systemctl.1.html

permalink
report
parent
reply

Linux

!linux@lemmy.ml

Create post

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

  • Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
  • No misinformation
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

Community stats

  • 6.7K

    Monthly active users

  • 6.7K

    Posts

  • 182K

    Comments