Changing to Systemd

Mr Green · 2012-08-09 04:06:25

With Arch moving towards systemd rc.conf is not used much any more.

The file I posted is standard rc.conf [pacman update]

For the time being rc.conf is supported [for now!]

handy · 2012-08-09 05:26:38

When the change came I just referred to this page & made the appropriate modifications:

https://wiki.archlinux.org/index.php/Rc.conf

Whilst writing this reply I made the following change to my rc.conf:

#-> HARDWARE <-

### MODULES=(sg r8168) <<<--- These two are now called
### via .conf files located in /etc/modules-load.d

This way at least if I forget where I put them I'll find this pointer which will eventually drum the change into my obstinate & recalcitrant brain.

Mr Green · 2012-08-09 06:02:05

I can only say that I still use old style rc.conf on my dekstop, still not ready to go systemd yet.

Having settings in one place seems to make more sense than link this with that.

But the Arch KISS of old is long gone...........

oliver · 2012-08-09 06:32:36

Mr Green wrote:

I can only say that I still use old style rc.conf on my dekstop, still not ready to go systemd yet.
Having settings in one place seems to make more sense than link this with that.
But the Arch KISS of old is long gone...........

Wasn't the old style rc.conf one of Arch's selling points? When I first considered moving from Gentoo (thanks to a thread on the gentoo forums) people were very satisfied with the ease of use of it.

handy · 2012-08-09 06:36:46

I too had that feeling of a certain loss of the "Arch KISS" when rc.conf got broken up. I was perfectly happy with the old way.

I haven't read about it to confirm, but hopefully what "they" are working on will turn into an even simpler system, in that it will look after more low level stuff "reliably" without need for user input. "?"

To do such is not an easy or quick job. There have been a lot of changes in Arch inside of the last 12 months. I expect that these changes have been stepping along to a pre-ordained plan., if so, that would strengthen my hope that a happy, stable plateau that makes all of these changes worthwhile is where we will arrive...

I'm not particularly unhappy with the changes, it is just that I personally haven't needed any of them.

Mr Green · 2012-08-09 10:10:27

Why can you not have a single configuration file? Its in one place all there not spread linked hidden pushed out covered ....

I am not fully up with systemd my take on it is that it improves boot time [but then I could be wrong and often am!]

Guess initscripts are so 2009

Mr Green · 2012-08-09 10:12:07

https://bbs.archlinux.org/viewtopic.php?id=145740

Mr Green · 2012-08-09 10:25:54

Think at some point I need to sit down and work my way through this:

https://wiki.archlinux.org/index.php/Sy … stallation

Some people seem to think it is easier than it looks.

Maybe I need to think about bringing it to ArchBang live [more fun!]

Might even improve boot times who knows.

Have tried it on a virtual machine thought I was booting a certain genpoo .....

Changes are always bad they put you out of your comfort zone. Fire up qemu or virtualbox get yourself a virtual Arch guest and break that. You can make all the mistakes you want without causing any pain when your system does not start.

handy · 2012-08-12 19:04:47

A couple of days ago I edited out all except the DAEMONS() line in my rc.conf, ... my machine still boots (a few seconds slower) & my network functions fine.

I guess I'll get around to moving over to systemd (& grub2) in the near future as it would seem that both rc.conf & grub(1) have both become redundant.

I may make my rc.conf purely a document with the sole function of refreshing my memory on where all of the bits that used to be in "it" are now.

Last edited by handy (2012-08-12 19:06:19)

ArchVortex · 2012-08-13 00:22:14

I too, am one of the Gentoo guys who was enticed over to Arch with its KISS principle and rc.conf file. Moving stuff back into different files is no big deal to me because Gentoo is already like that. Whatever. I'll get over it. The thing I'm missing is my ugly hack scripts and 5 second slower boot times.

Mr Green · 2012-08-13 00:58:52

https://wiki.archlinux.org/index.php/Im … erformance

Or get an SSD drive

handy · 2012-08-13 02:13:14

I'm in the process of converting over to systemd, primarily using this page: https://wiki.archlinux.org/index.php/Sy … tion_files

As I write this I'm at the point where the following services (DAEMONS) are installed & most are working, after setting them up to auto-start every boot by using the following command from root:

 systemctl enable <service>

Here are the service names that I've used thus far:

Network (Internet): dhcpcd@.service
NFS: rpc-statd.service
Cron: cronie.service
GPM: gpm.service
HddTemp: hddtemp.service
Sensors: lm_sensors.service
SSH: sshd.service & sshdgenkeys.service

I can play a video off of my NFS connected NAS, with sound, without loading ALSA.

The things that I know don't work properly yet:

I have to use my username & password then enter startx, to get Openbox to load & open. My setup was such that Openbox would just appear. I think this is to do with the changes to run levels. I'll look into that.

Even though the gpm.service is installed I can't use my mouse in ROXterm. This is very likely a ROXterm problem. I'll just check & see if Sakura can handle the mouse... it can't, so this problem looks to be in my system.

The Tint2 strip is where it normally is, though there are no icons displaying on it, & my clock is not functioning & is showing a very wrong time [edit:] I just checked & my system time & date is correct.[/edit], & I can't change desktops using the 6 panels that I have Tint2 display. So I've got some work to do there.

The three app's (ROXterm, Worker & Firefox) which are set to autostart on their set desktops don't? When I manually start them they each start on their set desktop though...

My two conky panels are nowhere to be seen.

All in all its not too bad considering the amount of changes that have been made. Very few of the Arch Wiki pages dealing with the various packages that get DAEMONized have been bought up to date with this dramatic set of Arch system(d) changes. Also the table listing the Initscripts (DAEMONS) <-> Systemd alternatives is I'm sure nowhere near up to date with the "unit" files that people have been creating.

The table is here: https://wiki.archlinux.org/index.php/Da … of_Daemons

I'll post some more when I make some headway on some of these problems.

Last edited by handy (2012-08-13 02:26:42)

Mr Green · 2012-08-13 02:33:56

Try

https://wiki.archlinux.org/index.php/Sy … er_systemd

Sure I had slim working ok but may need to check as I was testing on a virtual machine

handy · 2012-08-13 03:51:48

Thanks Mr Green, I'll have a look where you suggested. I don't use a Slim or the likes, I've been using something like this:

https://bbs.archlinux.org/viewtopic.php … 40#p439440

On another note, I've found that setting up Tint2 again from scratch has it working OK. The traydevice & udisksvm pair are running but they aren't functioning Tint2, nor is my volume control is also not appearing in Tint2 at this stage.

I'll keep on chuggin' along through this lot. It should keep me busy for a while I think.

Mr Green · 2012-08-13 04:51:11

What have you got in .xinitrc ? is dbus running?

handy · 2012-08-13 06:45:12

.xinitrc:

#!/bin/bash
# ~/.xinitrc

# export BROWSER=firefox-aurora
# export DE=xfce

# following is a workaround to make ctrl-alt-bakspace close X session:
setxkbmap -option terminate:ctrl_alt_bksp &

# following line should automatically turn on the num lock when X starts:
numlockx &

# the following sets the path for X11 so it can use the Terminus fonts:
xset +fp /usr/share/fonts/local
xset fp rehash

# trying to get volti to land in the Tint2 systray:
volti &

# starts synergys (server) daemon "-d ERROR restricts what gets logged:
#synergys -d ERROR &

# the next line kills a bug where the server screen blanks for a second
# when moving to it from the client (this bug can't last much longer...):
#xset -dpms &

# simple start for openbox:
#exec openbox-session

# following starts dbus & openbox:
exec ck-launch-session dbus-launch openbox-session

dbus is running.

Last edited by handy (2012-08-13 06:49:41)

oliver · 2012-08-13 06:50:23

handy wrote:

I have to use my username & password then enter startx, to get Openbox to load & open. My setup was such that Openbox would just appear. I think this is to do with the changes to run levels. I'll look into that.

You probably had it set in /etc/inittab which is no longer read (take a look if you still have it hanging around)

handy · 2012-08-13 07:16:17

I do still have inittab, I'm doing a bit of ferreting around on this OB startup problem at the moment.

This is what I have before eof in inittab:

# Following causes Openbox to start via ~/.xinitrc when the user logs in:
x:5:once:/bin/su handy -l -c "/bin/bash --login -c startx >/dev/null 2>&1"

I'll take inittab out of the equation & see what happens.

handy · 2012-08-13 07:34:10

inittab makes no difference.

I also found that my tint2 is not functioning properly after its first reboot - it is the same as before - no icons, clock doesn't keep time ...

Mr Green · 2012-08-13 08:04:39

Try running tint2 in terminal see if you get any output. Not sure about volti is there a reason it is not in autostart?

https://wiki.archlinux.org/index.php/Start_X_at_boot

and

https://wiki.archlinux.org/index.php/Sy … er_systemd

Just tested one above and it does startx and openbox but nm-applet is missing though network is working as is volumeicon

oliver · 2012-08-13 08:09:48

handy wrote:

inittab makes no difference.

inittab is no longer read when you move to systemd... you *probably* need to create a new 'service' file with something along the lines of the following in it:

ExecStart=/bin/su handy -l -c "/bin/bash --login -c startx >/dev/null 2>&1"

There's probably one already shared on the arch forums

handy · 2012-08-13 08:23:00

I made a major breakthrough

In trying to get OB to auto-start I first tried this:

https://wiki.archlinux.org/index.php/Au … th_systemd

Which had no visible effect.

Then I resorted to this:

https://wiki.archlinux.org/index.php/Sy … rvice_file

Which worked!!!

The machine shuts down & reboots fine. [edit:] Still have initscripts & sysvinit, when they are removed you must use systemctl reboot or systemctl poweroff , which are much more intelligent than what they supersede. [/edit]

It looks like tint2 is fully functional, including my sound mixer volti & all icons showing as they should.

I also got my two conky panels back & fully functional.

I still can't work with mouse highlighted text in ROXterm, but I'm not complaining. This lot is going much better than I thought it would & the results are coming along fairly quickly too.

The traydevice / udisksvm combo are trying to function but they aren't working right. I'll look into that after a sleep.

Thanks for your suggestions Mr Green, I'm off to bed.

Last edited by handy (2012-08-14 03:34:33)

Mr Green · 2012-08-13 08:29:25

network manger is running but no nm-applet in tint2

dbus-org.freedesktop.NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service

handy · 2012-08-13 17:52:57

Good list of Units you found there Mr Green.

My system seems to be fully functional (more testing needed) apart from udisksvm (which due to the development of both udev & Worker, I don't really need any more anyway) & what seemed to be the mouse in terminal functionality is actually the loss of the ability to use the keyboard shortcuts - ctrl plus x , c , v - so I should be able to get that sorted - it really isn't a mouse (gpm) problem at all.

I've had Worker setup with a couple of buttons that run simple scripts to unmount my NAS & reboot or unmount & cold boot my machine; they are what I always use for the job.

Here is one of the scripts:

#!/bin/bash
if [[ `whoami` != "root" ]];
then
  echo "Must be root to run this script."
  exit
fi
echo "Unmounting NFS volumes."
umount 192.168.1.15:/media
umount 192.168.1.15:/media-2
umount 192.168.1.15:/backup
echo "Unmounting complete, shutting down now."
shutdown -h now

They didn't work once I deleted initscripts & sysvinit (can see that a quick edit would have them functioning again). So I made new buttons using:

sudo systemctl reboot

&

sudo systemctl poweroff

Which quickly unmounted my NFS connected NAS & proceeded to do what they were supposed to do. Which I think is VERY impressive, as in the way things should work.

All in all the more I deal with systemd the greater my depth of appreciation for it.

[edit:] I've disabled traydevice & udisksvm as they are no longer required, & redid the setup of ROXterm's custom keyboard shortcuts & they now function as they should again.

I haven't found anything else that's broken yet.

Last edited by handy (2012-08-13 23:40:53)

Mr Green · 2012-08-13 23:24:55

The NetworkManager.service is simply not there, so will look into that..

Noticed I have a couple of FAILS during boot that I will check out

@Admin note might split topic as its going way off topic!

handy · 2012-08-13 23:45:58

This network section on the Gentoo wiki may be of use to you Mr Green:

http://en.gentoo-wiki.com/wiki/Systemd#Network

I agree, this thread should be split.

Mr Green · 2012-08-14 00:37:48

Static would be handy for server based systems

This is on arch wiki

https://wiki.archlinux.org/index.php/Sy … .28DHCP.29

Just wondered why Network Manager did not work, more to the point why its linked to a file that does not exist!

Mr Green · 2012-08-14 01:00:32

Got a couple of FAILS

syslog and rc.local

systemctl status syslog.socket # Arch news item I think....
systemctl status rc-local.service

[mrgreen@archbang ~]$ systemctl status syslog.socket
syslog.socket - Syslog Socket
	  Loaded: loaded (/usr/lib/systemd/system/syslog.socket; static)
	  Active: inactive (dead)
	    Docs: man:systemd.special(7)
	          http://www.freedesktop.org/wiki/Software/systemd/syslog
	  CGroup: name=systemd:/system/syslog.socket

[mrgreen@archbang ~]$ systemctl status rc-local.service
rc-local.service - /etc/rc.local Compatibility
	  Loaded: loaded (/usr/lib/systemd/system/rc-local.service; static)
	  Active: failed (Result: exit-code) since Tue, 14 Aug 2012 07:58:03 +0100; 59s ago
	 Process: 169 ExecStart=/etc/rc.local (code=exited, status=1/FAILURE)
	  CGroup: name=systemd:/system/rc-local.service

Fixed first syslog by doing this

https://wiki.archlinux.org/index.php/Sy … log_daemon

Second one '#' out lines in rc.local [amixer settings]

handy · 2012-08-14 01:33:23

I went pure systemd, so rc.local no longer exists on my system.

Mr Green · 2012-08-14 01:36:19

I am sort of half way there must read wiki again but can you just remove rc.local and inittab?

nm-applet is not working so may go dhcp route, though for laptops and ArchBang need to figure out how to get it working

So will remove network-manager for now

handy · 2012-08-14 01:46:22

If/when you remove (with pacman) initscripts & sysvinit they take rc.conf , rc.local , inittab & any & all the other files that belong to them.

So if you want to keep any of them back them up or rename them.

Last edited by handy (2012-08-14 01:48:02)

Mr Green · 2012-08-14 01:56:24

I have gone and deleted rc.local now getting FAIL did try to disable service but it did not work....

Will backup rc.conf [though pacman should do that!] and try again

Thanks

Mr Green · 2012-08-14 01:58:32

Ok so removed initscripts and sysvinit now have to fix reboot

Do we get paid for testing Arch linux?

handy · 2012-08-14 02:16:19

LOL

There would be more people fixing it if that was the case.

I want to remove ConsoleKit, but Openbox needs it for oblogout !?

I've posted a question on the Arch forums about that one, as I couldn't dig up anything useful from searching.

If you must still use ConsoleKit, I'm sure that it won't be long before a release of Openbox comes out where you don't have to.

Mr Green · 2012-08-14 02:48:06

On my main desktop I use a pipe menu ... if that is any help

Think the problem is with reboot command ....

https://wiki.archlinux.org/index.php/Sy … th_systemd

You will need to edit /etc/oblogout

systemctl reboot

https://wiki.archlinux.org/index.php/Sy … Management

I will edit oblogout.conf see if it works

Mr Green · 2012-08-14 03:01:36

[settings]
usehal = false

[looks]
opacity = 70
bgcolor = black
buttontheme = oxygen
buttons = cancel, logout, restart, shutdown, lock

[shortcuts]
cancel = Escape
shutdown = S
restart = R
logout = L
lock = K

[commands]
shutdown = sudo systemctl poweroff
restart = sudo systemctl reboot
logout = openbox --exit
lock = slimlock

Maybe?

handy · 2012-08-14 03:06:46

I discovered that oblogout is a plugin script for Ob. So I removed it & then consolekit & rebooted to errors. Had to log in manually but startx failed, more errors.

I realised that I was calling consolekit when I call openbox-session in .xinitrc , so I edited that out & then startx would work.

I'm about to reboot, hoping that there are no more errors... I'll let you know.

handy · 2012-08-14 03:11:59

YES!!!!! It worked, no consolekit, no oblogout & NO ERRORS!

As mentioned in an earlier post, I use Worker to issue my reboot & poweroff commands so I don't have the complications of adding the commands to the Obmenu, which really shouldn't be too hard anyway. & these new systemctl poweroff & reboot commands are SO intelligent & capable - umounting network shares & all for you.

Did I ever tell you that I like this systemd stuff. 8)

Last edited by handy (2012-08-14 03:44:16)

Mr Green · 2012-08-14 05:40:06

Here is what I use in pipe menu [will need editing to suit!]

#!/bin/bash

echo "<openbox_pipe_menu>
<item label=\"Log Out\">
<action name=\"Execute\">
<execute>
openbox --exit
</execute>
</action>
</item>
<item label=\"Reboot\">
<action name=\"Execute\">
<execute>
sudo reboot # change to suit
</execute>
</action>
</item>
<item label=\"Shutdown\">
<action name=\"Execute\">
<execute>
sudo shutdown -h now # change to suit
</execute>
</action>
</item>"
echo "</openbox_pipe_menu>"

Stick in ~/.config/openbox/pipemenus chmod +x obexit.sh [whatever]

Add to menu.xml

<menu execute="~/.config/openbox/pipemenus/obexit.sh" id="pipe" label="Exit"/>

handy · 2012-08-14 17:46:54

As I'm sure you already know Mr Green, without OBlogout, you still get the "Log Out" option in the Ob menu, which closes Ob & lands you at a prompt, from where you have to type in the commands to reboot, poweroff or whatever else takes your fancy.

Your pipe menu certainly makes it easier for those that need it.

Mr Green · 2012-08-14 22:55:44

You could set up an alias for shutdown if you did not want to type out systemctl poweroff each time

handy · 2012-08-15 01:51:19

I don't have to type it out, as I've mentioned previously in this thread, (post_24) I have two buttons configured in Worker to do the job, one says "Shutdown" the other says "reboot".

As previously mentioned (in post_24 with a script displayed) I used to have to use scripts to do the job (in Worker) as I had to umount my NAS NFS shares before shutting down or rebooting. Now with the new systemd commands I don't need the scripts as they umount the shares automatically themselves.

Last edited by handy (2012-08-15 01:52:53)

Mr Green · 2012-08-15 04:46:08

I see, not familiar with worker .... what is your ram usage like now?

handy · 2012-08-15 07:12:14

There are two old pictures of my Arch setup, the 2nd picture on this page is of a previous config' of Worker, I've changed some of the buttons since that screen shot dated 29th December 2011:

http://www.users.on.net/~thehands/my-ve … -arch.html

Any buttons that have a dog-eared top right hand corner also have a right mouse button option underneath.

Worker is not for everybody, but it suits me down to the ground, I was setup for that kind of dirutil by Jonathan Potter's Directory Opus (DOpus) back in my Amiga days.

I'll check on my RAM usage on boot tomorrow & post it here. I have had a LOT of stuff going on in the machine today.

Last edited by handy (2012-08-15 07:13:12)

scjet · 2012-08-15 16:24:39

try this also, if it helps to "ferret" out systemd: http://bbs.archbang.org/viewtopic.php?id=3152
A simple KISS one-file rc.conf "was" Arch, -unfortunately/fortunately Arch is going systemd, beit some sort or another. ?

Last edited by scjet (2012-08-15 16:26:06)

cirrus · 2012-08-21 17:22:17

after going native systemd and removing consolekit i think i see around 50MB shaved off ram usage , which is not to be sniffed at on older hardware . thanks to handy for urging me to remove consolekit.

chris_debian · 2012-09-04 01:51:26

Hi, all.

Just a thought, is it possible to give the user the option whether or not to go down the systemd route, as part of the install, or is systemd so fundamental to everything, that this option would just not be practicable to support?

Thanks,

Chris.

Mr Green · 2012-09-04 02:02:38

You would effectively need two installers/isos, source build is created for isos then copied over to create install.

A netinstall option may help but again two version would be required.

With input from community I am hoping we can meld the two together, use old and new... how practical or possible not sure.

chris_debian · 2012-09-04 02:10:16

Cheers, MG.

Seems like devs are split on this issue and it would be a shame to lose people. Maybe two isos is an option; or as mentioned elsewhere, a fork maybe the way forward, but then the rest of the A! community would have to make a choice, whixh wouldn't benefit anyone.

Perhaps this will becone a 'lilo/ grub > grub/ lilo > lilo is deprecated > what lilo?' situation. EDIT: With the exception of Slack, possibly :-)

Thanks,

Chris.

Last edited by chris_debian (2012-09-04 02:35:27)

ratcheer · 2012-09-08 07:02:19

cirrus wrote:

after going native systemd and removing consolekit i think i see around 50MB shaved off ram usage , which is not to be sniffed at on older hardware . thanks to handy for urging me to remove consolekit.

I just now went this route, as well. However, I had at one time installed xfce4, didn't care for it, and gone back to Openbox. In order to uninstall consolekit, I had to uninstall xfce4. That took me about four levels deep in dependencies, but I finally got it all cleaned out to the point that I could actually remove xfce4 and then consolekit.

Now, notification does not seem to be working. I do not get the temporary box at the top right of the screen when the network connects. I do get an nm-applet icon in my tint2 panel, but if I right-click it and ask it to show connection information, it gives a dialog box that says, "No valid active connections found!", even though I am on the network at this moment or I couldn't be on this site typing this.

What have I probably messed up and how do I go about fixing it?

Tim

PS - Here is a list of the stuff I removed:

[2012-09-08 07:48] removed xfwm4-themes (4.10.0-1)
[2012-09-08 07:48] removed xfce4-power-manager (1.2.0-3)
[2012-09-08 07:48] removed xfce4-mixer (4.8.0-4)
[2012-09-08 07:48] removed terminal (0.4.8-2)
[2012-09-08 07:48] Running 'pacman -R exo thunar thunar-volman xfce4-appfinder xfce4-notifyd xfce4-panel xfce4-session xfce4-settings xfdesktop xfwm4'
[2012-09-08 07:48] removed xfwm4 (4.10.0-2)
[2012-09-08 07:48] removed xfdesktop (4.10.0-3)
[2012-09-08 07:48] removed xfce4-settings (4.10.0-2)
[2012-09-08 07:48] removed xfce4-session (4.10.0-3)
[2012-09-08 07:48] removed xfce4-panel (4.10.0-1)
[2012-09-08 07:48] removed xfce4-notifyd (0.2.2-3)
[2012-09-08 07:48] removed xfce4-appfinder (4.10.0-1)
[2012-09-08 07:48] removed thunar-volman (0.8.0-1)
[2012-09-08 07:48] removed thunar (1.4.0-2)
[2012-09-08 07:48] removed exo (0.8.0-1)
[2012-09-08 07:48] Running 'pacman -R libxfce4ui'
[2012-09-08 07:48] removed libxfce4ui (4.10.0-1)
[2012-09-08 07:48] Running 'pacman -R xfce4'
[2012-09-08 07:48] removed xfconf (4.10.0-2)
[2012-09-08 07:48] removed tumbler (0.1.25-1)
[2012-09-08 07:48] removed gtk3-xfce-engine (3.0.0-1)
[2012-09-08 07:48] removed gtk2-xfce-engine (3.0.0-1)
[2012-09-08 07:48] removed garcon (0.2.0-1)
[2012-09-08 07:49] Running 'pacman -R consolekit'
[2012-09-08 07:49] removed consolekit (0.4.6-4)

Last edited by ratcheer (2012-09-08 07:06:44)

ratcheer · 2012-09-08 07:24:54

Ok, I see that removing xfce4-notifyd is probably the problem. I am seeking a suitable replacement.

Tim

PS - I have readded just xfce4-notifyd. I configured it and it's working properly. But now, nm-applet does not know about the connections. If I kill nm-applet and start it manually, it does have the connection info. So, I tried adding it to /etc/xdg/openbox/autostart. That makes nm-applet start twice, but neither instance knows about the connections. I have read articles in the wikis and the forums, but every suggestion messes up in one way or another.

I feel like I am close to everything working again, I just need some particular bit of info to get over the hump.

Last edited by ratcheer (2012-09-08 09:11:15)

scjet · 2012-09-08 13:35:45

I would say, you may have to use, only the /etc/xdg/openbox/..., and just use your ~/.config/opembox/..., for all your other configs, IF you're using OpenBox solely.?
http://bbs.archbang.org/viewtopic.php?pid=16892#p16892 -this worked for me.

I honesttly haven't tried the all xfce4,... along with OpenBox, but it may have introduced other anomolies,...?
Anyway, I'm defintely NOT jumping on the "systemd, or NOT to systend" any more, but that's another hopeless story.
When I went to a FULL systemd, I carefully followed the ArchHat's (err um sry, I meant Arch's) wiki's systemd -
as I'm sure you're well aware of.
But ya, xfce4 ? <- nope, Openbox -yes. everything works great for me. within systemd's "allowed" controls, thus far.
sry, if this doesn't help you at all. ?

Last edited by scjet (2012-09-08 13:47:31)

ratcheer · 2012-09-08 20:01:32

scjet wrote:

I would say, you may have to use, only the /etc/xdg/openbox/..., and just use your ~/.config/opembox/..., for all your other configs, IF you're using OpenBox solely.?
http://bbs.archbang.org/viewtopic.php?pid=16892#p16892 -this worked for me.
I honesttly haven't tried the all xfce4,... along with OpenBox, but it may have introduced other anomolies,...?
Anyway, I'm defintely NOT jumping on the "systemd, or NOT to systend" any more, but that's another hopeless story.
When I went to a FULL systemd, I carefully followed the ArchHat's (err um sry, I meant Arch's) wiki's systemd -
as I'm sure you're well aware of.
But ya, xfce4 ? <- nope, Openbox -yes. everything works great for me. within systemd's "allowed" controls, thus far.
sry, if this doesn't help you at all. ?

Thanks. I am looking that over. But, do you still have consolekit running?

Tim

Mr Green · 2012-09-08 23:36:17

ck-list-sessions

Check if consolekit is running

From Arch wiki

https://wiki.archlinux.org/index.php/ConsoleKit

scjet · 2012-09-09 05:01:50

Thanks. I am looking that over. But, do you still have consolekit running?
Tim

Hi Tim,
Yes, I assume I had consolekit running, that is, I did not remove my consolekit when I tried a full systemd (at that time within my ArchBang/Openbox setup), and, I didn't notice that I even had a need to remove "consolekit" ?

Last edited by scjet (2012-09-09 05:03:04)

ratcheer · 2012-09-09 05:51:21

scjet wrote:

Hi Tim,
Yes, I assume I had consolekit running, that is, I did not remove my consolekit when I tried a full systemd (at that time within my ArchBang/Openbox setup), and, I didn't notice that I even had a need to remove "consolekit" ?

Yes, they were talking about removing consolekit earlier in this thread. I have just added it back, that seems to be the best way to keep things going smoothly. I asked the developer about how to make things work correctly without consolekit and he said I "was on my own".

Everything is working again.

Tim

Mr Green · 2012-09-09 05:55:25

Handy post here

https://bbs.archlinux.org/viewtopic.php?id=147032

Oblogout can be edited to work with systemd commands, not sure about slim if you go autologin you may not need consolekit at all

ArchVortex · 2012-09-22 05:29:52

Allan removed the new systemd 191-1 out of [testing] for i686 because it crashes during boot up (as I found out on my testing partition with systemd) You may ask why I'm running Arch with systemd. Well, I believe you can't complain or criticize something without using it. I have a regular and a testing partition with systemd (rolling back to the last version solves the systemd crashing problem). Also, someone will have to support AB users with systemd (LennArch). Yes, I'm taking one for the team

Mr Green · 2012-09-22 05:36:56

No plans to change iso to systemd until either arch goes over to systems completely or archiso. Been running sysd for a weeks now and no real surprises. Still like the idea of initscripts things I can hack if need be....

Arch Linux

Announcement

#1 2012-08-09 04:06:25

Changing to Systemd

#2 2012-08-09 05:26:38

Re: Changing to Systemd

#3 2012-08-09 06:02:05

Re: Changing to Systemd

#4 2012-08-09 06:32:36

Re: Changing to Systemd

#5 2012-08-09 06:36:46

Re: Changing to Systemd

#6 2012-08-09 10:10:27

Re: Changing to Systemd

#7 2012-08-09 10:12:07

Re: Changing to Systemd

#8 2012-08-09 10:25:54

Re: Changing to Systemd

#9 2012-08-12 19:04:47

Re: Changing to Systemd

#10 2012-08-13 00:22:14

Re: Changing to Systemd

#11 2012-08-13 00:58:52

Re: Changing to Systemd

#12 2012-08-13 02:13:14

Re: Changing to Systemd

#13 2012-08-13 02:33:56

Re: Changing to Systemd

#14 2012-08-13 03:51:48

Re: Changing to Systemd

#15 2012-08-13 04:51:11

Re: Changing to Systemd

#16 2012-08-13 06:45:12

Re: Changing to Systemd

#17 2012-08-13 06:50:23

Re: Changing to Systemd

#18 2012-08-13 07:16:17

Re: Changing to Systemd

#19 2012-08-13 07:34:10

Re: Changing to Systemd

#20 2012-08-13 08:04:39

Re: Changing to Systemd

#21 2012-08-13 08:09:48

Re: Changing to Systemd

#22 2012-08-13 08:23:00

Re: Changing to Systemd

#23 2012-08-13 08:29:25

Re: Changing to Systemd

#24 2012-08-13 17:52:57

Re: Changing to Systemd

#25 2012-08-13 23:24:55

Re: Changing to Systemd

#26 2012-08-13 23:45:58

Re: Changing to Systemd

#27 2012-08-14 00:37:48

Re: Changing to Systemd

#28 2012-08-14 01:00:32

Re: Changing to Systemd

#29 2012-08-14 01:33:23

Re: Changing to Systemd

#30 2012-08-14 01:36:19

Re: Changing to Systemd

#31 2012-08-14 01:46:22

Re: Changing to Systemd

#32 2012-08-14 01:56:24

Re: Changing to Systemd

#33 2012-08-14 01:58:32

Re: Changing to Systemd

#34 2012-08-14 02:16:19

Re: Changing to Systemd

#35 2012-08-14 02:48:06

Re: Changing to Systemd

#36 2012-08-14 03:01:36

Re: Changing to Systemd

#37 2012-08-14 03:06:46

Re: Changing to Systemd

#38 2012-08-14 03:11:59

Re: Changing to Systemd

#39 2012-08-14 05:40:06

Re: Changing to Systemd