Difference between revisions of "Talk:Systemd"

From ArchWiki
Jump to: navigation, search
(remove one closed discussion)
(GNOME 3.6 issues inhibited commands)
(34 intermediate revisions by 10 users not shown)
Line 1: Line 1:
== <s> Lack of internet connection using static ip address without netcfg or NetworkManager</s> ==
 
 
See [[Systemd#A_pure_systemd_installation]] it instructs to remove the initscripts package.  When doing so take care not to use the -s option  of pacman with -R as it removes the iproute2 package also unless you have another package with iproute2 as a dependency.
 
 
Safe:
 
pacman -R initscripts
 
 
 
pacman -Rn initscripts
 
 
 
Not safe when iproute2 will also be removed:
 
pacman -Rs initscripts 
 
 
 
pacman -Rns initscripts
 
 
-- [[User:imatechguy|imatechguy]] ([[User talk:imatechguy|talk]]) 00:28, 11 Oct 2012 (UTC)
 
* It is fixed. iproute2 is in {{grp|base}} group now. Close.
 
:-- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 02:19, 18 October 2012 (UTC)
 
:* Only the {{Pkg|iproute2}} build in [testing] is in the base group. It's been in [testing] for nearly a week, so hopefully it'll be released soon.
 
::-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 16:19, 21 October 2012 (UTC)
 
 
 
== Display manager fails to load with fast SSD ==
 
== Display manager fails to load with fast SSD ==
  
Line 28: Line 7:
  
 
Just a tip for SSD users, not sure if it should be added to the page or not.<br> --[[User:Steev|Steev]] ([[User talk:Steev|talk]]) 16:59, 2 September 2012 (UTC)
 
Just a tip for SSD users, not sure if it should be added to the page or not.<br> --[[User:Steev|Steev]] ([[User talk:Steev|talk]]) 16:59, 2 September 2012 (UTC)
* This is a general problem that needs to be solved in the display manager. GDM already implements the bits for the [http://cgit.freedesktop.org/systemd/systemd/commit/?id=f1a8e221ecacea23 CanGraphical] flag.
+
:This is a general problem that needs to be solved in the display manager. GDM already implements the bits for the [http://cgit.freedesktop.org/systemd/systemd/commit/?id=f1a8e221ecacea23 CanGraphical] flag.
 
:-- [[User:Falconindy|Falconindy]] ([[User talk:Falconindy|talk]]) 21:34, 2 September 2012 (UTC)
 
:-- [[User:Falconindy|Falconindy]] ([[User talk:Falconindy|talk]]) 21:34, 2 September 2012 (UTC)
  
== Hibernation with systemd ==
+
== <s> Hibernation with systemd </s> ==
  
 
The hibernation section should be considered a hack since systemd does not directly handle the backend that handles power management. Systemd uses the Upower interface to handle such requests<br>-- [[User:Yungtrizzle|Yungtrizzle]] ([[User talk:Yungtrizzle|talk]]) 06:25, 10 October 2012‎
 
The hibernation section should be considered a hack since systemd does not directly handle the backend that handles power management. Systemd uses the Upower interface to handle such requests<br>-- [[User:Yungtrizzle|Yungtrizzle]] ([[User talk:Yungtrizzle|talk]]) 06:25, 10 October 2012‎
  
== Removing rc.local ==
+
:I talked about hibernation process with Lennart Poettering and he said that systemd-hibernate does only "echo disk > /sys/power/state" . As  far as i can see, it works perfectly with tuxonice, since it seems it is now using the same userspace API as kernel hibernation; so it works even without hibernate-script installed (i use it without that package).
 +
:-- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 13:54, 24 October 2012
 +
 
 +
:: what is the #Hibernation section all about anyway? It makes it sound like you need to use uswsusp to hibernate while it should work out of the box just fine. It doesn't explain at all why you would want to use uswsusp instead of the default command. I don't use hibernate nor do I know what uswsusp actually does, so what am I missing here?
 +
::-- [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 15:12, 25 October 2012 (UTC)
 +
 
 +
:::I agree with 65kid. In fact, systemctl hibernate works out of the box (it only does an "echo disk...", nothing else). We don't need uswsusp at all. I tried with stock arch kernel and it works.
 +
:::-- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 11:24, 26 October 2012
 +
 
 +
::::Then I suggest that - unless someone explains why you would want to use uswsusp - we remove this whole section because it is nothing but confusing. This article is already way too big to waste text on something that doesn't seem to make any sense.
 +
::::-- [[User:65kid|65kid]] ([[User talk:65kid|talk]]) 10:10, 26 October 2012 (UTC)
 +
 
 +
::::: I went ahead and removed the irrelevant information from the page, moving it to [[Uswsusp]]. I also added a note pointing readers there if they want to use another backend for suspending or hibernating.
 +
:::::-- [[User:Ifaigios|Ifaigios]] ([[User talk:Ifaigios|talk]]) 18:16, 26 October 2012 (UTC)
 +
 
 +
:::::: Hey [[User:Nierro|Nierro]], do {{ic|systemctl hibernate}} and {{ic|systemctl suspend}} really do different things on your box? In my setup (linux-pf, systemd 195-2), if I do the latter, my box is also in suspend mode, meaning that my power button is glowing on and off and I don't see grub after pressing the power button again but are back to my desktop almost immediately. To me, it rather seems as if {{ic|systemctl hibernate}} goes into hybrid mode?
 +
::::::-- [[User:Jakobh|jakobh]] [[User talk:Jakobh|✉]]  10:07, 29 October 2012 (UTC)
 +
 
 +
:::::: Got an answer to the question on the systemd mailing list now: [http://lists.freedesktop.org/archives/systemd-devel/2012-October/007245.html Link]
 +
::::::-- [[User:Jakobh|jakobh]] [[User talk:Jakobh|✉]]  17:56, 30 October 2012 (UTC)
 +
 
 +
== <s> GNOME 3.6 issues inhibited commands </s> ==
 +
It seems that GNOME 3.6 now issues the necessary "inhibited" commands, at my system now doesn't suspend twice with the standard configuration anymore. However I'm not familiar enough with the whole concept to be absolutely sure, so I won't update the page itself. Maybe someone with more competence regarding the inhibited commands can confirm this and edit the page?<br>
 +
-- [[User:Johnpatcher|Johnpatcher]] ([[User_talk:Johnpatcher|talk]]) 00:34, 31 October 2012 (UTC)
 +
: Inhibited note is added. Close. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 01:42, 12 November 2012 (UTC)
 +
 
 +
== Should we add a note about CUPS under 'Transitioning from initscripts to systemd'? ==
 +
Are there any more sockets that change?
  
It isn't clear how to get rid of rc.local.  It would be useful to include this statement from the forum discussion in moving from a mixed system to a pure system:
+
Copied from the CUPS wiki:
  
Go through {{ic|/etc/rc.local}} and {{ic|/etc/rc.local.shutdown}} and turn them into service files (or, if you intend to keep them as they are, copy {{ic|/usr/lib/systemd/system/rc-local{,.shutdown}.service}} to {{ic|/etc/systemd/system/}}).<br>--‎ [[User:Myshkin|Myshkin]] ([[User talk:Myshkin|talk]]) 00:21, 13 Oct 2012
+
...
  
== Replacing ConsoleKit with systemd-logind -> networkmanager ==
+
Systemd uses a different CUPS socket file located at:
  
As of {{pkg|networkmanager}} 0.9.6.0-2 in [extra] we do no more have to recompile it with systemd support from [[ABS]], is this right? So the note should be upgraded.
+
/usr/lib/systemd/system/cups.socket
Am i missing anything?<br> -- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 09:31, 15 October 2012
+
  
* 0.9.6.0-2 in [extra] was compiled on 2012-09-19 and the change to systemd was on 2012-09-29, so as far as I can see, it still needs to be recompiled. https://projects.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/networkmanager&id=c34580e6e35b9e87f7dc27f360507143d4fd9106
+
The default CUPS socket file is located at:
:[[User:65kid|65kid]] ([[User talk:65kid|talk]]) 20:00, 15 October 2012 (UTC)
+
  
:*Damn, you're right. I did not see that pkgrel=3 while we are still using -2. Sorry, it means i'm still using my recompiled package, while i thought i was using the [extra] one.
+
/var/run/cups/cups.sock
::-- [[User:Nierro|Nierro]] ([[User talk:Nierro|talk]]) 16:35, 15 October 2012
+
  
== Removing systemd-sysvcompat ==
+
Edit {{ic|/etc/cups/cupsd.conf}} and {{ic|/etc/cups/client.conf}} as root to use the systemd socket instead of the default.  Make sure to restart CUPS when you are done:
  
So I was thinking: lets go all the way and remove systemd-sysvcompat. After some scary moments I found out {{ic|init<nowiki>=</nowiki>/usr/lib/systemd/systemd}} has to be enabled since otherwise there is nothing to boot into. I also noticed this removes the reboot and poweroff commands ( {{ic|systemctl {reboot,shutdown<nowiki>}</nowiki>}} replace these).
+
# systemctl restart cups
  
Now, is this the recommended way to go in the future, or should everyone keep systemd-sysvcompat installed?<br>-- [[User:Lonaowna|Lonaowna]] ([[User talk:Lonaowna|talk]]) 23:56, 20 October 2012 (UTC)
+
...
 +
<br>
 +
-- [[User:JKAbrams|JKAbrams]] 5 November 2012
 +
:This sounds more like a {{pkg|cups}} packaging bug that should just be fixed.
 +
:-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 01:11, 8 November 2012 (UTC)
 +
::It sounds like someone who doesn't have a clue about systemd. That cups.socket file is a systemd unit file of type socket, which contains the location of the socket file for CUPS (and that is still /var/run/cups/cups.sock).
 +
::[[User:Raynman|Raynman]] ([[User talk:Raynman|talk]]) 22:49, 9 November 2012 (UTC)

Revision as of 01:42, 12 November 2012

Display manager fails to load with fast SSD

I was having a problem with my display manager (LXDM) not loading on my laptop, which has a Sandisk Extreme SSD. Xorg.log would show errors like "No screens found."

I eventually figured out that the problem was that my computer was booting so fast that KMS didn't have enough time to kick in before X was started. I solved by adding the KMS driver (i915 in my case) to the initramfs.

Just a tip for SSD users, not sure if it should be added to the page or not.
--Steev (talk) 16:59, 2 September 2012 (UTC)

This is a general problem that needs to be solved in the display manager. GDM already implements the bits for the CanGraphical flag.
-- Falconindy (talk) 21:34, 2 September 2012 (UTC)

Hibernation with systemd

The hibernation section should be considered a hack since systemd does not directly handle the backend that handles power management. Systemd uses the Upower interface to handle such requests
-- Yungtrizzle (talk) 06:25, 10 October 2012‎

I talked about hibernation process with Lennart Poettering and he said that systemd-hibernate does only "echo disk > /sys/power/state" . As far as i can see, it works perfectly with tuxonice, since it seems it is now using the same userspace API as kernel hibernation; so it works even without hibernate-script installed (i use it without that package).
-- Nierro (talk) 13:54, 24 October 2012
what is the #Hibernation section all about anyway? It makes it sound like you need to use uswsusp to hibernate while it should work out of the box just fine. It doesn't explain at all why you would want to use uswsusp instead of the default command. I don't use hibernate nor do I know what uswsusp actually does, so what am I missing here?
-- 65kid (talk) 15:12, 25 October 2012 (UTC)
I agree with 65kid. In fact, systemctl hibernate works out of the box (it only does an "echo disk...", nothing else). We don't need uswsusp at all. I tried with stock arch kernel and it works.
-- Nierro (talk) 11:24, 26 October 2012
Then I suggest that - unless someone explains why you would want to use uswsusp - we remove this whole section because it is nothing but confusing. This article is already way too big to waste text on something that doesn't seem to make any sense.
-- 65kid (talk) 10:10, 26 October 2012 (UTC)
I went ahead and removed the irrelevant information from the page, moving it to Uswsusp. I also added a note pointing readers there if they want to use another backend for suspending or hibernating.
-- Ifaigios (talk) 18:16, 26 October 2012 (UTC)
Hey Nierro, do systemctl hibernate and systemctl suspend really do different things on your box? In my setup (linux-pf, systemd 195-2), if I do the latter, my box is also in suspend mode, meaning that my power button is glowing on and off and I don't see grub after pressing the power button again but are back to my desktop almost immediately. To me, it rather seems as if systemctl hibernate goes into hybrid mode?
-- jakobh 10:07, 29 October 2012 (UTC)
Got an answer to the question on the systemd mailing list now: Link
-- jakobh 17:56, 30 October 2012 (UTC)

GNOME 3.6 issues inhibited commands

It seems that GNOME 3.6 now issues the necessary "inhibited" commands, at my system now doesn't suspend twice with the standard configuration anymore. However I'm not familiar enough with the whole concept to be absolutely sure, so I won't update the page itself. Maybe someone with more competence regarding the inhibited commands can confirm this and edit the page?
-- Johnpatcher (talk) 00:34, 31 October 2012 (UTC)

Inhibited note is added. Close. -- Fengchao (talk) 01:42, 12 November 2012 (UTC)

Should we add a note about CUPS under 'Transitioning from initscripts to systemd'?

Are there any more sockets that change?

Copied from the CUPS wiki:

...

Systemd uses a different CUPS socket file located at:

/usr/lib/systemd/system/cups.socket

The default CUPS socket file is located at:

/var/run/cups/cups.sock

Edit /etc/cups/cupsd.conf and /etc/cups/client.conf as root to use the systemd socket instead of the default. Make sure to restart CUPS when you are done:

# systemctl restart cups

...
-- JKAbrams 5 November 2012

This sounds more like a cups packaging bug that should just be fixed.
-- Jstjohn (talk) 01:11, 8 November 2012 (UTC)
It sounds like someone who doesn't have a clue about systemd. That cups.socket file is a systemd unit file of type socket, which contains the location of the socket file for CUPS (and that is still /var/run/cups/cups.sock).
Raynman (talk) 22:49, 9 November 2012 (UTC)