Re: migrate python script from sudo to doas
Hello Markus, I cannot reproduce your problem. As you can see here under I can create a user "test1" on the command line, and, with the same userid, I can create it with python2 and python3 too. (I'm running 6.4) I see 2 possible cause : - your python script, - or maybe the userid for which your python script runs is not the one defined in doas.conf. regards The python script I use is: " import subprocess cmd = "doas useradd -u 9003 -g=uid -s /sbin/nologin -d /tmp test3" cmd_list = cmd.split() exit = subprocess.check_call(cmd_list) " the tests results are: " obsd-laptop:~$ doas useradd -u 9001 -g=uid -s /sbin/nologin -d /tmp test1 obsd-laptop:~$ echo $? 0 obsd-laptop:~$ python2.7 test.py obsd-laptop:~$ echo $? 0 obsd-laptop:~$ userinfo test2 login test2 passwd * uid 9002 groups test2 change NEVER class gecos dir /tmp shell /sbin/nologin expire NEVER obsd-laptop:~$ python3.6 test.py obsd-laptop:~$ echo $? 0 obsd-laptop:~$ userinfo test3 login test3 passwd * uid 9003 groups test3 change NEVER class gecos dir /tmp shell /sbin/nologin expire NEVER " On Tue, Oct 30, 2018 at 1:22 PM Markus Rosjat wrote: > Hi, > > as I stated before on a cmd is no problem, Im using 6.4 release > > > Am 30.10.2018 um 12:56 schrieb Solene Rapenne: > > Markus Rosjat wrote: > >> hi all, > >> > >> I have some old python scripts that using os.spawnl to execute stuff > >> like useradd combined with sudo. This worked just fine on systems with > >> sudo installed but these days we have doas and its totally enough for > >> things I use to do so I said to myself "lets update these old scripts > >> ..." . In code this was basically replasing os.spawnl with > >> subprocess.check_call but when I run this the useradd command doesnt > >> get executed by the script. On the cmd it does, so this works on cmd: > >> > >> doas useradd -u 666 -g =uid -s /sbin/nologin -d > >> /var/mail/domain.tld/vmailuser0666 vmailuser0666 > >> > >> but in the script I with the code like this: > >> > >>exit = subprocess.check_call(['doas', 'useradd', '-u %s' % user_id, > >> '-g =uid', > >> '-s /sbin/nologin', > >> '-d %s' % mb_parent_dir, > >> user_name]) > >> > >> I get an exception that seems to be related to the fact that doas isnt > >> really working here > >> > >> doas: Authorization failed <- this comes from the script even the > >> provided password is correct > >> > >> Traceback (most recent call last): > >> File "/root/scripts/mb_add", line 244, in > >> mb_addresses) > >> File "/root/scripts/mb_add", line 174, in add_mailbox > >> user_name]) > >> File "/usr/local/lib/python2.7/subprocess.py", line 190, in > check_call > >> raise CalledProcessError(retcode, cmd) > >> subprocess.CalledProcessError: Command '['doas', 'useradd', '-u 666', > >> '-g =uid', '-s /sbin/nologin', '-d /var/mail/domain.tld/vmailuser666', > >> 'vmailuser666']' returned non-zero exit status 1 > >> > >> So does someone had some issues with migrating scripts from sudo to > >> doas, then some help or hintw would be very appreciated. > >> > >> > >> regards > > hi > > > > what openbsd version are you using? > > did you try the command outside of python? > > > > There were issues with doas a few days ago in snapshots. > > > > -- > Markus Rosjatfon: +49 351 8107224mail: ros...@ghweb.de > > G+H Webservice GbR Gorzolla, Herrmann > Königsbrücker Str. 70, 01099 Dresden > > http://www.ghweb.de > fon: +49 351 8107220 fax: +49 351 8107227 > > Bitte prüfen Sie, ob diese Mail wirklich ausgedruckt werden muss! Before > you print it, think about your responsibility and commitment to the > ENVIRONMENT > >
Re: chrome 68 and protonmail
For your info ... otter-browser is not working with protonmail. But midori is working fine. regards On Fri, Sep 14, 2018 at 9:14 AM Tiemen Werkman wrote: > > -Original Message- > > From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf > > Of vincent delft > > Sent: Friday, September 14, 2018 7:39 AM > > To: OpenBSD misc > > Subject: chrome 68 and protonmail > > > > Hello, > > > > With the last version of Chrome (Chromium 68.0.3440.106) on -current, I > > can > > no more login in protonmail. > > > > In fact after the 2nd login screen chrome complains about an issue. > > > > By looking at the console, I see this message: > > " > > <--- Last few GCs ---> > > > > [13615:0x1b00ec7000]19499 ms: Scavenge 28.5 (34.8) -> 28.0 (34.8) > > MB, > > 0.7 / 0.0 ms (average mu = 1.000, current mu = 1.000) idle task > > [13615:0x1b00ec7000]20552 ms: Scavenge 28.9 (34.8) -> 28.2 (34.8) > > MB, > > 4.9 / 0.2 ms (average mu = 1.000, current mu = 1.000) idle task > > [13615:0x1b00ec7000]24816 ms: Scavenge 29.1 (34.8) -> 28.3 (33.8) > > MB, > > 2.2 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation > > failure > > > > > > <--- JS stacktrace ---> > > > > JS stack trace = > > > > 0: ExitFrame [pc: 0x30a55ec5c33d] > > 1: InternalFrame [pc: 0x30a55ec1238c] > > Security context: 0x2471c02cba29 > https://mail.protonmail.com> > > 2: new constructor(aka u) [0x6ed0e8a85b9] [ > > https://mail.protonmail.com/openpgp.45fc464591fddb524fc0c8f83f781965944 > > 76934.js:2] > > [bytecode=0x23c4aa2110b1 offset=84](this=0x17ad66748f99 > 0xa7fcf3b2669>,e=0x17ad66748f41 ) > > 3: ConstructFrame [pc: 0x3... > > > > " > > > > I've cleared cache, config, ... but the problem persist. > > > > Am I the only one having such problem ? > > > > Note: Firefox cannot work for protonmail because of javascript issue (I > > do > > not remember the exact problem). > > Is there an another browser for protonmail ? > > > > regards > > Where is the latest version of chromium? > I've just checked several mirrors and I can't seem to find it. > > Tiemen Werkman > >
chrome 68 and protonmail
Hello, With the last version of Chrome (Chromium 68.0.3440.106) on -current, I can no more login in protonmail. In fact after the 2nd login screen chrome complains about an issue. By looking at the console, I see this message: " <--- Last few GCs ---> [13615:0x1b00ec7000]19499 ms: Scavenge 28.5 (34.8) -> 28.0 (34.8) MB, 0.7 / 0.0 ms (average mu = 1.000, current mu = 1.000) idle task [13615:0x1b00ec7000]20552 ms: Scavenge 28.9 (34.8) -> 28.2 (34.8) MB, 4.9 / 0.2 ms (average mu = 1.000, current mu = 1.000) idle task [13615:0x1b00ec7000]24816 ms: Scavenge 29.1 (34.8) -> 28.3 (33.8) MB, 2.2 / 0.0 ms (average mu = 1.000, current mu = 1.000) allocation failure <--- JS stacktrace ---> JS stack trace = 0: ExitFrame [pc: 0x30a55ec5c33d] 1: InternalFrame [pc: 0x30a55ec1238c] Security context: 0x2471c02cba29 https://mail.protonmail.com> 2: new constructor(aka u) [0x6ed0e8a85b9] [ https://mail.protonmail.com/openpgp.45fc464591fddb524fc0c8f83f78196594476934.js:2] [bytecode=0x23c4aa2110b1 offset=84](this=0x17ad66748f99 ,e=0x17ad66748f41 ) 3: ConstructFrame [pc: 0x3... " I've cleared cache, config, ... but the problem persist. Am I the only one having such problem ? Note: Firefox cannot work for protonmail because of javascript issue (I do not remember the exact problem). Is there an another browser for protonmail ? regards
Re: network connectivity problem (ifconfig, arp, ...)
Re-hello, The trunk is working fine at my office (between cable and wifi). I will need more time to better evaluate it. But this sounds indeed matching the need. But With this trunk now configured, I'm no more able to select the wifi at customer site. Indeed, at customer, I have 2 different nwid, and I'm used to switch from one to the other via simple ifconfig commands. When I will have time, I'll read some faq or man pages, to solve this situation via few ifconfig commands. In fact, I remain with my initial question: why arp having an entry with address "incomplete" on em0 does not perform the task when iwm0 is triggered and request a connection to my firewall ? The fw is running on the same address, just the path (netif) that change. regards On Mon, Sep 3, 2018 at 10:58 PM Vincent wrote: > Hello stefan, > > Hum... it could be similar situations. > > I've found an article combining the "join" and the trunk: > https://dataswamp.org/~solene/2018-08-30-openbsd-trunk.html > > I'll do same setup and will see > > Thanks. > > V. > > > > > > > > On 3 September 2018 20:26:27 CEST, Stefan Sperling wrote: >> >> On Mon, Sep 03, 2018 at 07:46:09PM +0200, vincent delft wrote: >> >>> Hello, >>> >>> I'm running -current and enjoy the new "join" feature of hostname.if. >>> >>> Nevertheless, I have sometime issues to have an internet connection. >>> >>> The context: >>> I have wifi and cable possibilities to connect the same network. Normaly I >>> prefer the network connection, so at my desk I plug the cable and use it. >>> But in some cases, I disconnect my laptop and use the wifi connection. >>> >>> Problem: >>> The wifi is well connected to my nwid, but the connectivity is not working >>> (cannot ping my main firewall to connect internet). >>> I think the problem is linked to wrong arp table (cfr here under) >>> >>> Why the arp entry for my firewall remains "expired" so long (could be more >>> than 10 minuntes) ? >>> Why a "doas arp -ad" does not remove this bad fw entry from the table ? >>> What could I do to solve the issue without rebooting the laptop ? (If I >>> reboot the laptop, this solve the problem). >>> >>> >>> >>> e5450:~$ arp -a >>> Host Ethernet AddressNetif Expire >>> Flags >>> fw (incomplete) em0 expired >>> 192.168.3.15 10:02:b5:83:40:41iwm0 permanent l >>> 192.168.3.16 f8:ca:b8:50:84:15 em0 permanent l >>> >> >> Didn't we already discuss the same question back in July? >> https://marc.info/?l=openbsd-misc=153220020618146=2 >> >> Again, try trunk(4). >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. >
network connectivity problem (ifconfig, arp, ...)
Hello, I'm running -current and enjoy the new "join" feature of hostname.if. Nevertheless, I have sometime issues to have an internet connection. The context: I have wifi and cable possibilities to connect the same network. Normaly I prefer the network connection, so at my desk I plug the cable and use it. But in some cases, I disconnect my laptop and use the wifi connection. Problem: The wifi is well connected to my nwid, but the connectivity is not working (cannot ping my main firewall to connect internet). I think the problem is linked to wrong arp table (cfr here under) Why the arp entry for my firewall remains "expired" so long (could be more than 10 minuntes) ? Why a "doas arp -ad" does not remove this bad fw entry from the table ? What could I do to solve the issue without rebooting the laptop ? (If I reboot the laptop, this solve the problem). e5450:~$ arp -a Host Ethernet AddressNetif Expire Flags fw (incomplete) em0 expired 192.168.3.15 10:02:b5:83:40:41iwm0 permanent l 192.168.3.16 f8:ca:b8:50:84:15 em0 permanent l
Re: Why openbsd use only 2 of my 4 CPU ?
Thanks Indeed it was very simple, sysctl hw.smt=1 solve the situation. Now my 4 cpu are working all together. I thought this problem was linked to some ACPI related features (like I did on this machine some months ago where I finally find the cause by disabling ichiic) I was on the wrong direction. It's true that those 2 CPU are not "real one", but I feel the difference when using libreoffice. Regards On Wed, Jul 25, 2018 at 8:01 PM vincent delft wrote: > Hello, > > I've migrated to -current to test the auto-join, but since then, my system > is slow. Specially with libreoffice, firefox, ... > > By looking at top, I've saw that only 2 CPU are actually running. > > (Should I say that with OpenBSD-6.3 this was not the case.) > > What can I do ? > In which direction could I search for a solution ? > > The dmesg and Top are here after. > > regards > > ANNEXES: > -- > > Top > - > load averages: 2.06, 0.88, > 0.38 > e5450.home.lan 19:46:08 > 45 processes: 1 running, 42 idle, 2 on > processor > up 0:06 > CPU0 states: 56.3% user, 0.0% nice, 18.0% sys, 5.8% spin, 0.6% intr, > 19.4% idle > CPU1 states: 50.6% user, 0.0% nice, 21.0% sys, 3.4% spin, 0.0% intr, > 25.0% idle > CPU2 states: 0.0% user, 0.0% nice, 0.0% sys, 0.0% spin, 0.0% intr, > 100% idle > CPU3 states: 0.0% user, 0.0% nice, 0.0% sys, 0.0% spin, 0.0% intr, > 100% idle > Memory: Real: 753M/1649M act/tot Free: 6171M Cache: 628M Swap: 0K/4220M > > PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND > 49990 vi590 405M 360M onproc/0 - 0:30 76.27% firefox > 49459 vi 20 362M 276M sleep/0 poll 0:29 24.56% firefox > 69993 vi 20 31M 54M run/0 poll 0:12 4.98% Xorg > 16268 vi 20 216M 136M sleep/0 poll 0:06 2.69% firefox > 58451 vi 20 1524K 3048K sleep/1 select0:03 1.71% compton > 9141 vi 20 188M 99M sleep/1 poll 0:03 1.56% firefox > 41741 vi 20 3560K 15M sleep/1 select0:05 0.44% tint2 > 43511 vi 20 8036K 14M sleep/0 select0:01 0.00% xterm > 1 root 100 404K 444K idle wait 0:01 0.00% init > 78121 vi 20 5596K 17M sleep/0 poll 0:01 0.00% openbox > > > > > DMESG: > --- > OpenBSD 6.3-current (GENERIC.MP) #140: Wed Jul 25 08:37:02 MDT 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8456654848 (8064MB) > avail mem = 8191193088 (7811MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed750 (89 entries) > bios0: vendor Dell Inc. version "A11" date 11/18/2015 > bios0: Dell Inc. Latitude E5450 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF! SSDT > SSDT SSDT SSDT PCCT SSDT SSDT SSDT SLIC MSDM DMAR > acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) > PEG2(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) > RP04(S4) PXSX(S4) RP05(S4) [...] > acpitimer0 at acpi0: 3579545 Hz, 24 bits > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2694.16 MHz > cpu0: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu0: 256KB 64b/line 8-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges > cpu0: apic clock running at 99MHz > cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.78 MHz > cpu1: > FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN > cpu1: 256KB 64b/line 8-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 1 (application processor) > cpu2: Int
Why openbsd use only 2 of my 4 CPU ?
Hello, I've migrated to -current to test the auto-join, but since then, my system is slow. Specially with libreoffice, firefox, ... By looking at top, I've saw that only 2 CPU are actually running. (Should I say that with OpenBSD-6.3 this was not the case.) What can I do ? In which direction could I search for a solution ? The dmesg and Top are here after. regards ANNEXES: -- Top - load averages: 2.06, 0.88, 0.38 e5450.home.lan 19:46:08 45 processes: 1 running, 42 idle, 2 on processor up 0:06 CPU0 states: 56.3% user, 0.0% nice, 18.0% sys, 5.8% spin, 0.6% intr, 19.4% idle CPU1 states: 50.6% user, 0.0% nice, 21.0% sys, 3.4% spin, 0.0% intr, 25.0% idle CPU2 states: 0.0% user, 0.0% nice, 0.0% sys, 0.0% spin, 0.0% intr, 100% idle CPU3 states: 0.0% user, 0.0% nice, 0.0% sys, 0.0% spin, 0.0% intr, 100% idle Memory: Real: 753M/1649M act/tot Free: 6171M Cache: 628M Swap: 0K/4220M PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND 49990 vi590 405M 360M onproc/0 - 0:30 76.27% firefox 49459 vi 20 362M 276M sleep/0 poll 0:29 24.56% firefox 69993 vi 20 31M 54M run/0 poll 0:12 4.98% Xorg 16268 vi 20 216M 136M sleep/0 poll 0:06 2.69% firefox 58451 vi 20 1524K 3048K sleep/1 select0:03 1.71% compton 9141 vi 20 188M 99M sleep/1 poll 0:03 1.56% firefox 41741 vi 20 3560K 15M sleep/1 select0:05 0.44% tint2 43511 vi 20 8036K 14M sleep/0 select0:01 0.00% xterm 1 root 100 404K 444K idle wait 0:01 0.00% init 78121 vi 20 5596K 17M sleep/0 poll 0:01 0.00% openbox DMESG: --- OpenBSD 6.3-current (GENERIC.MP) #140: Wed Jul 25 08:37:02 MDT 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8456654848 (8064MB) avail mem = 8191193088 (7811MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed750 (89 entries) bios0: vendor Dell Inc. version "A11" date 11/18/2015 bios0: Dell Inc. Latitude E5450 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF! SSDT SSDT SSDT SSDT PCCT SSDT SSDT SSDT SLIC MSDM DMAR acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2694.16 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.78 MHz cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 1 (application processor) cpu2: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.77 MHz cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,IBRS,IBPB,STIBP,SENSOR,ARAT,XSAVEOPT,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 1, core 0, package 0 cpu3 at mainbus0: apid 3 (application processor) cpu3: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.77 MHz cpu3:
strange observations during my auto-join tests
Hello Peter, all, I've just tested auto-join since 13 of july. First of all. THANKS !!! It works great. This email is just because I've observed 2 strange situations. I don't know if this is linked to auto-join or if this caused by errors on my setup. 1) egress group is not following the connected interface. To reproduce it, just establish a connection via a cable. ifconfig will show you that egress group is on that connection. Pull-off the ehternet cable and run "doas sh /etc/netstart". The system will switch perfectly to the wifi connection described in the hostname.if file. But, if I do a ifconfig, I still see the egress group on the cable interface. This was not my expectation. I thought that the egress group will switch too to the new running interface. 2) Time to times, the connection is correctly established on the correct interface (for example from cable to wifi), but arp shows that the arp table for few machines remains on the wrong interface. I have to run "doas arp -ad" several times to remove this bad entry in the arp table. Is there a better way to avoid such situation ? Thanks for your feedbacks. ANNEXES - e5450:~$ ifconfig em0: flags=8843 mtu 1500 lladdr f8:ca:b8:50:84:15 index 1 priority 0 llprio 3 groups: egress media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause) status: active inet 192.168.3.16 netmask 0xff00 broadcast 192.168.3.255 iwm0: flags=8802 mtu 1500 lladdr 10:02:b5:83:40:41 index 2 priority 4 llprio 3 groups: wlan media: IEEE802.11 autoselect (HT-MCS12 mode 11n) status: no network ieee80211: join Linksys19594 wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp inet 192.168.3.15 netmask 0xff00 broadcast 192.168.3.255 e5450:~$ doas sh /etc/netstart em0: no link .. sleeping iwm0: no link .. got link iwm0: bound to 192.168.3.15 from 192.168.3.1 (00:22:4d:ac:30:fd) e5450:~$ ifconfig em0: flags=8843 mtu 1500 lladdr f8:ca:b8:50:84:15 index 1 priority 0 llprio 3 groups: egress media: Ethernet autoselect (none) status: no carrier inet 192.168.3.16 netmask 0xff00 broadcast 192.168.3.255 iwm0: flags=8843 mtu 1500 lladdr 10:02:b5:83:40:41 index 2 priority 4 llprio 3 groups: wlan media: IEEE802.11 autoselect (HT-MCS1 mode 11n) status: active ieee80211: join Linksys19594 chan 10 bssid c8:d7:19:4c:76:73 61% wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp inet 192.168.3.15 netmask 0xff00 broadcast 192.168.3.255 e5450:~$ arp -a Host Ethernet AddressNetif Expire Flags fw (incomplete) em0 expired nas (incomplete) em0 expired 192.168.3.15 10:02:b5:83:40:41iwm0 permanent l 192.168.3.16 f8:ca:b8:50:84:15 em0 permanent l 192.168.3.20 c8:d7:19:4c:76:72iwm0 19m3s
which mirrors list ?
Hello, I'm just discovering that there are several sources of mirrors for http(s) sites. Is there any specific reasons why different sources with different content ? Are they all up-to-date ? https://ftp.openbsd.org/pub/OpenBSD/ftplist https://ftp.openbsd.org/pub/OpenBSD/snapshots/ftplist https://www.openbsd.org/ftp.html Many thanks Vincent
Re: interrupt at 50% on dell E5450
I'm back with some interesting info :-). By disabling each acpi module, I've discovered that the problem disappeared when I disable "acpiprt" in UKC. Based on the manpage, this module maps the PCI ... So, I've disabled each PCI. interrupts are gone when I disable "ichiic" in UKC :-) . (When I do not disable it it link to iic and then to spdmem0 (cfr dmesg in my previous email)) After such desabling, the rest of the machine seams to work. But I have to check ii more deeply. At least "Top" says that my 8GB memory are still present note: my laptop speaker is still making small noise when not muted. Questions: What is this modeule "ichiic" ? What am I missing by disabling it ? Why this module create interruputs on this Dell machine (e5450) ? Is there a link with the speaker ? rgds
Re: interrupt at 50% on dell E5450
Hello, I've remarked that the speakers of the laptop are doing a small noise when I do not listen music. If I mute the speaker (mixerctl outputs.master.mute) this little noise disappear. I thought this was an Hardware issue. So, I've re-installed the orignial disk I've received with the machine (which runs windows 10). But when I run Windows, then there is no strange noise at all from the speakers. Even when they are idle. So, I don't think this noise in the speakers is an hardware issue. So, it seems that azalia is generating some troubles. No ? An another element ... This strange noise is not in the headphone when I plug them. No idea is this is related to the interrups problem. rgds whitout headphone --- outputs.spkr_source=mix2 outputs.spkr_mute=off outputs.spkr_eapd=on outputs.hp_source=mix3 outputs.hp_mute=off outputs.hp_boost=off outputs.hp_eapd=on outputs.line_source=mix2 outputs.line_mute=off outputs.line_boost=off outputs.line_eapd=on outputs.hp_sense=unplugged outputs.line_sense=unplugged outputs.mic2_sense=unplugged outputs.spkr_muters=hp,line outputs.master=204,204 outputs.master.mute=off outputs.master.slaves=dac-2:3,dac-0:1,spkr,hp,line With headphone - e5450:~$ mixerctl | grep outputs outputs.spkr_source=mix2 outputs.spkr_mute=on outputs.spkr_eapd=on outputs.hp_source=mix3 outputs.hp_mute=off outputs.hp_boost=off outputs.hp_eapd=on outputs.line_source=mix2 outputs.line_mute=off outputs.line_boost=off outputs.line_eapd=on outputs.hp_sense=plugged outputs.line_sense=unplugged outputs.mic2_sense=unplugged outputs.spkr_muters=hp,line outputs.master=204,204 outputs.master.mute=off outputs.master.slaves=dac-2:3,dac-0:1,spkr,hp,line On Thu, Mar 1, 2018 at 6:53 PM, vincent delft <vincent.de...@gmail.com> wrote: > Hello Philip, > > After few minutes up, the vmstat result are the following: > both executed within few seconds interval. > > > vmstat -i > > interrupt total rate > irq0/clock 48183 388 > irq0/ipi 1971 > irq144/acpi0 270 > irq145/inteldrm0 7419 59 > irq96/xhci0 67761 546 > irq114/em0 900 > irq176/azalia1 10 > irq115/iwm0130 > irq101/ehci0 1070 > irq102/ahci0 240 > irq146/pckbc0 2041 > Total 124026 1000 > > > vmstat -s > >4096 bytes per page > 2002400 pages managed > 1900813 pages free >5333 pages active >9210 pages inactive > 0 pages being paged out > 49 pages wired > 237608 pages zeroed > 4 pages reserved for pagedaemon > 6 pages reserved for kernel > 0 swap pages > 0 swap pages in use > 0 total anon's in system > 0 free anon's > 193397 page faults > 191678 traps >19272320 interrupts > 52590 cpu context switches > 321 fpu context switches > 81438 software interrupts > 399151 syscalls > 0 pagein operations > 407 forks > 25 forks where vmspace is shared > 22 kernel map entries > 165624 zeroed page hits >2245 zeroed page misses > 0 number of times the pagedaemon woke up > 0 revolutions of the clock hand > 0 pages freed by pagedaemon > 0 pages scanned by pagedaemon > 0 pages reactivated by pagedaemon > 0 busy pages found by pagedaemon > 30862 total name lookups > cache hits (68% pos + 2% neg) system 0% per-directory > deletions 5%, falsehits 0%, toolong 0% > 0 select collisions > > > > > > On Thu, Mar 1, 2018 at 9:46 AM, Philip Guenther <guent...@gmail.com> > wrote: > >> On Thu, Mar 1, 2018 at 12:37 AM, vincent delft <vincent.de...@gmail.com> >> wrote: >> >>> If I do a “boot –c” and “disable acpimadt” the machine does no more do >>> lot >>> of interrupts. >>> >>> But I miss lot of hardwares (2 cpu instead of 4, no mouse, …) >>> >>> >>> >>> Otherwise, I’ve tried to remove lot of CPU performance parameters in the >>> Bios settings, but this has no effects. >>> >>> >>> >>> I’ve tried to disable HW elements like wifi, bluethoot, … But this has no >>> effect on the number of interrupts. >>> >> >> After a cold boot with acpimadt *enabled*, what's the output of "vmstat >> -i" ? >> >> >> Philip Guenther >> >> (You don't need to quote your previous message; there are list archives >> and it just makes it more annoying to reply.) >> >> >
Re: interrupt at 50% on dell E5450
Hello Philip, After few minutes up, the vmstat result are the following: both executed within few seconds interval. vmstat -i interrupt total rate irq0/clock 48183 388 irq0/ipi 1971 irq144/acpi0 270 irq145/inteldrm0 7419 59 irq96/xhci0 67761 546 irq114/em0 900 irq176/azalia1 10 irq115/iwm0130 irq101/ehci0 1070 irq102/ahci0 240 irq146/pckbc0 2041 Total 124026 1000 vmstat -s 4096 bytes per page 2002400 pages managed 1900813 pages free 5333 pages active 9210 pages inactive 0 pages being paged out 49 pages wired 237608 pages zeroed 4 pages reserved for pagedaemon 6 pages reserved for kernel 0 swap pages 0 swap pages in use 0 total anon's in system 0 free anon's 193397 page faults 191678 traps 19272320 interrupts 52590 cpu context switches 321 fpu context switches 81438 software interrupts 399151 syscalls 0 pagein operations 407 forks 25 forks where vmspace is shared 22 kernel map entries 165624 zeroed page hits 2245 zeroed page misses 0 number of times the pagedaemon woke up 0 revolutions of the clock hand 0 pages freed by pagedaemon 0 pages scanned by pagedaemon 0 pages reactivated by pagedaemon 0 busy pages found by pagedaemon 30862 total name lookups cache hits (68% pos + 2% neg) system 0% per-directory deletions 5%, falsehits 0%, toolong 0% 0 select collisions On Thu, Mar 1, 2018 at 9:46 AM, Philip Guenther <guent...@gmail.com> wrote: > On Thu, Mar 1, 2018 at 12:37 AM, vincent delft <vincent.de...@gmail.com> > wrote: > >> If I do a “boot –c” and “disable acpimadt” the machine does no more do lot >> of interrupts. >> >> But I miss lot of hardwares (2 cpu instead of 4, no mouse, …) >> >> >> >> Otherwise, I’ve tried to remove lot of CPU performance parameters in the >> Bios settings, but this has no effects. >> >> >> >> I’ve tried to disable HW elements like wifi, bluethoot, … But this has no >> effect on the number of interrupts. >> > > After a cold boot with acpimadt *enabled*, what's the output of "vmstat > -i" ? > > > Philip Guenther > > (You don't need to quote your previous message; there are list archives > and it just makes it more annoying to reply.) > >
Re: interrupt at 50% on dell E5450
Hello, If I do a “boot –c” and “disable acpimadt” the machine does no more do lot of interrupts. But I miss lot of hardwares (2 cpu instead of 4, no mouse, …) Otherwise, I’ve tried to remove lot of CPU performance parameters in the Bios settings, but this has no effects. I’ve tried to disable HW elements like wifi, bluethoot, … But this has no effect on the number of interrupts. I've tried to disable Virtualization Feature, but no effect neither. Is there any commands I can use to better pin-point to root cause of the problem ? rgds On Tue, Feb 27, 2018 at 7:24 PM, vincent delft <vincent.de...@gmail.com> wrote: > Hello, > > I've just installed current on my new dell e5450, but encounter some > troubles. > > 1 of the 4 display CPU in Top is heating 50% for interrupts. > > Concerning the installation process I did, I just followed the normal > process by booting bsd.rd and performing a standard install by getting > files from internet. > So, at the reboot he installed automatically some firmwares: iwm, uvideo > and vmm. > > I've removed those firmwares via pkg_delete, but the problem remains. > > on Bios level, I've not performed changes. > Before booting, I've checked that "legacy" was activated, since it was, > I've leave it as it is. > > > Any ideas ? > > something I should de-activate ? > > > Vincent > > ps: > except that, I have 2 small problems: > 1. the brightness button which does not work. xbacklight neither, but > xrandr --brightness work well :-). > > 2. After a lid close (suspend), when I open it, the machine try to start, > the screen appears very shortly but goes back in "sleeping". Pressing the > power button make the system coming back to normal where it was. > I see in dmesg message like: "acpivideo0: unknown event 0x00" when I close > or open the lid. > using the "moon" button does not create such problem. The suspend and > resume work perfectly. > > > > > > > > > > > TOP: > -- > > load averages: 0.03, 0.02, 0.00e5450.home.lan 18:39:24 > 28 processes: 27 idle, 1 on processor up 0:02 > CPU0 states: 0.2% user, 0.0% nice, 0.5% system, 60.5% interrupt, 38.9% > idle > CPU1 states: 1.3% user, 0.0% nice, 1.2% system, 0.0% interrupt, 97.5% > idle > CPU2 states: 1.9% user, 0.0% nice, 0.7% system, 0.0% interrupt, 97.4% > idle > CPU3 states: 0.2% user, 0.0% nice, 1.4% system, 0.0% interrupt, 98.3% > idle > Memory: Real: 20M/391M act/tot Free: 7431M Cache: 283M Swap: 0K/4220M > > PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND > 1 root 100 384K 428K idle wait 0:01 0.00% init > 8886 vi180 684K 796K sleep/2 pause 0:00 0.00% ksh > 76946 _smtpq 20 1476K 3680K idle kqread0:00 0.00% smtpd > 14499 _smtpd 20 1392K 3640K idle kqread0:00 0.00% smtpd > 36195 root 20 1528K 2244K idle kqread0:00 0.00% smtpd > 33739 _smtpd 20 1472K 3704K idle kqread0:00 0.00% smtpd > 98349 _smtpd 20 1264K 3460K idle kqread0:00 0.00% smtpd > 19311 root 20 880K 1376K idle select0:00 0.00% sshd > 30693 _smtpd 20 1348K 3552K idle kqread0:00 0.00% smtpd > 30697 _smtpd 20 1264K 3512K idle kqread0:00 0.00% smtpd > 21077 _ntp 20 700K 2364K sleep/2 poll 0:00 0.00% ntpd > 98937 root 30 312K 1252K idle ttyin 0:00 0.00% getty > 52645 root 30 312K 1256K idle ttyin 0:00 0.00% getty > 80044 root 30 316K 1252K idle ttyin 0:00 0.00% getty > 38165 _pflogd40 712K 532K sleep/2 bpf 0:00 0.00% pflogd > 48738 _ntp 2 -20 756K 2448K sleep/2 poll 0:00 0.00% ntpd > 23159 root 20 684K 616K idle kqread0:00 0.00% slaacd > 77351 _syslogd 20 932K 1616K sleep/3 kqread0:00 0.00% syslogd > > dmesg > > > OpenBSD 6.2-current (GENERIC.MP) #11: Mon Feb 26 19:16:54 MST 2018 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 8456654848 <(845)%20665-4848> (8064MB) > avail mem = 8193343488 <(819)%20334-3488> (7813MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed750 (89 entries) > bios0: vendor Dell Inc. version "A11" date 11/18/2015 > bios0: Dell Inc. Latitude E5450 > acpi0 at bios0: rev 2 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF! SSDT > SSDT SSDT SSDT PCCT SSDT SSDT SSDT SLIC MSDM DMAR > acpi0: wakeup device
interrupt at 50% on dell E5450
Hello, I've just installed current on my new dell e5450, but encounter some troubles. 1 of the 4 display CPU in Top is heating 50% for interrupts. Concerning the installation process I did, I just followed the normal process by booting bsd.rd and performing a standard install by getting files from internet. So, at the reboot he installed automatically some firmwares: iwm, uvideo and vmm. I've removed those firmwares via pkg_delete, but the problem remains. on Bios level, I've not performed changes. Before booting, I've checked that "legacy" was activated, since it was, I've leave it as it is. Any ideas ? something I should de-activate ? Vincent ps: except that, I have 2 small problems: 1. the brightness button which does not work. xbacklight neither, but xrandr --brightness work well :-). 2. After a lid close (suspend), when I open it, the machine try to start, the screen appears very shortly but goes back in "sleeping". Pressing the power button make the system coming back to normal where it was. I see in dmesg message like: "acpivideo0: unknown event 0x00" when I close or open the lid. using the "moon" button does not create such problem. The suspend and resume work perfectly. TOP: -- load averages: 0.03, 0.02, 0.00e5450.home.lan 18:39:24 28 processes: 27 idle, 1 on processor up 0:02 CPU0 states: 0.2% user, 0.0% nice, 0.5% system, 60.5% interrupt, 38.9% idle CPU1 states: 1.3% user, 0.0% nice, 1.2% system, 0.0% interrupt, 97.5% idle CPU2 states: 1.9% user, 0.0% nice, 0.7% system, 0.0% interrupt, 97.4% idle CPU3 states: 0.2% user, 0.0% nice, 1.4% system, 0.0% interrupt, 98.3% idle Memory: Real: 20M/391M act/tot Free: 7431M Cache: 283M Swap: 0K/4220M PID USERNAME PRI NICE SIZE RES STATE WAIT TIMECPU COMMAND 1 root 100 384K 428K idle wait 0:01 0.00% init 8886 vi180 684K 796K sleep/2 pause 0:00 0.00% ksh 76946 _smtpq 20 1476K 3680K idle kqread0:00 0.00% smtpd 14499 _smtpd 20 1392K 3640K idle kqread0:00 0.00% smtpd 36195 root 20 1528K 2244K idle kqread0:00 0.00% smtpd 33739 _smtpd 20 1472K 3704K idle kqread0:00 0.00% smtpd 98349 _smtpd 20 1264K 3460K idle kqread0:00 0.00% smtpd 19311 root 20 880K 1376K idle select0:00 0.00% sshd 30693 _smtpd 20 1348K 3552K idle kqread0:00 0.00% smtpd 30697 _smtpd 20 1264K 3512K idle kqread0:00 0.00% smtpd 21077 _ntp 20 700K 2364K sleep/2 poll 0:00 0.00% ntpd 98937 root 30 312K 1252K idle ttyin 0:00 0.00% getty 52645 root 30 312K 1256K idle ttyin 0:00 0.00% getty 80044 root 30 316K 1252K idle ttyin 0:00 0.00% getty 38165 _pflogd40 712K 532K sleep/2 bpf 0:00 0.00% pflogd 48738 _ntp 2 -20 756K 2448K sleep/2 poll 0:00 0.00% ntpd 23159 root 20 684K 616K idle kqread0:00 0.00% slaacd 77351 _syslogd 20 932K 1616K sleep/3 kqread0:00 0.00% syslogd dmesg OpenBSD 6.2-current (GENERIC.MP) #11: Mon Feb 26 19:16:54 MST 2018 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8456654848 <(845)%20665-4848> (8064MB) avail mem = 8193343488 <(819)%20334-3488> (7813MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xed750 (89 entries) bios0: vendor Dell Inc. version "A11" date 11/18/2015 bios0: Dell Inc. Latitude E5450 acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG HPET SSDT UEFI SSDT ASF! SSDT SSDT SSDT SSDT PCCT SSDT SSDT SSDT SLIC MSDM DMAR acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2694.16 MHz cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA, CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM, PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,SMX,EST,TM2,SSSE3, SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE, POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB, RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,BMI1,HLE, AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,RDSEED,ADX,SMAP,PT,SENSOR,ARAT,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache acpitimer0: recalibrated TSC frequency 2294695314 <(229)%20469-5314> Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 99MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i5-5300U CPU @ 2.30GHz, 2693.77 MHz cpu1:
Re: FAQ's duplicating file systems, both methods fail to reproduce correctly
On Sun, Dec 10, 2017 at 10:39 PM, Philip Guentherwrote: > 'pax' and 'tar' are actually the same binary so they have the same > limitation from the file formats that are supported, as well as any purely > internal limitations. "pax -rw" actually has file format limitations by > design, so it doesn't automagically free you from those limitations. > > By Looking a tar man page, I do not find comments regarding "length" constraints :(. On pax, it stated that with the default archive format "ustar", filenames must be 100 char max and path names must be 256 char max. But It's not clear which archive format the command Tar is using. Is it using the "old tar" format or the new "ustar" format as described in the pax man pages ? Amazing for me to see that both are the same binary t420:~$ ls -ali /bin/tar 32778 -r-xr-xr-x 3 root bin 433488 Oct 4 05:13 /bin/tar t420:~$ ls -ali /bin/pax 32778 -r-xr-xr-x 3 root bin 433488 Oct 4 05:13 /bin/pax
Re: FAQ's duplicating file systems, both methods fail to reproduce correctly
Hello, Did you tried pax ? some thing like: pax -rw -pe I don't know if this the best tool, but I'm using it to duplicate a 1TB drive (having lot of hard links) onto an other one. I've done it couple of time, and I've do not see issues. rgds On Sun, Dec 10, 2017 at 7:03 PM,wrote: > Forgive problems with this email. > I saw how my emails showed up on marc.info > Scary. This is just temporary. > > OK. I've tried to use both methods and just don't > get true duplication. > > tar > It can't work with file and directory names > that are OK in filesystem, but too long for itself. > Quite a while back I lost a lot of unimportant files > and directories that had absolute paths too long. > Why is this happening with tar? Can this be fixed? > If not, I'd like to add a note about that to the FAQ. > > dump > I had to move /usr/local to a bigger partition. growfs, > etc. I kept the /usr/local untouched and then dumped it > to the new partition, expecting a true duplication. > Nope. > It changed all of the program symlinks permissions. > Why is dump doing this? Can this be fixed? > Otherwise, a note about this should be added to the FAQ > also. > > Question: > Can dd be used to do what I did with dump or tar? > Smaller partition copied to a bigger partition. > > I'm willing to try and help out, but I'm going through > both laptop and server hell at the moment. > > Thanks, > Chris Bennett > >
Re: protonmail.com broken on OpenBSD 6.2-Stable with Firefox
Hello Rupert, In my case (openbsd current), this value of javascript.options.asmjs was already "true". So, I've tried by setting it "false". And with the value "false" it works :-). At least protonmail.com. and few websites I've tried. Thanks On Thu, Nov 2, 2017 at 12:23 PM, Rupert Gallagherwrote: > Try this... > > javascript.options.asmjs: true > > Sent from ProtonMail Mobile > > On Wed, Nov 1, 2017 at 17:32, tec...@protonmail.com > wrote: > > >> Hello, > > Can't get to the login page on FF, just see a never ending > loop of 'Loading Protonmail...' > > Damn frustrating. I can confirm this > has happened with 3 different installs. > > Having to use chromium, > definitely not a good solution for a Google-hater. > > Thanks
Re: protonmail.com broken on OpenBSD 6.2-Stable with Firefox
Hello, Can you try with the safe mode: firefox --safe-mode. This should work fine. rgds On Wed, Nov 1, 2017 at 5:32 PM, tec...@protonmail.comwrote: > > Hello, > > > > Can't get to the login page on FF, just see a never ending loop of > 'Loading Protonmail...' > > > > Damn frustrating. I can confirm this has happened with 3 different > installs. > > > > Having to use chromium, definitely not a good solution for a > Google-hater. > > > > Thanks
Re: Fail2ban alternative for OpenBSD
Hello all, My I add my 2 cents ... I had the same problematic some months ago, so I develop log2table ( http://vincentdelft.be/post/post_20170517) Which has the same idea of fail2ban. It's a python script with no specific requirements, except some entries in doas.conf. The added value is that you can ban a bad IP based on the different actions he is doing on your machine (ssh, http, ...). In short, every attack gives a "weight" (you decide in the config file) and when the threshold is reached the IP is blocked (1 hour in my config). rgds On Mon, Oct 30, 2017 at 10:31 AM, Kamil Cholewińskiwrote: > On Mon, 30 Oct 2017, Gregory Edigarov wrote: > > On 29.10.17 03:20, x9p wrote: > >> > >> Coming from the Linux world, I wonder if there is a better alternative > >> to fail2ban, already being used in OpenBSD servers by the majority. > >> > > I suggest you NEVER use such "solutions". It's security by obscurity > > model, and therefore a bad very very bad thing. > > You'd be much safer completely turning off password authentication, > > using keys instead. > > Throttling brute-force attack attempts is usually Good. Passwords are > one thing to try forcing, but there may be other undiscovered (or > unpatched) vulns, like the Debian key fiasco or such. > > Of course, if it actually made sense, OpenBSD would probably ship it as > a default ;) > > <3,K. > >