| ham5urg | Ansible is a good approach for scripting a system though. | 00:00 |
|---|---|---|
| ham5urg | With Devuan a good combination. | 00:01 |
| rwp | ham5urg, You can set EDITOR='edit script here' such as: EDITOR="perl -pi -e 's@^XKBLAYOUT=.*@XKBLAYOUT=\"us\"@'" dpkg-reconfigure keyboard-configuration | 00:43 |
| rwp | Also, there are TWO different keyboard configurations. One is for the kernel vt console and then Xorg with setxkbmap is on top of that. | 00:44 |
| rwp | For the kernel vt console I do a custom hack in /etc/rc.local with dumpkeys and loadkeys. For X I use a combination of setxkbmap, xmodmap, and xset. | 00:46 |
| FilipZ | rrq: Sorry that I ask about this only now. How exactly could I do this pre-up, so it would kill the locked dhclient processes, but also wouldn't crash networking in another way? | 16:57 |
| buZz | Bug report submitted to: Devuan Bug Tracking System <submit@bugs.devuan.org> | 17:31 |
| buZz | w00t | 17:31 |
| buZz | (smpq 1.6-2 on arm64 crashes on usage, while my own 1.6 compiles work just fine) | 17:31 |
| buZz | no issues on arm32,x64,x86 | 17:31 |
| FilipZ | rrq: Are you online now? | 17:56 |
| FilipZ | Could somebody help with setting ifupdown to kill the remaining dhclient processes before automatically bringing up again the bugged wlan0 interface? | 18:01 |
| FilipZ | I don't know how should I do it so it would work correctly. | 18:02 |
| buZz | FilipZ: why not just disable wlan0 if you dont want it? | 18:17 |
| buZz | (edit /etc/network/interfaces) | 18:18 |
| FilipZ | buZz: And why disabling my only option for the internet connection would be of any help? I did not write even once that I don't need it. I obviously need a way to "fix it" so I could use it without this issue. | 18:21 |
| buZz | oh i dont know, you said bugged wlan0 | 18:21 |
| buZz | cant know what you're doing if you dont say :P | 18:21 |
| FilipZ | I am using wpa_gui to connect with the internet. I found out that my hardware malfunctions for some unknown reasons, causing my wireless software now either repeatedly disconnect and connect again(the lighter issue), and in the worse, but less often case, it breaks in some way, and then I don't know a way to make it work again other then turning off an on the entire system. I am asking for the help with that first, lighter issue, a | 18:29 |
| FilipZ | an "fix it" temporarily by bringing the wlan0 down with ifdown, then killing the dhclient processes(when it happens it spawns multiple of them, while one of them gets locked), and then bringing the interface up again. I am asking how to make this happen automatically. | 18:29 |
| FilipZ | So it would kill the dhclient processes before it would spawn another and then connect again. | 18:30 |
| FilipZ | buZz: Now could you tell how could I do this? | 18:32 |
| rwp | FilipZ, Simplest might be to add a "down pkill dhclient" line to the /etc/network/interfaces wlan0 stanza. | 18:54 |
| FilipZ | rwp: I got adviced to add "pre-up pkill -9 dhclient" after the "iface default inet dhcp" line, but after I did so, the system started with the wpa_cli and wpa_gui turned on three times, and without dhclient at all. | 19:45 |
| FilipZ | So where should I add that line, and what "down" on the beginning means? | 19:46 |
| bb|hcb | FilipZ: pre-up is better. You can add the line on the bottom | 20:16 |
| rwp | What I do not understand is what makes your environment FilipZ so problematic. As compared to mine for example. | 20:19 |
| rwp | In Jessie's wicd everything worked perfectly. In Stretch wicd became buggy and would leave me with multiple dhclients running that I would need to kill. | 20:19 |
| rwp | But then I switched to a wpa_supplicant roaming config without wicd, because of the python 2 deprecation. wpa_supplicant roaming has never had dhclient problems for me. | 20:20 |
| rwp | I have experienced a wpa_supplicant problem if I have two Access Points both configured both in range but both weak. | 20:20 |
| rwp | wpa_supplicant will decide to drop the connected one and then try the other. | 20:21 |
| rwp | And then decide the same thing for the other, too weak, drop it, try the other. | 20:21 |
| rwp | Repeating that loop endlessly because it keeps thinking the other will be better. | 20:21 |
| rwp | I have to remove one of the AP configs in order to have it avoid trying it and looping. | 20:21 |
| rwp | But never a problem with dhclient management with it. YMMV! | 20:22 |
| FilipZ | In my case it repeatedly connects and disconnects to the single access point. | 20:33 |
| FilipZ | Even when the signal is strong. | 20:33 |
| FilipZ | rwp: I added that line, so it would look like this: https://paste.debian.net/1257512/ however after "ifdown --force wlan0", the dhclient stays, so it doesn't work, right? | 20:47 |
| FilipZ | Also rrq: in the line "pre-up pkill -9 dhclient", what is "-9" for? I couldn't find this flag in the man description. | 20:51 |
| bb|hcb | FilipZ: -9 (SIGKILL) is unconditional process termination; in that way the process will not do any cleanup or delay before the exit. I am not sure how good is that with dhclient, because it is better to let it release first. Personally i'd do something like "pkill dhclient; sleep 1; pkill -9 dhclient" | 21:04 |
| rrq | FilipZ: yes pre-up is better, and yes a "nice" tickle first and a kick in the belly after.. then the next line is another pre-up with start of dhclient... | 22:19 |
| rrq | you need to run it once like before the killing so that you get the full command line to use (from pgrep -a dhclient) | 22:21 |
| rrq | then go bacl to "manual" and add the killing plus a pre-up with the captured dhclient command | 22:21 |
| rrq | and then it doesn't hurt with also having a "down pkill dhclient" | 22:22 |
| rrq | (I think you also have your dhclient command line soemwhere in the backlog of this chat) | 22:23 |
| rrq | actually, perhaps the dhclient start command should be as an "up" command rather than a "pre-up" ... as there is no need for it to start before the interface is brought up at link level | 22:25 |
| rrq | another thing to bear in mind is that dhclient has its own configuration file under /etc/dhcp/dhclient.conf, but the default setup works well for standard domestic setup. | 22:29 |
| rrq | my dhclient command is: /sbin/dhclient -4 -v -i -pf /run/dhclient.wlan0.pid -lf /var/lib/dhcp/dhclient.wlan0.leases -I -df /var/lib/dhcp/dhclient6.wlan0.leases wlan | 22:35 |
| rrq | and I think yours would be the same .. (and of course the "up" marker before it) | 22:36 |
| ham5urg | What's about /etc/default/networking ? Is it to replace /etc/network/interfaces ? | 23:36 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!