Skip to main content
Topic: Why is there a /run/sysemd folder?! (Read 895 times) previous topic - next topic
0 Members and 3 Guests are viewing this topic.

Why is there a /run/sysemd folder?!

Enjoying my artix install, I went to symlink something to enabme the service, bam

/run/systemd directory exists on my machine. why?!
recursive ls of the directory:

Code: [Select]
/run/systemd:
inhibit  machines  seats  sessions  users

/run/systemd/inhibit:
1  1.ref  3  3.ref

/run/systemd/machines:

/run/systemd/seats:
seat0

/run/systemd/sessions:
1  1.ref

/run/systemd/users:
1000

Is it safe to remove it?  i want it banished from my ssd.....

Re: Why is there a /run/sysemd folder?!

Reply #1
I believe this is for elogind sessions, if you notice there is a seats dir in the /run/systemd folder.

Re: Why is there a /run/sysemd folder?!

Reply #2
Is it safe to remove it?  i want it banished from my ssd.....
You can install seatd. I have seatd on my own desktop and laptop, and I don't have /run/systemd. Caveat: I use no-DM, no-DE dwm, with for example, pure ALSA for sound, so I don't need elogind features not present in seatd.

Re: Why is there a /run/sysemd folder?!

Reply #3
/run/systemd is created by elogind (the default session manager on Artix). It's there for compatibility with apps written with systemd in mind and because, well, elogind is pretty much a fork of systemd itself.

For it to be removed and not come back, you'd need to switch session managers (say, to seatd), though this is not without sacrifice (for instance, none of the major desktop environments support not using systemd or elogind).