Skip to main content ↑ ↓
Topic: dinit for volumeicon? (Read 1204 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: dinit for volumeicon?

Reply #15 –
Is  the service in ~/.config/dinit.d/?

You can try with the absolute path:
Code: [Select]
env-file = /home/n00b/.config/dinit.d/environment

Re: dinit for volumeicon?

Reply #16 –
Quote
Is  the service in ~/.config/dinit.d/?
Code: [Select]
$:~/.config/dinit.d$ ls
boot.d  enviroment

So yes?

/home/USER/.config/dinit.d/enviroment worked

Code: [Select]
$: dinitctl list
[[+]     ] boot
[{+}     ] system
[{+}     ] dbus (pid: 875)
[{+}     ] pipewire (pid: 879)
[{+}     ] pipewire-pulse (pid: 881)
[{+}     ] wireplumber (pid: 880)
[{+}     ] volumeicon (pid: 16945)

Thank you @kiblaster
I will edit the wiki.

The unurgent question remains, should volumeicon have a dinit?
Is it better in Moksha startup?
How does one make that call?
Finally,
Quote
If you need services that use the "display" at the moment you cannot use turnstile with startx.
I think this is no longer true and "display" needs have a simple fix, yes?

Re: dinit for volumeicon?

Reply #18 –
I guess the problem is using the user dir in a user services file makes it user specific, yes?

Re: dinit for volumeicon?

Reply #19 –
I mean is the volumeicon service file in the "~/.config/dinit.d/ folder"?
Near environment file otherwise it won't work of course.
I see that it is not because because of the wiki.
Instead of editing system file in /etc copy the service in ~/.config/dinit.d/.
Or in this case create it directly there.
So far services in the repo do not have DISPLAY at some point this may be included and therefore environment could be placed somewhere in /etc and thus you can refer to it using the absolute path /etc/path/file.

Note I had a typo and I always wrote environment wrong now edited.

Re: dinit for volumeicon?

Reply #20 –
Quote from: kiblaster – on
I mean is the volumeicon service file in the "~/.config/dinit.d/ folder"?
Near environment file otherwise it won't work of course.
Of course. derp
Quote from: kiblaster – on
I see that it is not because because of the wiki.
Instead of editing system file in /etc copy the service in ~/.config/dinit.d/.
Or in this case create it directly there.
done... and when the service file is placed in ~/.config/dinit.d/
Code: [Select]
env-file = environment
works perfectly.
Quote from: kiblaster – on
So far services in the repo do not have DISPLAY at some point this may be included and therefore environment could be placed somewhere in /etc and thus you can refer to it using the absolute path /etc/path/file.

First, thank you for your patience with me.

It occurs to me  that dinit services will not typically need DISPLAY,  Is that true?
Perhaps only turnstile services would, does that make sense?

Perhaps an addon to support DISPLAY in turnstile? But I know nothing.

Are these reasonable lessons I could take away from this?
1) It seems the sound stuff goes in turnstile, as it is DE independent.

2) volumeicon should start with Moksha, as it is DE dependent.

3) But the blueman-applet, which I need started, probably is DE independent, so could use a turnstile service? And might be user independent?

Thank you again.

Re: dinit for volumeicon?

Reply #21 –
Services that use the DISPLAY will need it.
Something that runs in the background does not.
(This happens in turnstile because DISPLAY var is not set).

You can start dinit services in you DE autostart so that they will be  DE independent.
Code: [Select]
dinitctl --user start volumeicon

Re: dinit for volumeicon?

Reply #22 –
Quote from: kiblaster – on

You can start dinit services in you DE autostart so that they will be  DE independent.
Code: [Select]
dinitctl --user start volumeicon

I was thinking the init should start the DE. But I am often wrong.
How do you pick who starts who?

Re: dinit for volumeicon?

Reply #23 –
I do not think that the DE can start the init.
What's the problem?