[SOLVED] /etc/systemd/system.conf: DumpCore

What's that option for?
I cannot find it by myself, sorry...
Last edited by kokoko3k (2015-01-22 15:27:50)

karol wrote:
/etc/systemd/system.conf has a man page:
man systemd-system.conf wrote: LogLevel=, LogTarget=, LogColor=, LogLocation=, DumpCore=yes, CrashShell=no, ShowStatus=yes,
CrashChVT=1, DefaultStandardOutput=journal, DefaultStandardError=inherit
Configures various parameters of basic manager operation. These options may be overridden by
the respective command line arguments. See systemd(1) for details about these command line
arguments.
but it doesn't say what does this option do.
man systemd wrote: --dump-core
Dump core on crash. This switch has no effect when run as user instance.

Similar Messages

[Solved]I deleted /etc/systemd/logind.conf by mistake

I deleted /etc/systemctl/logind.conf by mistake with
sudo rm /etc/systemd/logind.conf
How can I get that file back?
Last edited by aaa234 (2015-06-07 10:26:56)

it's ok now, I reinstalled it with
sudo pacman -S systemd
The problem is solved, thank u so much everyone.

[SOLVED] config in /etc/systemd (ssh, getty) resets after system upgr.

I've made changes in /etc/systemd/system/getty.target.wants/[email protected] (don't clear console at boot as per https://wiki.archlinux.org/index.php/Sy … r_boot.3F) and /etc/systemd/system/sockets.target.wants/sshd.socket (changed ssh port) but they keep getting reset after a system upgrade (not sure by what package, pacman -Qo file says that no package owns them)
I'm starting to wonder if above places are the correct place and even way to do mentioned changes.
What I want to achieve;
1) simple way to not clear console after boot
2) change what port ssh (systemd ssh socket) listens at
3) make them changes permanent and durable even after a system upgrade
My setup is pure systemd.
Last edited by ImbaLocus (2012-10-30 23:41:08)

Thank you, this works.
Have yet to do an upgrade but I'm sure configuring according to your solution will This works perfectly.
Last edited by ImbaLocus (2012-11-01 12:48:33)

[solved] writing systemd service file to run script

i have completely migrated to systemd. now, i am trying to write a service file to run a startup script (~/.startup.sh). one of the functions of the script is to set the brightness of the screen:
echo "95" > /sys/class/backlight/intel_backlight/brightness
i created /etc/systemd/system/startup.service:
[Unit]
Description=Run startup script
[Service]
Type=oneshot
ExecStart=~/.startup.sh
[Install]
WantedBy=multi-user.target
but i get the following error:
Failed to issue method call: Unit startup.service failed to load: Invalid argument. See system logs and 'systemctl status startup.service' for details.
i have two questions:
1. what am i missing?
2. how can i avoid permission issues associated with modifying the brightness file (e.g., permission denied errors, the need to put in the password, etc.)?
thanks.
Last edited by anti-destin (2012-08-01 22:26:04)

thanks for the replies.
just a note: using an absolute path didn't fix the issue.
but i went ahead and created the file /etc/tmpfiles.d/backlight.conf:
w /sys/class/backlight/intel_backlight/brightness - - - - 95
and that worked.
is there a reason for recommending using a tmpfile rather than a service?
in any case, i'm marking this as solved.

[solved] /etc/udev/rules.d/10-network.rules ignored

Hi.
I have 4 nics (eth0, eth1, eth2, eth3) mapped to MAC addresses in /etc/udev/rules.d/10-network.rules.
Some months ago, I had to symlink /etc/udev/rules.d/80-net-name-slot.rules to /dev/null in order to use these static names.
Now it doesn't work anymore (again and again and again) after a full update (kernel and I assume systemd). The "nic-names" are completely wrong. You call this "predictable". I call this "unpredictable". The only thing which is predictable is that after a kernel update, the network will stop working. It has been that way for months and months ... fortunately I don't update other machines anymore.
Was this non sense really necessary?
Anyway, if you could tell me what to do now to get my network rules applied again, I would really appreciate.
Right now all ethX/MAC are wrong and none of them gets an IP (had to set an IP manually to post here).
* I know what "predictable Network Interface Names" is about. I don't want this bullshit. It's much worse as it used to be. Keep it simple, folks!
Last edited by Agnelo de la Crotche (2013-03-27 07:14:05)

tomegun wrote:To narrow down the problem you are experiencing: What do you mean when you say that the names are "wrong"? Are they still eth0, eth1,... just in the wrong order, or are you actually seeing the "weird" new names given by udev?
To answer this question more precisely.
* with /etc/udev/rules.d/80-net-name-slot.rules => /dev/nul and /etc/udev/rules.d/10-network.rules posted earlier (in #4)
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:0a:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:06:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:24:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:1b:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
link/ether 66:64:b3:6a:26:61 brd ff:ff:ff:ff:ff:ff
The rules are ignored.
* after deleting /etc/udev/rules.d/80-net-name-slot.rules
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp6s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:0a:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: enp6s1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:06:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
4: enp2s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:24:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
5: enp4s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:1b:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
link/ether a2:ee:ec:d1:65:2d brd ff:ff:ff:ff:ff:ff
The rules don't apply.
* with /etc/udev/rules.d/80-net-name-slot.rules => /dev/nul and after replacing eth0, eth1, eth2, eth3 with arbitrary names net0, net1, net2, net3 in /etc/udev/rules.d/10-network.rules
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: net1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:24:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
3: net3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:0a:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
4: net2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:06:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
5: net0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000
link/ether 00:1b:XX:XX:XX:XX brd ff:ff:ff:ff:ff:ff
6: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT
link/ether ea:63:09:b7:1b:1b brd ff:ff:ff:ff:ff:ff
But the rules were applied in this case!
It solved the problem described originally. I think I was hit by the race condition after upgrating to kernel 3.8.4-1. This was actually my first 3.8 kernel.
With kernel 3.7, the rules were working even if the devices were named eth0, eth1, etc.
Those names don't work anymore, at least in my case.
Further I created this file for static ips:
# cat /etc/systemd/system/network.service
[Unit]
Description=Wired Static IP Connectivity
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-net0.device
After=sys-subsystem-net-devices-net0.device
[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/sbin/ip link set dev net0 up
ExecStart=/sbin/ip addr add 192.168.101.9/24 dev net0
ExecStart=/sbin/ip link set dev net1 up
ExecStart=/sbin/ip addr add 192.168.102.9/24 dev net1
ExecStart=/sbin/ip link set dev net2 up
ExecStart=/sbin/ip addr add 192.168.104.9/24 dev net2
ExecStart=/sbin/ip link set dev net3 up
ExecStart=/sbin/ip addr add 192.168.105.9/24 dev net3
ExecStart=/sbin/ip route add default via 192.168.101.1
ExecStop=/sbin/ip addr flush dev net0
ExecStop=/sbin/ip link set dev net0 down
ExecStop=/sbin/ip addr flush dev net1
ExecStop=/sbin/ip link set dev net1 down
ExecStop=/sbin/ip addr flush dev net2
ExecStop=/sbin/ip link set dev net2 down
ExecStop=/sbin/ip addr flush dev net3
ExecStop=/sbin/ip link set dev net3 down
[Install]
WantedBy=multi-user.target
I disabled netcfg and enabled network.service.
Problem is solved now.

[Solved] Overriding systemd Unit Files Isn't Working

I'm trying to set up some custom dependencies for various services, some of which are supported packages, some are custom packages I've developed. I am running into problems following the procedure described here - specifically, service files in /etc/systemd/system are ignored, and the only way to override them is to edit the files in /usr/lib/systemd/system. I have verified this issue on both a VPS instance and my desktop. Both systems were originally built well before systemd and have been converted to pure systemd systems. Does anyone else see these issues, or know of any reason this would be happening and/or how to resolve it?
Steps to reproduce. This example uses httpd and mysql, but I've tested it with several other services, always with the same results:
Enable the service unit and create a new override:
systemctl enable httpd.service
rm /etc/systemd/system/multi-user.target.wants/httpd.service
cp /usr/lib/systemd/system/httpd.service /etc/systemd/system/multi-user.target.wants/httpd.service
Edit /etc/systemd/system/multi-user.target.wants/httpd.service, adding a line 'Wants=mysqld.service' to the [Unit] section.
Make systemd changes effective, and verify them. The first command results in an error that says "Failed to issue method call: Invalid argument". The final command will show an empty list ("Wants="), when it should list mysqld. Running systemd-delta also shows no override.
systemctl reenable httpd
systemctl daemon-reload
systemctl show -p "Wants" httpd.service
Change the replacement unit file to .include the packaged unit file:
cat > /etc/systemd/system/multi-user.target.wants/httpd.service << __EOF
.include /usr/lib/systemd/system/httpd.service
[Unit]
Wants=mysqld.service
__EOF
Repeat step #3, with the same results
Reenable the package's unit:
rm /etc/systemd/system/multi-user.target.wants/httpd.service
systemctl enable httpd.service
Edit the original unit file in /usr/lib/systemd/system/httpd.service, adding the 'Wants=myslqd.service' to the Unit section
Repeat step 3
Result is the correct and expected one this time ("Wants=myslqd.service")
Last edited by dwheeler (2012-11-14 19:53:10)

Well...
I'm still having problems with .service custom files!
I want to customize the ExecStart from original cronie.service file, like this:
# cat /etc/systemd/system/cronie.service
.include /usr/lib/systemd/system/cronie.service
[Service]
ExecStart=/usr/sbin/crond -n -s -m off
==============================
# systemctl restart cronie.service
Failed to issue method call: Unit cronie.service failed to load: Invalid argument. See system logs and 'systemctl status cronie.service' for details.
==============================
# systemd-delta
[OVERRIDDEN] /etc/systemd/system/cronie.service → /usr/lib/systemd/system/cronie.service
--- /usr/lib/systemd/system/cronie.service 2012-11-22 20:04:00.000000000 -0200
+++ /etc/systemd/system/cronie.service 2012-11-27 16:09:49.944085437 -0200
@@ -1,10 +1,3 @@
-[Unit]
-Description=Periodic Command Scheduler
+.include /usr/lib/systemd/system/cronie.service
[Service]
-ExecStart=/usr/sbin/crond -n
-ExecReload=/bin/kill -HUP $MAINPID
-Restart=always
-[Install]
-WantedBy=multi-user.target
+ExecStart=/usr/sbin/crond -n -s -m off
==============================
# systemctl status cronie.service
cronie.service - Periodic Command Scheduler
Loaded: error (Reason: Invalid argument)
Active: inactive (dead)
CGroup: name=systemd:/system/cronie.service
Nov 27 13:52:59 xpto systemd[1]: Starting Periodic Command Scheduler...
Nov 27 13:52:59 xpto systemd[1]: Started Periodic Command Scheduler.
Nov 27 13:52:59 xpto /usr/sbin/crond[309]: (CRON) INFO (running with inotify support)
Nov 27 14:01:01 xpto /usr/sbin/crond[8216]: pam_unix(crond:session): session opened for user root by (uid=0)
Nov 27 14:01:01 xpto /USR/SBIN/CROND[8217]: (root) CMD (run-parts /etc/cron.hourly)
==============================
What am I doing wrong?
Thanks in advance.

[Solved]With systemd on install media, systemctl works during install?

When I upgrading my current machine from sysvinit to systemd, in order to use systemctl to enable services, I first had to reboot the system.
With the new install media for October using systemd, is it possible to enable these services using systemctl during the install (ie, so I could add 'systemctl enable foo.service' to install scripts)?
I do realize that I could just manually symlink, but it feel much nicer to use systemctl.
Last edited by Morrad (2012-10-08 05:12:39)

I do exactly that in my install script...
systemctl enable cronie.service
systemctl enable [email protected]
systemctl enable UEFIstubMOVE.path
systemctl start UEFIstubMOVE.path
...but see below for the message I get when I try to start one of the services...
ln -s '/usr/lib/systemd/system/cronie.service' '/etc/systemd/system/multi-user.target.wants/cronie.service'
ln -s '/usr/lib/systemd/system/[email protected]' '/etc/systemd/system/multi-user.target.wants/[email protected]'
ln -s '/etc/systemd/system/UEFIstubMOVE.path' '/etc/systemd/system/multi-user.target.wants/UEFIstubMOVE.path'
Running in chroot, ignoring request.

SOLVED: Created /etc/X11/xorg.conf, now system won't boot.

I was trying to solve an issue with display resolution not sticking and it was suggested to me that I create an /etc/X11/xorg.conf.
I created the file and put in the lines that I had in my .xprofile related to xrandr.
Now... my system will not boot. It appears to get hung up trying to detect my ethernet connection. I tried Ctrl-Alt-F1 to avoid X windowing, no dice.
What's more, my system rescue pen drive appears to have died. I still have my Arch install CD.
All I want to do is delete xorg.conf. My arch root is a logical volume so I have no idea how to mount it after I boot from the Arch install CD, or if I can even do this.
Update: So embarrassing, my mount command was wrong. Once I did something that looked like this:
mount /dev/VolGroup0/root /mnt/
I was able to get into /etc/X11 and delete xorg. conf. Rebooted and all appears well.
Last edited by testingwithfire (2014-06-02 01:36:07)

For mounting LVM, this page should probably help: https://wiki.archlinux.org/index.php/LV … al_volumes
Once in, then it should be easy.

[solved] full systemd integration of /etc/rc.local and pm-utils

Hello!
I try to fully integrate my /etc/rc.local into systemd. But I'm not very successful with it yet…
For the moment I use this workaround.
My rc.local looks like
#!/bin/bash
# /etc/rc.local: Local multi-user startup script.
/usr/sbin/wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant.conf
/usr/sbin/dhcpcd -qb eth0 wlan0
/usr/bin/amixer -q -c 0 sset 'Master',0 0% mute
/bin/mount -o remount,noatime /
I tried to work with wiki and man, since people tell me more often I should go that way. I did it and integrated all of my daemons except for the rc.local.
I really need help at this point…
Thanks in advance!
Last edited by domac (2012-08-14 19:07:35)

Ok… it's getting weird now… my files look like:
[Unit]
Description=WPA supplicant daemon (interface-specific version)
Requires=sys-subsystem-net-devices-%I.device
After=sys-subsystem-net-devices-%I.device
# NetworkManager users will probably want the dbus version instead.
[Service]
Type=simple
ExecStart=/usr/sbin/wpa_supplicant -i %I -c /etc/wpa_supplicant/wpa_supplicant-%I.conf
[Install]
Alias=multi-user.target.wants/[email protected]
[Unit]
Description=dhcpcd on %I
Wants=network.target
Before=network.target
[Service]
Type=forking
PIDFile=/run/dhcpcd-%I.pid
ExecStart=/usr/sbin/dhcpcd -A -q -w %I
ExecStop=/usr/sbin/dhcpcd -k %I
[Install]
Alias=multi-user.target.wants/[email protected]
and with this setting I get two (visible) errors at boot, as you can see in #journalctl:
Aug 14 01:32:49 vex dhcpcd[250]: eth0: carrier acquired
Aug 14 01:32:49 vex dhcpcd[257]: wlan0: carrier acquired
Aug 14 01:32:49 vex dhcpcd[250]: eth0: carrier lost
Aug 14 01:32:49 vex dhcpcd[250]: eth0: waiting for carrier
Aug 14 01:32:49 vex dhcpcd[257]: wlan0: sending IPv6 Router Solicitation
Aug 14 01:32:49 vex dhcpcd[257]: wlan0: sendmsg: Cannot assign requested address
Aug 14 01:32:49 vex dhcpcd[257]: wlan0: broadcasting for a lease
Aug 14 01:32:49 vex dhcpcd[257]: wlan0: carrier lost
Aug 14 01:32:49 vex dhcpcd[257]: wlan0: carrier acquired
Aug 14 01:32:49 vex dhcpcd[257]: wlan0: sending IPv6 Router Solicitation
Aug 14 01:32:49 vex dhcpcd[257]: wlan0: sendmsg: Cannot assign requested address
Aug 14 01:32:49 vex dhcpcd[257]: wlan0: broadcasting for a lease
Aug 14 01:32:50 vex systemd-logind[260]: New seat seat0.
Aug 14 01:32:50 vex systemd-logind[260]: Watching system buttons on /dev/input/event3 (Power Button)
Aug 14 01:32:50 vex systemd-logind[260]: Watching system buttons on /dev/input/event5 (Video Bus)
Aug 14 01:32:50 vex systemd-logind[260]: Watching system buttons on /dev/input/event4 (Video Bus)
Aug 14 01:32:50 vex systemd-logind[260]: Watching system buttons on /dev/input/event1 (Lid Switch)
Aug 14 01:32:50 vex systemd-logind[260]: Watching system buttons on /dev/input/event2 (Sleep Button)
Aug 14 01:32:51 vex dhcpcd[257]: wlan0: offered 192.168.2.117 from 192.168.2.1
Aug 14 01:32:51 vex dhcpcd[257]: wlan0: acknowledged 192.168.2.117 from 192.168.2.1
Aug 14 01:32:51 vex dhcpcd[257]: wlan0: leased 192.168.2.117 for 864000 seconds
Aug 14 01:32:51 vex dhcpcd[257]: forked to background, child pid 350
Aug 14 01:32:53 vex dhcpcd[350]: wlan0: sending IPv6 Router Solicitation
Aug 14 01:32:57 vex dhcpcd[350]: wlan0: sending IPv6 Router Solicitation
Aug 14 01:32:59 vex dbus-daemon[259]: dbus[259]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Aug 14 01:32:59 vex console-kit-daemon[354]: missing action
Aug 14 01:32:59 vex dbus-daemon[259]: dbus[259]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Aug 14 01:32:59 vex dbus-daemon[259]: dbus[259]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Aug 14 01:32:59 vex dbus-daemon[259]: dbus[259]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Aug 14 01:32:59 vex systemd-logind[260]: New session 1 of user domac.
Aug 14 01:33:01 vex acpid[254]: client connected from 459[0:100]
Aug 14 01:33:01 vex acpid[254]: 1 client rule loaded
Aug 14 01:33:01 vex dhcpcd[350]: wlan0: sending IPv6 Router Solicitation
Aug 14 01:33:01 vex dhcpcd[350]: wlan0: no IPv6 Routers available
Aug 14 01:33:19 vex dhcpcd[250]: timed out
Aug 14 01:33:19 vex systemd[1]: [email protected]: control process exited, code=exited status=1
Aug 14 01:33:19 vex systemd[1]: Unit [email protected] entered failed state.
… but, it works now! dafuq?!
Well, this is no solution yet… help is appreciated.
Edit: Removed those two lines that were causing errors and rebooted. Can someone explain their relevance to me?
#journalctl now looks like:
Aug 14 01:40:49 vex dhcpcd[250]: eth0: carrier acquired
Aug 14 01:40:49 vex dhcpcd[259]: wlan0: sending IPv6 Router Solicitation
Aug 14 01:40:49 vex dhcpcd[259]: wlan0: sendmsg: Network is unreachable
Aug 14 01:40:49 vex dhcpcd[250]: eth0: carrier lost
Aug 14 01:40:49 vex dhcpcd[250]: eth0: waiting for carrier
Aug 14 01:40:49 vex dhcpcd[259]: wlan0: broadcasting for a lease
Aug 14 01:40:50 vex su[252]: pam_unix(su:session): session opened for user domac by (uid=0)
Aug 14 01:40:50 vex su[252]: pam_unix(su:session): session closed for user domac
Aug 14 01:40:50 vex dhcpcd[259]: wlan0: carrier lost
Aug 14 01:40:50 vex systemd-logind[262]: New seat seat0.
Aug 14 01:40:50 vex systemd-logind[262]: Watching system buttons on /dev/input/event3 (Power Button)
Aug 14 01:40:50 vex systemd-logind[262]: Watching system buttons on /dev/input/event5 (Video Bus)
Aug 14 01:40:50 vex systemd-logind[262]: Watching system buttons on /dev/input/event4 (Video Bus)
Aug 14 01:40:50 vex systemd-logind[262]: Watching system buttons on /dev/input/event1 (Lid Switch)
Aug 14 01:40:50 vex systemd-logind[262]: Watching system buttons on /dev/input/event2 (Sleep Button)
Aug 14 01:40:51 vex dhcpcd[259]: wlan0: carrier acquired
Aug 14 01:40:51 vex dhcpcd[259]: wlan0: sending IPv6 Router Solicitation
Aug 14 01:40:51 vex dhcpcd[259]: wlan0: sendmsg: Cannot assign requested address
Aug 14 01:40:51 vex dhcpcd[259]: wlan0: broadcasting for a lease
Aug 14 01:40:52 vex dhcpcd[259]: wlan0: offered 192.168.2.117 from 192.168.2.1
Aug 14 01:40:52 vex dhcpcd[259]: wlan0: acknowledged 192.168.2.117 from 192.168.2.1
Aug 14 01:40:52 vex dhcpcd[259]: wlan0: leased 192.168.2.117 for 864000 seconds
Aug 14 01:40:52 vex dhcpcd[259]: forked to background, child pid 344
Aug 14 01:40:55 vex dhcpcd[344]: wlan0: sending IPv6 Router Solicitation
Aug 14 01:40:59 vex dbus-daemon[260]: dbus[260]: [system] Activating via systemd: service name='org.freedesktop.ConsoleKit' unit='console-kit-daemon.service'
Aug 14 01:40:59 vex dhcpcd[344]: wlan0: sending IPv6 Router Solicitation
Aug 14 01:40:59 vex console-kit-daemon[348]: missing action
Aug 14 01:40:59 vex dbus-daemon[260]: dbus[260]: [system] Activating service name='org.freedesktop.PolicyKit1' (using servicehelper)
Aug 14 01:40:59 vex dbus-daemon[260]: dbus[260]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Aug 14 01:40:59 vex dbus-daemon[260]: dbus[260]: [system] Successfully activated service 'org.freedesktop.ConsoleKit'
Aug 14 01:40:59 vex systemd-logind[262]: New session 1 of user domac.
Aug 14 01:41:01 vex acpid[256]: client connected from 453[0:100]
Aug 14 01:41:01 vex acpid[256]: 1 client rule loaded
Aug 14 01:41:03 vex dhcpcd[344]: wlan0: sending IPv6 Router Solicitation
Aug 14 01:41:03 vex dhcpcd[344]: wlan0: no IPv6 Routers available
Aug 14 01:41:19 vex dhcpcd[250]: timed out
Aug 14 01:41:19 vex systemd[1]: [email protected]: control process exited, code=exited status=1
Aug 14 01:41:19 vex systemd[1]: Unit [email protected] entered failed state.
Cheers, will visit my bed now!
Last edited by domac (2012-08-13 23:44:15)

[SOLVED]xpra + winswitch - best practice due to /etc/X11/xorg.conf.d/*

Running xpra causes some headaches.
The application builds fine and installs just perfectly, the troubles comes from the default Xorg configuration is no longer stored in /etc/X11/xorg.conf, it's now stored and read from numerous files under /etc/X11/xorg.conf.d/ where just so happen to be my 5-nvidia.conf.
Starting xpra via:
xpra start :100
Causes:
X.Org X Server 1.14.3
Release Date: 2013-09-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.11.0-1-ARCH x86_64
Current Operating System: Linux archie 3.11.2-1-ARCH #1 SMP PREEMPT Fri Sep 27 07:35:36 CEST 2013 x86_64
Kernel command line: root=/dev/sda1 rw initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
Build Date: 13 September 2013 01:28:59PM
Current version of pixman: 0.30.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/home/torxed/.xpra/Xorg.:100.log", Time: Thu Oct 3 19:56:30 2013
(++) Using config file: "/etc/xpra/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
setversion 1.4 failed
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(EE)
Fatal server error:
(EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
(EE) Please also check the log file at "/home/torxed/.xpra/Xorg.:100.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.
2013-10-03 19:56:30,893
2013-10-03 19:56:30,893 Xvfb command has terminated! xpra cannot continue
2013-10-03 19:56:30,894
2013-10-03 19:56:30,895 removing socket /home/torxed/.xpra/archie-100
tl;dr: 5-nvidia.conf is trying to get loaded after xf86-video-dummy is loaded (which is the default for xpra).
Now to the question: What's the best practice because there's no information about this issue, and i can't be the only one who's run in to this since the xorg.conf was removed. At the moment I move all my nvidia configs out of the way, start xpra and move them back in. This works for the better part as long as i execute xpra with my own scripts.
But is there a better way (which doesn't perhaps include recreating xorg.conf since that appears to be something you should walk away from)?
Last edited by Torxed (2013-10-04 10:29:35)

Good thinking! (xpra is basically just screen but for x, or a X11 tunnel via SSH).
After a really quick poking around and remembering that xpra really just uses xorg-server-xvfb and at the very bottom of /etc/xpra/xpra.conf there's a line that says:
xvfb=xpra_Xdummy -dpi 96 -noreset -nolisten tcp +extension GLX +extension RANDR +extension RENDER -logfile ${HOME}/.xpra/Xorg.${DISPLAY}.log -config /etc/xpra/xorg.conf
Appending -configdir appears to be working.
Here are the full steps:
[torxed@archie ~]$ sudo cp -r /etc/X11/xorg.conf.d /etc/xpra/
[torxed@archie ~]$ sudo rm /etc/xpra/xorg.conf.d/*nvidia*
[torxed@archie ~]$ sudo sed -i '$s/$/ -configdir \/etc\/xpra\/xpra.conf.d/' /etc/xpra/xpra.conf
*nvidia* would have to match your graphic-driver-config that would cause xorg-server-xvbf to crash.
I'll update the wiki and put a mention on the package about it because this either has to be standard or well known from the start because it really just breaks the package all together.
Last edited by Torxed (2013-10-04 10:29:09)

[Solved] Starting systemd --user as a systemd --system process?

Hey guys,
I would like to run systemd --user as a system service using this .service file I wrote:
$ cat [email protected]
[Unit]
Description=Systemd --user instance for %I
Documentation=man:systemd
[Service]
User=%I
ExecStart=/usr/lib/systemd/systemd --user --log-level=debug
[Install]
WantedBy=multi-user.target
I enabled it for my user using `systemctl enable systemd-user@evan`, however, when starting it it fails with the following errors:
Jul 21 21:14:42 desktop systemd[12920]: systemd 204 running in user mode. (+PAM -LIBWRAP -AUDIT -SELINUX -IMA -SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ)
Jul 21 21:14:42 desktop systemd[12920]: Using cgroup controller name=systemd. File system hierarchy is at /sys/fs/cgroup/systemd/system/[email protected]/[email protected]/systemd-12920.
Jul 21 21:14:42 desktop systemd[12920]: Failed to create root cgroup hierarchy: Permission denied
Jul 21 21:14:42 desktop systemd[12920]: Failed to allocate manager object: Permission denied
Is it possible to run systemd --user like this? Do I need to add something to my [email protected]?
Last edited by EvanPurkhiser (2013-07-22 02:10:10)

EDIT: I just realized that the systemd-user-session-units package will only include specific units at build-time weather I have have the programs or not. You're right, I should just use this package!
Well, to be honest, maybe I'm trying to hack around a problem that doesn't even really exist, but I don't think the systemd-user-sessions-units package meets my needs.
The way I would like to have my user sessions setup is something like this:
I would like to have an instance of systemd --user always running under my user so I can keep things like transmission-daemon always running, even when I don't have a user session open. When I do start my user session (via logging into getty) I want to bring my systemd instance up to a certain target. For example, logging in via tty1 should bring up graphical.target, which will start X11 and all that, while logging into any other tty will start console.target (for stuff like ssh-agent etc).
Thinking more about this I suppose there's really no reason I couldn't use the [email protected] from systemd-user-session-units, but since I won't use most of the other user units included, I would rather just not use it.
Here's what my .profile looks like:
if systemctl -q is-active systemd-user@evan
then
# Default systemd to the console target
target="console"
# If we're logging in from VT1 start the graphical target
if [[ $XDG_VTNR == 1 ]] && ! systemctl --user -q is-active graphical.target &> /dev/null
then
export DISPLAY=:0
target="graphical"
fi
# Set all environment variables in the systemd --user instance (still working on this)
env | systemctl --user set-environment -
# Bring up systemd --user to the specified target
systemctl --user start ${target}.target
fi
source "$HOME/.bashrc"
Last edited by EvanPurkhiser (2013-07-22 03:56:13)

[Solved] Installting A Pure systemd System From Scratch

Hello all,
A few months back I gave Arch a spin and it was great, but decided to wait for Windows 8 RTM to come out to check it out as well.
Windows 8 being the horrible thing it is, Arch is the way to go, and I would like to do a test installation alongside Windows 7, in order to make sure I can make the switch permanently.
Having followed the forums pretty consistently, it seems that systemd is the future.
Instead of waiting for it to be integrated (which is supposed to happen at some point), I was wondering if I can somehow install a pure systemd system as part of the basic installation and not installing initscripts at all.
Thanks, Adam.
Last edited by adam777 (2012-08-28 12:55:27)

mhertz wrote:
luvfree wrote:[...].
I'm going to reinstall anyway so why not wait until the iso doesn't pacstrap the old initscripts and sysvinit?
Just makes for a cleaner install all around.
I'm certainly not going to leave this install on with 4 installed desktop environments.[...]
I myself was also reinstalling alot and imaging and whatnot when I first began with linux(arch), but after some time I realised that it was pointless and linux dosen't need those reinstalls for optimization like windows did, and pacman has nifty switches to get you sorted on what you've explicitly installed and hence, can go delete the cruft not used anymore, or to list files not owned by any installed packages, to clean up in etc...
Nowadays, I newer reinstall unless something would go _really_ wrong, and only backup config-files and home-files, and keep a livecd around for rescue-operations, and an automated personal install script for if I ever do need to reinstall...
Anyway, of course it's your own choise
I understand and the arch way is awesome.
but it is still on the new side to me.
I've bloated this install with 4 desktop environments so a reinstall is inevitable. lol
once I settle on which one to keep I'll do just that.
it will be some time though I'm sure.
I'm just keeping my eye out for an iso without the old initscripts pacstapped to begin with.
it just HAS to be a cleaner install.
Thanks for your input though.
CHEERS.
Oh yeah and by the way I've used nothing but linux for over 10 years now.
No windoze here.
Last edited by luvfree (2012-09-05 03:40:22)

Is adding /usr/lib to /etc/ld.so.conf.d/00-system.conf a bad idea?

I recently noticed I was using AMD's libOpenCL (the ICD) because its path was being injected through the ld.so.conf.d configuration files.
I had installed another ICD, and was expecting to use the libOpenCL.so from /usr/lib, but I wasn't, so I created a file /etc/ld.so.conf.d/00-system.conf with a single line: /usr/lib, so that system libraries are used first.
Is this a bad idea in general and does this break anything? I know I'm relying on Arch to provide the latest (hopefully ABI backwards compatible) version of all libraries, but this shouldn't really be a problem, right?

The following is said in the manpage of 'ldconfig':
ldconfig creates the necessary links and cache to the most recent shared libraries found in the directories specified on the command line, in the file /etc/ld.so.conf, and in the trusted directories (/lib and /usr/lib).
The way I see it, these directories are automatically considered.
Edit: Ups, ebal was faster.
Last edited by matzo (2010-02-19 21:02:52)

[SOLVED]/etc/vconsole.conf doesn't react to any change

Hi,
I'm new in Arch Linux, so sorry if I'm missreading something.
I try to change my font and keymap using this manual: https://wiki.archlinux.org/index.php/KEYMAP
So i edit /etc/vconsole.conf like this:
KEYMAP=cz-lat2
FONT=Lat2-Terminus16
but nothing change, even after reboot. "kbd" is installed.
Btw. when I run "setfont Lat2-Terminus16" the font is changed (but just this session).
Thanks
Last edited by Kotrfa (2012-11-06 16:22:41)

It doesnt work in any form.
I tried to add i915 to my mkinicpio to modules, but when I run:
[dan@localhost ~]$ sudo mkinitcpio -p linux
[sudo] password for root:
==> Building image from preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
==> Starting build: 3.6.3-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
findmnt: /etc/fstab: parse error at line 7
-> Running build hook: [pata]
-> Running build hook: [scsi]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [usbinput]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux.img
bsdcpio: Failed to set default locale
==> Image generation successful
==> Building image from preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: 3.6.3-1-ARCH
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [pata]
-> Running build hook: [scsi]
-> Running build hook: [sata]
-> Running build hook: [filesystems]
-> Running build hook: [usbinput]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
bsdcpio: Failed to set default locale
==> Image generation successful
There are messages about failing to set locale.
Btw. here is my locale and locale -a output:
[dan@localhost ~]$ locale -a
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_COLLATE to default locale: No such file or directory
C
POSIX
cs_CZ.utf8
en_GB.utf8
[dan@localhost ~]$ locale
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
LANG=en_US.utf8
LC_CTYPE="en_US.utf8"
LC_NUMERIC="en_US.utf8"
LC_TIME="en_US.utf8"
LC_COLLATE="en_US.utf8"
LC_MONETARY="en_US.utf8"
LC_MESSAGES="en_US.utf8"
LC_PAPER="en_US.utf8"
LC_NAME="en_US.utf8"
LC_ADDRESS="en_US.utf8"
LC_TELEPHONE="en_US.utf8"
LC_MEASUREMENT="en_US.utf8"
LC_IDENTIFICATION="en_US.utf8"
LC_ALL=
Edit: When I try to change my keyboard layout in gnome creating /etc/X11/xorg.conf.d/10-keyboard.conf with:
Section "InputClass"
Identifier "Keyboard Defaults"
MatchIsKeyboard "yes"
Option "XbkLayout" "cz"
EndSection
it doesn't work.
And when I try to use: "setxkbmap cz", it change my keyboard to czech, but it doesn't work in terminal (when i type "+ěščřtřžýáí" i get "+???????".
Last edited by Kotrfa (2012-10-29 12:33:51)

[SOLVED]Strange file /etc/ld.so.confe

Dear community,
Starting with filesystem 2010.01-1, after each filesystem update I am finding a file called /etc/ld.co.confe, which is a copy of /etc/ld.co.conf (this is besides the usual /etc/ld.co.conf.pacnew). I took a quick look at PKGBUILD and filesystem.install in /vas/abs/core/filesystem, there was nothing pointing to this file...
Does anyone knows its purpose? The current version is filesystem 2010.02-3.
Thanks.
Last edited by Leonid.I (2010-02-21 20:36:01)

foutrelis wrote:
That file has been created by the qt3 package's qt.install file. Apparently in sed, '-ie' is not the same as '-i -e'.
I filed a bug report here, but for now it's safe to just delete it.
Thanks.
I agree, in 'sed -ie' , 'e' will be considered as a backup suffix. Perhaps it should have been 'sed -ei'
L.
edit: wrong emoticon
Last edited by Leonid.I (2010-02-17 18:03:13)

[SOLVED] /etc/systemd/system.conf: DumpCore

Similar Messages

Maybe you are looking for