[arch-general] systemd and fancontrol
Hi All, I've just switched to systemd from initscript and I can't resolve an issue: fancontrol fails to run at boot time, but it works properly when manually started. Logs: UNIT LOAD ACTIVE SUBJOB DESCRIPTION colord.service loaded failed failed Manage, Install and Generate Color Profiles fancontrol.service loaded failed failed Fan control daemon # systemctl status fancontrol fancontrol.service - Fan control daemon Loaded: loaded (/etc/systemd/system/fancontrol.service; enabled) Active: failed (Result: exit-code) since Tue, 23 Oct 2012 07:23:42 +0200; 4min 53s ago Process: 434 ExecStart=/usr/sbin/fancontrol (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/fancontrol.service Oct 23 07:23:51 arch fancontrol[434]: Controls hwmon1/device/fan2_input Oct 23 07:23:51 arch fancontrol[434]: MINTEMP=35 Oct 23 07:23:51 arch fancontrol[434]: MAXTEMP=45 Oct 23 07:23:51 arch fancontrol[434]: MINSTART=155 Oct 23 07:23:51 arch fancontrol[434]: MINSTOP=160 Oct 23 07:23:51 arch fancontrol[434]: MINPWM=155 Oct 23 07:23:51 arch fancontrol[434]: MAXPWM=210 Oct 23 07:23:51 arch fancontrol[434]: Device path of hwmon1 has changed Oct 23 07:23:51 arch fancontrol[434]: Device name of hwmon1 has changed Oct 23 07:23:51 arch fancontrol[434]: Configuration appears to be outdated, please run pwmconfig again I thought it is a timing issue, so I tweaked fancontrol.service, but didn't helped: # cat /etc/systemd/system/fancontrol.service .include /usr/lib/systemd/system/fancontrol.service [Unit] Requires=sensord.service After=sensord.service Any advice? Thanks. zs
Re: [arch-general] Modify installed package version
[2012-10-23 10:35:56 +0530] gt: > Alternatively can I rename the package directory inside > /var/lib/pacman/local/ and %VERSION% string inside the desc file to > achieve the same? Sure you can. But what exactly are you trying to achieve? Avoid upgrading a specific package? The IgnorePkg option of pacman.conf can make that happen in a much more robust way. -- Gaetan
Re: [arch-general] Modify installed package version
On 10/22/2012 11:05 PM, gt wrote: > Hey guys > > is there a way to modify an installed package's version using pacman, > instead of upgrading the package. That is, only change the version in the > database, but don't actually upgrade a package. > > Alternatively can I rename the package directory inside > /var/lib/pacman/local/ and %VERSION% string inside the desc file to > achieve the same? > Yeah, in fact some times for a quick fix I don't even bother with the directory name, the desc file is enough.
[arch-general] Modify installed package version
Hey guys is there a way to modify an installed package's version using pacman, instead of upgrading the package. That is, only change the version in the database, but don't actually upgrade a package. Alternatively can I rename the package directory inside /var/lib/pacman/local/ and %VERSION% string inside the desc file to achieve the same?
Re: [arch-general] Exiting wpa_supplicant
On Mon, Oct 22, 2012 at 7:29 PM, Thomas Bächler wrote: > Am 22.10.2012 17:57, schrieb Nelson Marambio: > > I use wpa_supplicant in combination with the -B switch to establish the > > connection. After a pause of 10 seconds I pull an IP address by calling > > dhcpcd. > > I can't count the number of reasons why this is a bad idea. > > I've looked into this topic years ago, and the result is netcfg's > net-auto-wireless mode. > > > That's interesting. Why is that a bad idea? I used to do it by hand, waiting for wpa_supplicant to stablish a connection and then running dhcp. Nowadays I just use wicd but I'm interested to understand what could go wrong. -- Rafael Beraldo cabaladada.org
Re: [arch-general] autofs issue after location change
On 22/10/2012, Genes MailLists wrote: > I had used one of my autofs mounts last night on my laptop. This > morning I put it to sleep and moved to a different location where that > nfs server is not available. > > I am fully updated to testing repo (as of last night anyway :-) ). > > (i) pacman hung (tho I understand from > > > https://projects.archlinux.org/pacman.git/commit/?id=e183522e3168c4a31103b3c7910fa8d29333fb5a > > that this may be fixed .. tho that was quite quite some time > back so maybe something else is happening. That fix (“diskspace: only load filesystem info on demand”) is not in the 4.0.3 release; I think it’s probably waiting for a 4.1 release because it’s on the master branch. As for the rest of your problems I have no idea; I’m not familiar with “autofs” or “systemd” :) >(ii) Alerted by the hang - I tried to restart autofs via > systemctl restart autofs > > Perhaps I didn't wait long enough - but this did not complete. > >(iii) So I rebooted pc. The shutdown hung after systemd reported > [ok] for shutting off remote file systems. Again I only waited > a few minutes - perhaps it would have timed out after sufficiently long > - but how long? > > >(iii) was especially surpising to me - I thought systemd would kill > the daemon sooner. > >Can anyone share What is the right way of dealing with this 'dead > autofs mount' issue?
Re: [arch-general] Leafnode and Systemd
On Tue, Oct 23, 2012 at 12:34:20AM +0100, Whiskers wrote: > On Mon, 22 Oct 2012 18:40:23 -0400 Dave Reisner wrote: > > >On Mon, Oct 22, 2012 at 11:19:37PM +0100, Whiskers wrote: > >> Thank you to all those who responded :)) > >> > >> I now have Leafnode-2 up and running smoothly with systemd. > >> > >> I have created these files: > >> > >> $ cat /etc/systemd/system/leafnode.socket > >> [Unit] > >> Description=Leafnode NNTP Socket > >> > >> [Socket] > >> ListenStream=119 > >> Accept=yes > >> > >> [Install] > >> WantedBy=sockets.target > >> > >> and > >> > >> $ cat /etc/systemd/system/leafnode@.service > >> [Unit] > >> Description=Leafnode NNTP service > >> After=syslog.target > > > >This isn't needed. syslog is always available thanks to the journal > >socket. > > OK. > > >> > >> [Service] > >> ExecStart=/usr/local/sbin/leafnode > > > >/usr/local? > > That's where Leafnode-2 puts itself by default. I assumed you were using the package in [community]. > >> StandardInput=socket > >> User=news > >> > >> Access control depends entirely on ufw (iptables), rather than > >> specifying a hostname or IPv6 or IPv4 number in leafnode.socket, > >> although that would > > > >Binding to a specifc IP is hardly what I'd call access control. > > Wouldn't "ListenStream=127.0.0.1;119" prevent anyone not logged in to > localhost from using Leafnode? Sure. Nit: Would be a colon, not a semi-colon delimiter. > >> probably work instead. The ListenStream line could probably be omitted > >> entirely, unless some port other than 119 is required. > > > >Without the ListenStream declaration, systemd has no idea what port to > >open the socket on. It's needed. > > Xinetd doesn't need to be told. Isn't there a table of standard ports for > specified services? Yes, there's a table of standard ports -- it's /etc/services. It merely lets you refer to ports by name rather than by number. Something still needs to indicate what port to listen on, regardless of how its mentioned. So, I call bull on xinetd not needing to know this. _somehow_ it's being told. d
Re: [arch-general] Leafnode and Systemd
On Mon, 22 Oct 2012 18:40:23 -0400 Dave Reisner wrote: >On Mon, Oct 22, 2012 at 11:19:37PM +0100, Whiskers wrote: >> Thank you to all those who responded :)) >> >> I now have Leafnode-2 up and running smoothly with systemd. >> >> I have created these files: >> >> $ cat /etc/systemd/system/leafnode.socket >> [Unit] >> Description=Leafnode NNTP Socket >> >> [Socket] >> ListenStream=119 >> Accept=yes >> >> [Install] >> WantedBy=sockets.target >> >> and >> >> $ cat /etc/systemd/system/leafnode@.service >> [Unit] >> Description=Leafnode NNTP service >> After=syslog.target > >This isn't needed. syslog is always available thanks to the journal >socket. OK. >> >> [Service] >> ExecStart=/usr/local/sbin/leafnode > >/usr/local? That's where Leafnode-2 puts itself by default. >> StandardInput=socket >> User=news >> >> Access control depends entirely on ufw (iptables), rather than >> specifying a hostname or IPv6 or IPv4 number in leafnode.socket, >> although that would > >Binding to a specifc IP is hardly what I'd call access control. Wouldn't "ListenStream=127.0.0.1;119" prevent anyone not logged in to localhost from using Leafnode? >> probably work instead. The ListenStream line could probably be omitted >> entirely, unless some port other than 119 is required. > >Without the ListenStream declaration, systemd has no idea what port to >open the socket on. It's needed. Xinetd doesn't need to be told. Isn't there a table of standard ports for specified services? [...] >> -- >> -- ^^ >> -- Whiskers >> -- ~~ -- -- ^^ -- Whiskers -- ~~
Re: [arch-general] Leafnode and Systemd
On Mon, Oct 22, 2012 at 11:19:37PM +0100, Whiskers wrote: > Thank you to all those who responded :)) > > I now have Leafnode-2 up and running smoothly with systemd. > > I have created these files: > > $ cat /etc/systemd/system/leafnode.socket > [Unit] > Description=Leafnode NNTP Socket > > [Socket] > ListenStream=119 > Accept=yes > > [Install] > WantedBy=sockets.target > > and > > $ cat /etc/systemd/system/leafnode@.service > [Unit] > Description=Leafnode NNTP service > After=syslog.target This isn't needed. syslog is always available thanks to the journal socket. > > [Service] > ExecStart=/usr/local/sbin/leafnode /usr/local? > StandardInput=socket > User=news > > Access control depends entirely on ufw (iptables), rather than specifying > a hostname or IPv6 or IPv4 number in leafnode.socket, although that would Binding to a specifc IP is hardly what I'd call access control. > probably work instead. The ListenStream line could probably be omitted > entirely, unless some port other than 119 is required. Without the ListenStream declaration, systemd has no idea what port to open the socket on. It's needed. > > Run > > # systemctl start leafnode.socket > > and > > # systemctl enable leafnode.socket > > to start systemd listening for calls for Leafnode immediately and after > the next system boot. > > -- > -- ^^ > -- Whiskers > -- ~~
Re: [arch-general] Strange network problem
On Mon, Oct 22, 2012 at 10:15:18PM +, Fons Adriaensen wrote: > Hello all, > > I've got a strange problem with a machine that had a fresh install > three weeks ago. Nothing new has been installed on it since then. > > About one time in four, after that machine has been booted, a ssh > to it (on a LAN) fails with 'no route to host'. Using ip link and > ip addr on it shows everything is OK, it's not a NIC that gets the And 'ip r' shows the machine has a default route to the gateway? It's a two way street. Do you have any roblems with outbound connections originating from this machine? d > wrong name or so. The network on that machine is set up using netcfg, > in the recommended way (/etc/conf.d/netcfg). > > Rebooting has solved the problem in all cases. Sounds delightfully racy. > Any hints as to what is going wrong ? I'm not sure there's enough info here for anyone to do anything more than guess.
[arch-general] Strange network problem
Hello all, I've got a strange problem with a machine that had a fresh install three weeks ago. Nothing new has been installed on it since then. About one time in four, after that machine has been booted, a ssh to it (on a LAN) fails with 'no route to host'. Using ip link and ip addr on it shows everything is OK, it's not a NIC that gets the wrong name or so. The network on that machine is set up using netcfg, in the recommended way (/etc/conf.d/netcfg). Rebooting has solved the problem in all cases. Any hints as to what is going wrong ? TIA, -- FA A world of exhaustive, reliable metadata would be an utopia. It's also a pipe-dream, founded on self-delusion, nerd hubris and hysterically inflated market opportunities. (Cory Doctorow)
Re: [arch-general] Leafnode and Systemd
Thank you to all those who responded :)) I now have Leafnode-2 up and running smoothly with systemd. I have created these files: $ cat /etc/systemd/system/leafnode.socket [Unit] Description=Leafnode NNTP Socket [Socket] ListenStream=119 Accept=yes [Install] WantedBy=sockets.target and $ cat /etc/systemd/system/leafnode@.service [Unit] Description=Leafnode NNTP service After=syslog.target [Service] ExecStart=/usr/local/sbin/leafnode StandardInput=socket User=news Access control depends entirely on ufw (iptables), rather than specifying a hostname or IPv6 or IPv4 number in leafnode.socket, although that would probably work instead. The ListenStream line could probably be omitted entirely, unless some port other than 119 is required. Run # systemctl start leafnode.socket and # systemctl enable leafnode.socket to start systemd listening for calls for Leafnode immediately and after the next system boot. -- -- ^^ -- Whiskers -- ~~
Re: [arch-general] Exiting wpa_supplicant
[2012-10-22 17:57:30 +0200] Nelson Marambio: > I use wpa_supplicant in combination with the -B switch to establish > the connection. After a pause of 10 seconds I pull an IP address by > calling dhcpcd. This 10-second sleep is flaky. Instead, after you've started wpa_supplicant, run `wpa_cli -a /path/to/script -B` with a script roughly looking like: case "$2" in CONNECTED) [[ -f /run/dhcpcd-$1.pid ]] && dhcpcd -qx $1 dhcpcd -q $1 ;; DISCONNECTED) dhcpcd -qx $1 ;; esac -- Gaetan
Re: [arch-general] Exiting wpa_supplicant
Am 22.10.2012 17:57, schrieb Nelson Marambio: > I use wpa_supplicant in combination with the -B switch to establish the > connection. After a pause of 10 seconds I pull an IP address by calling > dhcpcd. I can't count the number of reasons why this is a bad idea. I've looked into this topic years ago, and the result is netcfg's net-auto-wireless mode. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Exiting wpa_supplicant
On Mon, Oct 22, 2012 at 11:57 AM, Nelson Marambio wrote: > Dear list, > > I try to write a small shellscript that (dis-)connects me with / from the > WLAN of my university. > > I use wpa_supplicant in combination with the -B switch to establish the > connection. After a pause of 10 seconds I pull an IP address by calling > dhcpcd. > > My question (in context of the wlan-disconnect-script): how can I exit > wpa_supplicant if it runs in the background ? Up to now it's done by "sudo > killall wpa_supplicant" but I guess it's not the best way. I suggest "wpa_cli terminate". See the wpa_cli manpage.
[arch-general] Exiting wpa_supplicant
Dear list, I try to write a small shellscript that (dis-)connects me with / from the WLAN of my university. I use wpa_supplicant in combination with the -B switch to establish the connection. After a pause of 10 seconds I pull an IP address by calling dhcpcd. My question (in context of the wlan-disconnect-script): how can I exit wpa_supplicant if it runs in the background ? Up to now it's done by "sudo killall wpa_supplicant" but I guess it's not the best way. Kind regards, Nelson.
Re: [arch-general] Is it proper that I add some material about raspberry pi on Arch over the Archwiki?
2012/10/22 Karol Blazewicz > On Mon, Oct 22, 2012 at 2:35 PM, Øyvind Heggstad > wrote: > > Just a small sidenote here: > > > > archlinux does not support arm. > > Yup. > The Czech R-Pi article I linked to has a note at the very top that > says (in English ;P) "Support for the ARM architecture is provided on > http://archlinuxarm.org/"; > Oki I've created it folks https://wiki.archlinux.org/index.php/Raspberry Used the Czech article as template to have consistence, still having problems with the mark up. Fixing it asap. Please help me :)
Re: [arch-general] [arch-dev-public] WARNING: changes to screen in testing
On Mon, Oct 22, 2012 at 14:13:22 -0400, Dave Reisner wrote: > Surely there's a way to tell screen to look in a different place > for sockets. Figure out the command to do so and advertise it in > a post_upgrade message as a crutch until the user can restart > their screen sessions. Or symlink old to new location? Worked for me. Geert -- geert.hendrickx.be :: ge...@hendrickx.be :: PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [arch-general] neo - german keyboard layout
On Mon, Oct 22, 2012 at 16:32:04 +0200, G. Schlisio wrote: > thanks for answering. > i added keymap to mkinitcpio, but where can i adjust the used > layout? before the hdd is decrypted (like, say, while entering the > password) it cannot access the /etc/vconsole.conf so there needs to > be an other place. mkinitcpio will automatically copy the necessary config (/etc/vconsole.conf in this case) into the initrd image, that's exactly what the HOOKS are for. Geert -- geert.hendrickx.be :: ge...@hendrickx.be :: PGP: 0xC4BB9E9F This e-mail was composed using 100% recycled spam messages!
Re: [arch-general] neo - german keyboard layout
Am 22.10.2012 08:50, schrieb Geert Hendrickx: On Thu, Oct 18, 2012 at 22:16:22 +0200, G. Schlisio wrote: hi list, i played around with neo2, an alternative kbd layout optimized for german. in my kde environment. the main concept of neo is using meta keys to shift between layers. for me, the meta4 key is not working on either side. i found some suggestions to solve this problem, but nothing worked so far. anybody out there knowing, how to fix this? and how can i enable neo in initramfs, for input of my encryption pw? For X11 and Linux console this is completely separate. For the console, you configure the keymap in /etc/vconsole.conf, and you add "keymap" to the HOOKS line in /etc/mkinitcpio.conf to have it loaded early in the initrd to enter your encryption pw. For X11 you either use KDE's keyboard settings (since Neo is apparantly shipped with xkeyboard-config, it should be listed by xkb), or you just run setxkbmap somewhere in your X startup scripts as suggested by Robbie. Geert (Colemak user) thanks for answering. i added keymap to mkinitcpio, but where can i adjust the used layout? before the hdd is decrypted (like, say, while entering the password) it cannot access the /etc/vconsole.conf so there needs to be an other place.
Re: [arch-general] neo - german keyboard layout
> For X11 and Linux console this is completely separate. > > For the console, you configure the keymap in /etc/vconsole.conf, and you > add "keymap" to the HOOKS line in /etc/mkinitcpio.conf to have it loaded > early in the initrd to enter your encryption pw. > > For X11 you either use KDE's keyboard settings (since Neo is apparantly > shipped with xkeyboard-config, it should be listed by xkb), or you just > run setxkbmap somewhere in your X startup scripts as suggested by Robbie. Most of the login managers (gdm, xdm, lightdm at least do) will use the $HOME/.Xkbmap file to set your xkb settings. You just put the setxkbmap options in the file, in the OP case that would be "-layout de,neo" I guess. -- damjan
[arch-general] autofs issue after location change
I had used one of my autofs mounts last night on my laptop. This morning I put it to sleep and moved to a different location where that nfs server is not available. I am fully updated to testing repo (as of last night anyway :-) ). (i) pacman hung (tho I understand from https://projects.archlinux.org/pacman.git/commit/?id=e183522e3168c4a31103b3c7910fa8d29333fb5a that this may be fixed .. tho that was quite quite some time back so maybe something else is happening. (ii) Alerted by the hang - I tried to restart autofs via systemctl restart autofs Perhaps I didn't wait long enough - but this did not complete. (iii) So I rebooted pc. The shutdown hung after systemd reported [ok] for shutting off remote file systems. Again I only waited a few minutes - perhaps it would have timed out after sufficiently long - but how long? (iii) was especially surpising to me - I thought systemd would kill the daemon sooner. Can anyone share What is the right way of dealing with this 'dead autofs mount' issue? Thanks gene/
Re: [arch-general] Arch on SSD!
Am 22.10.2012 12:57, schrieb Mauro Santos: > On 22-10-2012 10:57, Paul Gideon Dann wrote: >> I always use the form /dev/mapper/vg-lv, though. The /dev/vg/lv form >> sometimes isn't available in early boot. I think it depends of udev, and >> has >> certainly broken for me in the past. >> >> Paul >> > > Would /dev/vg/lv be as reliable as /dev/mapper/vg-lv or is the latter > preferable? This is no longer the case. Actually, if something with udev fails, neither /dev/vg/lv nor /dev/mapper/vg-lv will exist, but only /dev/dm-N with some arbitrary number N. While LVM and udev still don't like each other, these problems have mostly been fixed now. signature.asc Description: OpenPGP digital signature
Re: [arch-general] Arch on SSD!
On 22-10-2012 10:57, Paul Gideon Dann wrote: > I always use the form /dev/mapper/vg-lv, though. The /dev/vg/lv form > sometimes isn't available in early boot. I think it depends of udev, and has > certainly broken for me in the past. > > Paul > Would /dev/vg/lv be as reliable as /dev/mapper/vg-lv or is the latter preferable? -- Mauro Santos
Re: [arch-general] Is it proper that I add some material about raspberry pi on Arch over the Archwiki?
On Mon, Oct 22, 2012 at 2:35 PM, Øyvind Heggstad wrote: > Just a small sidenote here: > > archlinux does not support arm. Yup. The Czech R-Pi article I linked to has a note at the very top that says (in English ;P) "Support for the ARM architecture is provided on http://archlinuxarm.org/";
Re: [arch-general] Is it proper that I add some material about raspberry pi on Arch over the Archwiki?
On Mon, 22 Oct 2012 03:17:50 -0200 Victor Silva wrote: > Guys some time ago I got a Pi. I know there is much to be done with > it, so far I`ve installed arch on it, running a seed box at the > moment. The idea would use the power of archwiki to have people > sharing information and having cool ideas for raspberry pi. I`ve seen > guys doing great stuff like a solar powered py running SETI@Home, > mods to run pinball machines and so on. But all this information is > still scattered on the Internet making it a bit harder to people just > starting up. > > For instance: > http://www.raspberrypi-tutorials.co.uk/ > http://elinux.org/RPi_Tutorials > > Just as example are quite scattered regarding format. So maybe we > could use the community to build a great wiki. The > http://archlinuxarm.org/ seems to have no wiki. (Do they use > https://wiki.archlinux.org/ ?) Could one please give me some > pointers of how could I start it? > > > I tried to get some info on archlinuxarm.org website but so far no > answer. http://archlinuxarm.org/forum/viewtopic.php?f=31&t=3992 > > > Hope this can work. > > Regards, > vfbsilva Just a small sidenote here: archlinux does not support arm. The archlinux-arm project is a compleatly independent project and is not supported by archlinux at all, and a disclaimer for this should probably be put on the wiki page. On the other hand, 64bit support in arch started out as a community project too, so you never know what the future will hold :)
Re: [arch-general] Arch on SSD!
On Monday 22 Oct 2012 10:34:48 Mauro Santos wrote: > Or better yet, use UUID, I've been using UUIDs for a long time and they > never failed me, while every once in a while I see people with problem > when using /dev/sd*, I don't recall seeing people with problems when > using lvm though, maybe those know what they are doing a lot better :p I always prefer LVM names to UUIDs. I use UUIDs for filesystems on raw partitions, but LVM is clever enough to always use the same name regardless of where the physical device is attached. After all, the point of LVM is to shield you from these sorts of details. I always use the form /dev/mapper/vg-lv, though. The /dev/vg/lv form sometimes isn't available in early boot. I think it depends of udev, and has certainly broken for me in the past. Paul
Re: [arch-general] Arch on SSD!
On 22-10-2012 03:51, John Hutchison wrote: > On Mon, Oct 22, 2012 at 02:11:23AM +0100, nailz wrote: >> but should the LVM partition be marked as ext4 in fstab? > > According to few sources (gentoo wiki, linuxconfig.org) on how fstab > should be: they have the LVM volumes labeled as ext4 (or whatever the > actual fs is) but the mountpoint is not /dev/sdx#, rather it uses the > lvm dev mapping, or however you call it: > > from http://linuxconfig.org/Linux_lvm_-_Logical_Volume_Manager: >> /dev/mynew_vg/vol01 /home/foobar/ ext3 yadda yadda > > from http://wiki.gentoo.org/wiki/LVM#.2Fetc.2Ffstab: >> /dev/vg0/lvol1 /mnt/data ext4 noatime 0 2 > Or better yet, use UUID, I've been using UUIDs for a long time and they never failed me, while every once in a while I see people with problem when using /dev/sd*, I don't recall seeing people with problems when using lvm though, maybe those know what they are doing a lot better :p > So whatever Andrea called their virtual group is what it must be set to. > If you go to the Archwiki, it uses 'VolGroup00' as the volume group. > > Use vgdisplay to figure out the volume group name. > > Note: I do not use LVM myself, so please keep that in mind. This is just > from my cursory research > > > -- > John Hutchison > Programmieren und > Informatik-Abteilung > Feiern Sie 20 Jahre Linux! > gplus.to/athetius > -- Mauro Santos
