nvd0 lockup while compiling ports
Hi, I've got a new Workstation last week with the Main HD as M2 Card. FreeBSD recognizes the card as nvd0 nvd0: NVMe namespace nvd0: 488386MB (1000215216 512 byte sectors) When compiling some ports (in this example VirtualBox-ose) I experiencing lockups on the Harddisk when many files are deleted. here is the entries gstat reports dT: 1.064s w: 1.000s L(q) ops/sr/s kBps ms/rw/s kBps ms/w %busy Name 25281769 0 00.0 0 00.0 100.0| nvd0 25279769 0 00.0 0 00.0 100.0| nvd0p4 25279769 0 00.0 0 00.0 100.0| ufs/USR here the right part of gstat -d -o dT: 1.003s w: 1.000s d/s kBps ms/do/s ms/o %busy Name 770 24641 31965 00.0 100.1| nvd0 770 24641 31965 00.0 100.1| nvd0p4 770 24641 31965 00.0 100.1| ufs/USR the numbers under L(q) go up to about 16 and as long as theses operations are not finisched, no outer file operation is possible on this filesystem. The number of ops/s and d/s is constant aproximatly 770. Is there a way to speed up delete operations or limit the queue length? Regards Estartu ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with piped tar
Am 23.08.2016 um 13:31 schrieb Gary Palmer: > On Tue, Aug 23, 2016 at 09:35:12AM +0200, Gerhard Schmidt wrote: >> Am 23.08.2016 um 09:18 schrieb Daniel Braniss: >>> >>>> On 23 Aug 2016, at 10:06, Gerhard Schmidt <esta...@ze.tum.de> wrote: >>>> >>>> Hi, >>>> >>>> i'm quite often use tar to copy files using >>>> >>>> tar cf - /some/dir | (cd /dest/dir; tar xvvf - ) >>> the ???new??? way: >>> tar cf - /some/dir | tar xvvd - -C /dest/dir >>> which of course does not explain way your version hangs, but this one is >>> cleaner, and btw, don???t >>> include /. >> >> that's very strange. It's working, but doesn't solve another related >> problem. When i pipe the tar thru nc a have the same problem as my >> version. And it's no difference if there is a tar c an the receiving end >> of nc or just a '> file.tar' > > Is the sending side using nc -N ? If not, the sending socket is not being > shut down. Is that something new? Because it worked on freebsd9 without the -N option. The problem seams to be that tar c doesn't terminate after the last File is send. I think it send the EOF (because nc -N terminates and therefor terminates the pipe) but the tar process doesn't terminate. Estartu -- - Gerhard Schmidt | E-Mail: schm...@ze.tum.de TU-München| Jabber: esta...@ze.tum.de WWW & Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems while reading from /dev/cd0
Am 23.08.2016 um 13:12 schrieb Dimitry Andric: > On 23 Aug 2016, at 08:50, Gerhard Schmidt <esta...@ze.tum.de> wrote: >> >> I'm having some very curios Problems while reading from an BD-R recorded >> as a tar directly on the disk without a filesystem. >> >> When i try to read the Disk via 'tar tvvf /dev/cd0' >> >> i get the following output >> >> -rw-r--r-- 0 root wheel 5793264611 1 Jan 2015 file1.db >> tar: Error reading '/dev/cd0' >> Archive Format: POSIX ustar format, Compression: none >> tar: Error exit delayed from previous errors. >> >> reading the whole file via 'dd if=/dev/cd0 of=backup.tar bs=2048' and >> than 'tar tvvf backup.tar' the file is read without a hitch. So the data >> on the disk is OK but can't be read directly by tar. >> >> if i try the dd without the bs=2048 i get >> >> dd: /dev/cd0: Invalid argument >> 0+0 records in >> 0+0 records out >> 0 bytes transferred in 0.000115 secs (0 bytes/sec) >> >> So there is a problem reading anything other than 2048 byte blocks from >> a Disk. > > Have you tried tar's -b option, to set the block size 2048? Maybe that > will help. It does partially. extracting the files work but testing the archive with tar t fails. Estartu -- -- Gerhard Schmidt| E-Mail: schm...@ze.tum.de Technische Universität München | Jabber: esta...@ze.tum.de WWW & Online Services | Tel: +49 89 289-25270 | PGP-PublicKey Fax: +49 89 289-25257 | on request ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Problems with piped tar
Am 23.08.2016 um 09:18 schrieb Daniel Braniss: > >> On 23 Aug 2016, at 10:06, Gerhard Schmidt <esta...@ze.tum.de> wrote: >> >> Hi, >> >> i'm quite often use tar to copy files using >> >> tar cf - /some/dir | (cd /dest/dir; tar xvvf - ) > the ‘new’ way: > tar cf - /some/dir | tar xvvd - -C /dest/dir > which of course does not explain way your version hangs, but this one is > cleaner, and btw, don’t > include /. that's very strange. It's working, but doesn't solve another related problem. When i pipe the tar thru nc a have the same problem as my version. And it's no difference if there is a tar c an the receiving end of nc or just a '> file.tar' Regards Estartu -- - Gerhard Schmidt | E-Mail: schm...@ze.tum.de TU-München| Jabber: esta...@ze.tum.de WWW & Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Problems with piped tar
Hi, i'm quite often use tar to copy files using tar cf - /some/dir | (cd /dest/dir; tar xvvf - ) the files are copied without a problem but the reading tar never terminates and so the whole command never terminates. This is new since FreeBSD 10. Regards Estartu -- -- Gerhard Schmidt| E-Mail: schm...@ze.tum.de Technische Universität München | Jabber: esta...@ze.tum.de WWW & Online Services | Tel: +49 89 289-25270 | PGP-PublicKey Fax: +49 89 289-25257 | on request ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Problems while reading from /dev/cd0
Hi, I'm having some very curios Problems while reading from an BD-R recorded as a tar directly on the disk without a filesystem. When i try to read the Disk via 'tar tvvf /dev/cd0' i get the following output -rw-r--r-- 0 root wheel 5793264611 1 Jan 2015 file1.db tar: Error reading '/dev/cd0' Archive Format: POSIX ustar format, Compression: none tar: Error exit delayed from previous errors. reading the whole file via 'dd if=/dev/cd0 of=backup.tar bs=2048' and than 'tar tvvf backup.tar' the file is read without a hitch. So the data on the disk is OK but can't be read directly by tar. if i try the dd without the bs=2048 i get dd: /dev/cd0: Invalid argument 0+0 records in 0+0 records out 0 bytes transferred in 0.000115 secs (0 bytes/sec) So there is a problem reading anything other than 2048 byte blocks from a Disk. Reading directly with tar worked in the past. I really don't know how long it's there but i guess it's since i updated from FreeBSD 9 to FreeBSD 10. I running right now FreeBSD 10.3-RELEASE-p4 Here is the output from the kernel boot msg of the BRD Drive. cd0 at ahcich7 bus 0 scbus7 target 0 lun 0 cd0: Removable CD-ROM SCSI device cd0: Serial Number SIK9JFANE175 cd0: 150.000MB/s transfers (SATA 1.x, UDMA6, ATAPI 12bytes, PIO 8192bytes) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed Regards Estartu -- -- Gerhard Schmidt| E-Mail: schm...@ze.tum.de Technische Universität München | Jabber: esta...@ze.tum.de WWW & Online Services | Tel: +49 89 289-25270 | PGP-PublicKey Fax: +49 89 289-25257 | on request ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Error upgrading from 10.1-RELEASE to 10.2-RELEASE
Am 26.08.2015 um 07:03 schrieb Andreas Ott: Hi, On Mon, Aug 24, 2015 at 05:07:55PM +0200, Christian Kratzer wrote: The only way I have been able to upgrade systems is by repeatedly running freebsd-update. Same here, one system needed three attempts of running freebsd-upgrade and the other one four, on both I pointed to an update server with -s . Hi, change the servername in /etc/freebsd-update.conf from update.FreeBSD.org to update.freebsd.org and the mirror detection works again. Updates from one of the mirrors seams to succed. Regards Estartu -- --- Gerhard Schmidt| http://www.augusta.de/~estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | JabberID: esta...@augusta.de | on request Germany|| ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: freebsd-update to 10.2-RELEASE broken ?
Am 16.08.2015 um 20:07 schrieb Kurt Jaeger:
Hi!
[bob wrote]
[ck wrote]
I have been trying to update several of my FreeBSD 10.1 amd64
VM to 10.2-RELEASE with freebsd-update and have been failing with
an incorrect hash error.
FWIW I had the same issue yesterday on a couple of systems.
Repeating freebsd-update worked after two or three goes.
I've seen the same problem on several hosts and discussed it by mail
with gjb@.
We assumed that I have a DNS problem because of this line:
Looking up update.FreeBSD.org mirrors... none found.
This happens with this query inside the freebsd-update script, at
line 950:
host -t srv _http._tcp.update.FreeBSD.org
I think there is also a problem with freebsd-update.
[root@miraculix ~]# freebsd-update upgrade -r 10.2-RELEASE
Looking up update.FreeBSD.org mirrors... none found.
Fetching metadata signature for 10.1-RELEASE from update.FreeBSD.org... done.
Fetching metadata index... done.
Inspecting system... done.
^C
[root@miraculix ~]# host -t srv _http._tcp.update.FreeBSD.org
_http._tcp.update.freebsd.org has SRV record 1 40 80 update6.freebsd.org.
_http._tcp.update.freebsd.org has SRV record 1 35 80 update4.freebsd.org.
_http._tcp.update.freebsd.org has SRV record 1 30 80 update2.freebsd.org.
_http._tcp.update.freebsd.org has SRV record 1 5 80 update3.freebsd.org.
_http._tcp.update.freebsd.org has SRV record 1 50 80 update5.freebsd.org.
freebsd-update reporting no mirrors found but the host command returns mirrors.
The problem seams to be the
sed -nE s/${MLIST} (has SRV record|server selection) //p
MLIST is _http._tcp.update.FreeBSD.org but sed doesn't match any of the lines
from the host command.
Replaceing the servername with the lowercase variant matches every line.
There is not DNS Problem but a case sensitivity problem in freebsd-update
Regards
Estartu
--
---
Gerhard Schmidt| http://www.augusta.de/~estartu |
Fischbachweg 3 || PGP Public Key
86856 Hiltenfingen | JabberID: esta...@augusta.de | on request
Germany||
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Installing FreeBSD on MacPro
Hi, I'm trying to install FreeBSD 10.2 on a MacPro. Installing and Booting works. But a few seconds after login and accessing the Harddisk, I'm getting the following errors. ahcich0: Timeout on slot 13 port 0 ahcich0: is 0008 cs ss rs tfd 40 serr cmd cd17 (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 28 15 40 40 2f 00 00 01 00 00 (ada0:ahcich0:0:0:0): CAM status: Command timeout (ada0:ahcich0:0:0:0): Retrying command ahcich0: Timeout on slot 15 port 0 ahcich0: is 0008 cs ss rs tfd 40 serr cmd cf17 (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 a0 5f bd 40 13 00 00 00 00 00 (ada0:ahcich0:0:0:0): CAM status: Command timeout (ada0:ahcich0:0:0:0): Retrying command ahcich0: Timeout on slot 2 port 0 ahcich0: is 0008 cs ss rs tfd 40 serr cmd c217 (ada0:ahcich0:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 08 c0 23 bd 40 13 00 00 00 00 00 (ada0:ahcich0:0:0:0): CAM status: Command timeout (ada0:ahcich0:0:0:0): Retrying command Any Ideas what causes this and what can be done to fix it. the dmesg of the MacPro is the following Copyright (c) 1992-2015 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.2-RELEASE #0 r28: Wed Aug 12 15:26:37 UTC 2015 r...@releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 VT: running with driver efifb. CPU: Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz (2700.06-MHz K8-class CPU) Origin=GenuineIntel Id=0x306e4 Family=0x6 Model=0x3e Stepping=4 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x7fbee3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,DCA,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND AMD Features=0x2c100800SYSCALL,NX,Page1GB,RDTSCP,LM AMD Features2=0x1LAHF Structured Extended Features=0x281FSGSBASE,SMEP,ERMS XSAVE Features=0x1XSAVEOPT VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr TSC: P-state invariant, performance statistics real memory = 68719476736 (65536 MB) avail memory = 66655334400 (63567 MB) Event timer LAPIC quality 600 ACPI APIC Table: APPLE Apple00 FreeBSD/SMP: Multiprocessor System Detected: 24 CPUs FreeBSD/SMP: 1 package(s) x 12 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 cpu8 (AP): APIC ID: 8 cpu9 (AP): APIC ID: 9 cpu10 (AP): APIC ID: 10 cpu11 (AP): APIC ID: 11 cpu12 (AP): APIC ID: 16 cpu13 (AP): APIC ID: 17 cpu14 (AP): APIC ID: 18 cpu15 (AP): APIC ID: 19 cpu16 (AP): APIC ID: 20 cpu17 (AP): APIC ID: 21 cpu18 (AP): APIC ID: 22 cpu19 (AP): APIC ID: 23 cpu20 (AP): APIC ID: 24 cpu21 (AP): APIC ID: 25 cpu22 (AP): APIC ID: 26 cpu23 (AP): APIC ID: 27 ioapic0 Version 2.0 irqs 0-23 on motherboard ioapic1 Version 2.0 irqs 24-47 on motherboard lapic0: Forcing LINT1 to edge trigger random: Software, Yarrow initialized module_register_init: MOD_LOAD (vesa, 0x80db8eb0, 0) error 19 kbd0 at kbdmux0 acpi0: APPLE Apple00 on motherboard acpi0: Power Button (fixed) unknown: I/O range not supported Timecounter HPET frequency 14318180 Hz quality 950 Event timer HPET frequency 14318180 Hz quality 350 Event timer HPET1 frequency 14318180 Hz quality 340 Event timer HPET2 frequency 14318180 Hz quality 340 Event timer HPET3 frequency 14318180 Hz quality 340 Event timer HPET4 frequency 14318180 Hz quality 340 Event timer HPET5 frequency 14318180 Hz quality 340 Event timer HPET6 frequency 14318180 Hz quality 340 Event timer HPET7 frequency 14318180 Hz quality 340 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0 cpu3: ACPI CPU on acpi0 cpu4: ACPI CPU on acpi0 cpu5: ACPI CPU on acpi0 cpu6: ACPI CPU on acpi0 cpu7: ACPI CPU on acpi0 cpu8: ACPI CPU on acpi0 cpu9: ACPI CPU on acpi0 cpu10: ACPI CPU on acpi0 cpu11: ACPI CPU on acpi0 cpu12: ACPI CPU on acpi0 cpu13: ACPI CPU on acpi0 cpu14: ACPI CPU on acpi0 cpu15: ACPI CPU on acpi0 cpu16: ACPI CPU on acpi0 cpu17: ACPI CPU on acpi0 cpu18: ACPI CPU on acpi0 cpu19: ACPI CPU on acpi0 cpu20: ACPI CPU on acpi0 cpu21: ACPI CPU on acpi0 cpu22: ACPI CPU on acpi0 cpu23: ACPI CPU on acpi0 atrtc0: AT realtime clock port 0x70-0x77 on acpi0 Event timer RTC frequency 32768 Hz quality 0 attimer0: AT timer port 0x40-0x43,0x50-0x53 on acpi0 Timecounter i8254 frequency 1193182 Hz quality 0 Event timer i8254 frequency 1193182 Hz quality 100 Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0
Re: Problems with openssl 1.0.2 update
On 23.03.2015 13:40, Guido Falsi wrote: On 03/23/15 11:33, Gerhard Schmidt wrote: Hi, we experiencing a problem after upgrading the openssl port to openssl 1.0.2. /usr/bin/vi started to crash after some seconds with segfault. /rescue/vi works just fine. Deleting the openssl 1.0.2 package everything works just fine again. Installing the old openssl 1.0.1_18 package it still works just fine. it seams that besides vi the bash also has this problem. Anybody experiencing the same or is this something specific to my system. I'm running FreeBSD 10.1 updated tonight. I am seeing runtime problems with asterisk13 (which I maintain), caused by the OpenSSL update fallout. In this case, after some analysis, I concluded the problem is the libsrtp port requiring OpenSSL from ports(for a reason), causing asterisk to link to that too, which would be correct. Asterisk also uses the security/trousers port, which links to system OpenSSL. This ensues a conflict which now results in asterisk segfaulting and stopping to work. I'm investigating what can be done about this. As a local solution I can force the trousers port to link against OpenSSL from ports, but this will not fix the general problem. As a port maintaner I ony see modifying the trousers port to depend on ports OpenSSL as a solution, is this acceptable? Most Ports link against the port openssl if its installed and agains the system openssl if not. That should be the prefered way to handle problem. I don't know if an incompatibility between system an port openssl is a problem. I've removed the portbuild openssl from this server completely. As far as i can see the problem is with openldap-client build agains the ports openssl and used by nss_ldap or pam_ldap modul. I will do some testing when my test host is ready. Testing on an Production server is not that good :-) Regards Estartu -- - Gerhard Schmidt | E-Mail: schm...@ze.tum.de TU-München| Jabber: esta...@ze.tum.de WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage signature.asc Description: OpenPGP digital signature
Problems with openssl 1.0.2 update
Hi, we experiencing a problem after upgrading the openssl port to openssl 1.0.2. /usr/bin/vi started to crash after some seconds with segfault. /rescue/vi works just fine. Deleting the openssl 1.0.2 package everything works just fine again. Installing the old openssl 1.0.1_18 package it still works just fine. it seams that besides vi the bash also has this problem. Anybody experiencing the same or is this something specific to my system. I'm running FreeBSD 10.1 updated tonight. Regards Estartu -- -- Gerhard Schmidt| E-Mail: schm...@ze.tum.de Technische Universität München | Jabber: esta...@ze.tum.de WWW Online Services | Tel: +49 89 289-25270 | PGP-PublicKey Fax: +49 89 289-25257 | on request ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problems with openssl 1.0.2 update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 23.03.2015 15:14, Dewayne Geraghty wrote: On 24/03/2015 12:16 AM, Gerhard Schmidt wrote: On 23.03.2015 13:40, Guido Falsi wrote: On 03/23/15 11:33, Gerhard Schmidt wrote: Hi, we experiencing a problem after upgrading the openssl port to openssl 1.0.2. /usr/bin/vi started to crash after some seconds with segfault. /rescue/vi works just fine. Deleting the openssl 1.0.2 package everything works just fine again. Installing the old openssl 1.0.1_18 package it still works just fine. it seams that besides vi the bash also has this problem. Anybody experiencing the same or is this something specific to my system. I'm running FreeBSD 10.1 updated tonight. I am seeing runtime problems with asterisk13 (which I maintain), caused by the OpenSSL update fallout. In this case, after some analysis, I concluded the problem is the libsrtp port requiring OpenSSL from ports(for a reason), causing asterisk to link to that too, which would be correct. Asterisk also uses the security/trousers port, which links to system OpenSSL. This ensues a conflict which now results in asterisk segfaulting and stopping to work. I'm investigating what can be done about this. As a local solution I can force the trousers port to link against OpenSSL from ports, but this will not fix the general problem. As a port maintaner I ony see modifying the trousers port to depend on ports OpenSSL as a solution, is this acceptable? Most Ports link against the port openssl if its installed and agains the system openssl if not. That should be the prefered way to handle problem. I don't know if an incompatibility between system an port openssl is a problem. I've removed the portbuild openssl from this server completely. As far as i can see the problem is with openldap-client build agains the ports openssl and used by nss_ldap or pam_ldap modul. I will do some testing when my test host is ready. Testing on an Production server is not that good :-) Regards Estartu I only use openssl from ports and have just completed a rebuild of 662 packages for server requirements and include: trousers, ldap client and server, and 71 other ports built without any issues on amd64 10.1Stable using clang. Not so successful on i386 but I don't believe its related to openssl. I never had an issue building anything. Using it is the problem. Setup authentication via ldap (nss_ldap) and you are in hell. Bash crashes when you try to login. vi crashes when you try to change a file. Anything that uses nsswitch has some problems. Regards Estartu -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBCAAGBQJVECVNAAoJEHTSQ8xFcA2jj6MP/ifZj6q3sK96ak6KQQezM466 kRC/YuCJymzSv30HbAu2P5i2Qmkaqz/72BCVZ+YhS1n4FBw9TxHrnCI77jO94y9P 55pfvSvYzKk6sLkWEOsbqWjPLQcrTUpfHjWHC3d0uvlzVNnyiYoHGBscWMpIvpoG Jz+yV8NsJEU5Zm4YSRzOd9VM2xaLi+dBSdSmOvWTp77Oa7Rd4vYrDypcPmA2RXa7 cfTU4OBj3XdYgKF0D4E3I0xcqhvlBAgB806oVeWS7xsI3T7X3ZABBWxPf6ErPDOr a3hSjl3ZyRMku+4wSvqclWQ1GCrUh33oP5UELD81nPnci7RCxIGoUo3OiZTXvzy+ Oh12eTmEpZrpYo0QALV8Z2oxhlzWm91/iIYnfx9wr6Hk9EHYyNWlckwndfFGVcC0 bJ6KmnX3CbcxKN6RPYG38bNFJ5X9v2gqsqJFKy98KHhBlJ3O49OBzHLzFsaN7r24 TbUzwPrK3qIntMgQF5Y8uD7a1mkjpcG0H/3iwB4QZnWS9WMiynIQqTow6EeIEBgj 0TMHFWkbPetn9h9kxbF+XWf10ARVr0kH9OrTZ+2iO2B+uQb65gC5qRno/WWHBmCp MSuez+SPv3JIu7ArX9nzpEtG1wQd+r3uiGjX2YB2/kw+a+cX3/B1kWk1R1R1F5Qv /ImcsZjxeR3aNKcDsz9F =TQFs -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Problems with openssl 1.0.2 update
On 23.03.2015 14:17, Mike Tancsa wrote: On 3/23/2015 6:33 AM, Gerhard Schmidt wrote: Hi, we experiencing a problem after upgrading the openssl port to openssl 1.0.2. /usr/bin/vi started to crash after some seconds with segfault. Is you vi linked to openssl ? /usr/bin/vi: libutil.so.9 = /lib/libutil.so.9 (0x800883000) libncursesw.so.8 = /lib/libncursesw.so.8 (0x800a95000) libc.so.7 = /lib/libc.so.7 (0x800cea000) no but... I was finally able to repoduce this problem on my testserver. The problem is related to nss_ldap or pam_ldap used in the user authentication. The openldap-client, nss_ldap and pam_ldap are linked against the ports openssl lib. vi crashed when I tried to change a file. First change and vi crashes. if i remove ldap from /etc/nsswitch.conf and vi is running just fine. there is definitely a issue with openssl 1.0.2 somewhere Regards Estartu ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
passwd with pam_ldap and nss_ldap
Hi I have some FreeBSD servers running using pam_ldap and nss_ldap for central user management. Running fine so far. Changing the password is still a Problem. I have found a PR dated back to 2004 diskussing this problem. Is there someone working on this or doesn't anybody beside me needed this feature. See http://www.freebsd.org/cgi/query-pr.cgi?pr=59638 Bye Estartu -- - Gerhard Schmidt | E-Mail: [EMAIL PROTECTED] TU-München| WWW Online Services | Tel: 089/289-25270| Fax: 089/289-25257| PGP-Publickey auf Anfrage signature.asc Description: OpenPGP digital signature
Re: Loosing spam fight
On Thu, Jan 25, 2007 at 12:11:43PM +0100, Georg Bege wrote: Woah you just made my day Saying dspam or greylisting is useless ;) I hope you mean that by ironic - no you cannot block 100% spam but 99.99% effectivly which I already do even productive. But not with sendmail (who is using sendmail these days?) I do, and I have a hitquote arounf 99% as well. I'm using spamassassin and greylisting. Works pretty good. Filter/Tagging spam isn't a MTA problem, it's a configuration problem. You can do anything on any MTA. bye Estartu -- Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| pgpZRfkvRxtzj.pgp Description: PGP signature
Re: FreeBSD/i386 6-stable + 4 GB RAM
On Tue, Mar 14, 2006 at 10:46:59AM -0600, Eric Anderson wrote: Oliver Fromme wrote: Hi, I'll be getting a few new machines for a customer soon. They will be SMP (dual processor Pentium-IV) with 4 GB RAM, and I plan to install FreeBSD/i386 6-stable on them. What's the current status of running with that amount of memory? I'm not completely up to date in that regard, and searching the archive didn't get any definitive answers. I remember that there were several issues in the past, but I have no idea if they still exist. They required fiddling with VM_KMEM_SIZE_MAX, or KVA_PAGES or similar things. Will FreeBSD/i386 6-stable run on a 4 GB machine out of the box? Do I have to apply special tuning (kernel config or sysctl or whatever)? Using PAE shouldn't be necessary, I assume. It would also be interesting to know if 4-stable (which is currently running on the predecessor machines) would run without problems on those new 4 GB ones, too. Thanks in advance for any information! The base install, running GENERIC will only use 3GB. I believe you would either need to use the PAE kernel option, or use the 64bit version of FreeBSD on a corresponding 64bit hardware. I Have a i386 server running with 4Gig of ram without PAE. It's running with 5-STABLE. Has this changed in 6.0. Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD/i386 6-stable + 4 GB RAM
On Wed, Mar 15, 2006 at 04:10:30PM +0100, Andy Hilker wrote: Hi, You (Gerhard Schmidt) wrote: The base install, running GENERIC will only use 3GB. I believe you would either need to use the PAE kernel option, or use the 64bit version of FreeBSD on a corresponding 64bit hardware. I Have a i386 server running with 4Gig of ram without PAE. It's running with 5-STABLE. Has this changed in 6.0. No. It depends on your hardware how much memory is really available. But there is no limit at 3GB in general. Do you use special options (KVA space etc.) in kernel-config or make.conf to have a stable system? I have the following options in the kernel # Fix for the Memory problems options VM_KMEM_SIZE_SCALE=4 options VM_KMEM_SIZE_MAX=(1024*1024*1024) options KVA_PAGES=512 It runs stable for 4 Years now. Some problem when hyperthreading is enabled, but without hyperthreading it's stable sofar. Bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | EMail: [EMAIL PROTECTED] | on request Germany|| ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems with make release
Hi, i've tried to make an snapshotrelease from releng_5. Everything works well until the readmes from the ports collections are generated. Than the build stops withe message [...] === x11-wm === Creating README.html === Creating README.html for all ports perl: not found *** Error code 127 Stop in /usr/ports. + umount /dev *** Error code 1 Stop in /usr/src/release. perl v5.8.6 is installed on the the build system. any suggestions. bye Estartu Gerhard Schmidt| Nick : estartu IRC : Estartu | Fischbachweg 3 || PGP Public Key 86856 Hiltenfingen | Privat: [EMAIL PROTECTED] |on request Germany|| pgpL8Q87FAcOw.pgp Description: PGP signature
