From owner-freebsd-hackers@freebsd.org Sun Nov 15 01:02:56 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 096D1A2EA1D for ; Sun, 15 Nov 2015 01:02:56 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) Received: from barracuda.ixsystems.com (mail.ixsystems.com [69.198.165.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id D86CF1F43 for ; Sun, 15 Nov 2015 01:02:55 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) X-ASG-Debug-ID: 1447549370-08ca040e850d6d0002-P5m3U7 Received: from [10.0.1.8] (ip72-209-175-134.ks.ks.cox.net [72.209.175.134]) by barracuda.ixsystems.com with ESMTP id 5JPY819pGCKNlRMg (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 14 Nov 2015 17:02:52 -0800 (PST) X-Barracuda-Envelope-From: jmaloney@pcbsd.org X-Barracuda-AUTH-User: jmaloney@pcbsd.org X-Barracuda-Apparent-Source-IP: 72.209.175.134 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: FreeBSD smbfs horribly slow From: Joe Maloney X-ASG-Orig-Subj: Re: FreeBSD smbfs horribly slow In-Reply-To: <1312151904.87133792.1447539054621.JavaMail.zimbra@uoguelph.ca> Date: Sat, 14 Nov 2015 19:02:50 -0600 Cc: Mario Lobo , freebsd-hackers@freebsd.org, Mark Saad , Allan Jude Message-Id: <310B6D45-63E1-4012-BA35-8CB40CE9EBCF@pcbsd.org> References: <20151113162548.61529137@Papi> <56463ACE.5020605@freebsd.org> <20151114115022.781c0bc1@Papi> <1312151904.87133792.1447539054621.JavaMail.zimbra@uoguelph.ca> To: Rick Macklem X-Mailer: Apple Mail (2.3096.5) X-Barracuda-Connect: ip72-209-175-134.ks.ks.cox.net[72.209.175.134] X-Barracuda-Start-Time: 1447549372 X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA X-Barracuda-URL: https://10.2.0.41:443/cgi-mod/mark.cgi X-Barracuda-BRTS-Status: 1 X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests=HTML_MESSAGE X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.24400 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE BODY: HTML included in message Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 01:02:56 -0000 I=E2=80=99ve noticed that with the freebsd version of mount_smbfs I am = not able to mount an airport disk. With FreeBSD I can use gvfs = available in ports to get around that issue. https://github.com/freebsd/freebsd/tree/master/contrib/smbfs = However with the Mac OS X version of mount_smbfs I can mount an airport = disk. I realize this structure, and ASPL clobbering is pretty gross to = look at. Apologies in advance. I am curious if there is anything = useful to see here. http://opensource.apple.com/source/smb/smb-759.40.1/ = =46rom what I can tell it looks like the mount_smbfs tool originated in = FreeBSD, and was ported to other BSD=E2=80=99s? Or is FreeBSD using = this which has been abandoned by Linux? =20 https://www.samba.org/samba/smbfs/ Joe Maloney > On Nov 14, 2015, at 4:10 PM, Rick Macklem = wrote: >=20 > Mario Lobo wrote: >> On Fri, 13 Nov 2015 19:04:05 -0500 >> Mark Saad wrote: >>=20 >>> Mario >>> Can you share more about your setup . >>> What filesystem is the samba share exported from ? >>=20 >> The shares tested were both from a FBSD (10.2-STABLE) samba4 and = Linux >> (Centos) samba 3.6. >>=20 >>> What mount options >>> on the filesystem level do you use ? >>>=20 >>=20 >> smbfs rw,noatime,-N,-Iserverip 0 0 >>=20 >>> What version of samba , was it from ports or a package ? >>>=20 >>=20 >> See above. >>=20 >>> On the samba level can you tell us about your config ? Have you = tried >>> any of the tuning from https://calomel.org/samba_optimize.html >>>=20 >>=20 >> Like I said, the problem is not with the server. >>=20 >>> Did you change any sysctls ? What did you set ? >>>=20 >>> Lastly what's the hardware like ; CPU, nic type , ram , etc >>>=20 >>=20 >> I tried the same FBSD client on different hardware. Made no = difference. >>=20 > Did that different hardware have a different type of net interface = that > uses a different net device driver? >=20 > I have no idea if smbfs can do the same thing, but both NFS and iSCSI > can generate TCP TSO output segments of near 64K in data length and > that can cause problems for some net device drivers. > --> If the net interface has TSO enabled, try disabling it. >=20 > I never use smbfs, so I can't help more, rick >=20 >>=20 >>=20 >>> --- >>> Mark Saad | nonesuch@longcount.org >>>=20 >>>> On Nov 13, 2015, at 6:13 PM, Mario Lobo wrote: >>>>=20 >>>> 2015-11-13 16:32 GMT-03:00 Allan Jude : >>>>=20 >>>>>> On 2015-11-13 14:25, Mario Lobo wrote: >>>>>> Hi; >>>>>>=20 >>>>>> It seems no one in @questions had any info/pointers/interest on >>>>>> this so I'm trying @hackers for some light. >>>>>>=20 >>>>>> Thanks, >>>>>>=20 >>>>>>=20 >>>>>> Begin forwarded message: >>>>>>=20 >>>>>> Date: Wed, 11 Nov 2015 17:53:11 -0300 >>>>>> From: Mario Lobo >>>>>> To: freebsd-questions >>>>>> Subject: FreeBSD smbfs horribly slow >>>>>>=20 >>>>>> Googling on this subject, I found: >>>>> = http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/098717= .html >>>>>> = https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.html >>>>> = https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/261804.= html >>>>>>=20 >>>>>> I am on 10.2-STABLE and using FreeBSD as a client to any amb = share >>>>>> continues to be very slow. >>>>>>=20 >>>>>> The share is mounted through mount_smbfs. I tried smbnetfs (fuse) >>>>>> and it is just a tiny bit better but doesn't compare to other >>>>>> clients (linux or win) when writing/reading files >>>>>>=20 >>>>>> It gets even worse if an application is doing operations with >>>>>> variable size records inside a data file on the share. >>>>>>=20 >>>>>> Does anyone have any advice to improve this? >>>>>>=20 >>>>>> Thanks, >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> _______________________________________________ >>>>>> freebsd-hackers@freebsd.org mailing list >>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>>>> To unsubscribe, send any mail to " >>>>> freebsd-hackers-unsubscribe@freebsd.org" >>>>>=20 >>>>> What kind of operations are you doing? >>>>>=20 >>>>> I just mounted a share from my windows desktop on my FreeBSD >>>>> -CURRENT machine, and was able to write new files at 64 >>>>> megabytes/s (roughly 1/2 the available gigabit/sec) >>>>>=20 >>>>> Reading it back only got 50 megabytes/s, not sure why. >>>>>=20 >>>>> -- >>>>> Allan Jude >>>> Which one is the server? Windows or FBSD? >>>>=20 >>>> I have no problems with either one being the server. The problem is >>>> when FBSD is the client. >>>>=20 >>>> I wrote a daemon that executes operations on old DBF/NTX (clipper) >>>> files (Yeah, I know ... but that's what they have for 20+ years = ..). >>>>=20 >>>> Anyway, a site interacts with this daemon via tcp, with commands to >>>> add/delete/update records/indexes, as well as finding keys on the >>>> indexxes. >>>>=20 >>>> I prepared a test that has several of these routines together on a >>>> 10.2-STABLE machine. >>>>=20 >>>> Enough to say that when executing the tests with the files stored >>>> locally, the whole test takes 3-4 seconds to complete. >>>>=20 >>>> When doing the same test with the files on a share on the same wire >>>> (1G connection, no matter which OS runs the share), the test takes >>>> around 3:50 minutes to complete! >>>>=20 >>>> I am preparing a Centos VM and compiling the deamon on it to check >>>> the results. >>>>=20 >>>> -- >>>> Mario Lobo >>>> http://www.mallavoodoo.com.br >>>> FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% >>>> winfoes FREE) _______________________________________________ >>>> freebsd-hackers@freebsd.org mailing list >>>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>> To unsubscribe, send any mail to >>>> "freebsd-hackers-unsubscribe@freebsd.org" >>=20 >>=20 >>=20 >> -- >> Mario Lobo >> http://www.mallavoodoo.com.br >> FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] >>=20 >> "UNIX was not designed to stop you from doing stupid things, >> because that would also stop you from doing clever things." >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >>=20 > _______________________________________________ > freebsd-hackers@freebsd.org = mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers = > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org = " From owner-freebsd-hackers@freebsd.org Sun Nov 15 01:13:25 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC903A2ECE1 for ; Sun, 15 Nov 2015 01:13:25 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) Received: from barracuda.ixsystems.com (mail.ixsystems.com [69.198.165.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 93AE91387 for ; Sun, 15 Nov 2015 01:13:25 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) X-ASG-Debug-ID: 1447550001-08ca040e840d810002-P5m3U7 Received: from [10.0.1.8] (ip72-209-175-134.ks.ks.cox.net [72.209.175.134]) by barracuda.ixsystems.com with ESMTP id rfFBIVD8xCTBCOHz (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 14 Nov 2015 17:13:22 -0800 (PST) X-Barracuda-Envelope-From: jmaloney@pcbsd.org X-Barracuda-AUTH-User: jmaloney@pcbsd.org X-Barracuda-Apparent-Source-IP: 72.209.175.134 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: FreeBSD smbfs horribly slow From: Joe Maloney X-ASG-Orig-Subj: Re: FreeBSD smbfs horribly slow In-Reply-To: <310B6D45-63E1-4012-BA35-8CB40CE9EBCF@pcbsd.org> Date: Sat, 14 Nov 2015 19:13:21 -0600 Cc: Mario Lobo , Mark Saad , Allan Jude , freebsd-hackers@freebsd.org Message-Id: <9044E3FC-BD0A-4F28-8AD3-98D743A99452@pcbsd.org> References: <20151113162548.61529137@Papi> <56463ACE.5020605@freebsd.org> <20151114115022.781c0bc1@Papi> <1312151904.87133792.1447539054621.JavaMail.zimbra@uoguelph.ca> <310B6D45-63E1-4012-BA35-8CB40CE9EBCF@pcbsd.org> To: Rick Macklem X-Mailer: Apple Mail (2.3096.5) X-Barracuda-Connect: ip72-209-175-134.ks.ks.cox.net[72.209.175.134] X-Barracuda-Start-Time: 1447550002 X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA X-Barracuda-URL: https://10.2.0.41:443/cgi-mod/mark.cgi X-Barracuda-BRTS-Status: 1 X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests=HTML_MESSAGE X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.24400 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE BODY: HTML included in message Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 01:13:25 -0000 Just to clarify what I was intending to ask I am curious about the = state, and health of the current smbfs code in FreeBSD. That is why I = am trying to determine where it originated from, etc. If there might be = a newer version of it, or if it=E2=80=99s still the best way of mounting = a CIFS share on FreeBSD. Joe Maloney > On Nov 14, 2015, at 7:02 PM, Joe Maloney wrote: >=20 > I=E2=80=99ve noticed that with the freebsd version of mount_smbfs I am = not able to mount an airport disk. With FreeBSD I can use gvfs = available in ports to get around that issue. >=20 > https://github.com/freebsd/freebsd/tree/master/contrib/smbfs = > >=20 > However with the Mac OS X version of mount_smbfs I can mount an = airport disk. I realize this structure, and ASPL clobbering is pretty = gross to look at. Apologies in advance. I am curious if there is = anything useful to see here. >=20 > http://opensource.apple.com/source/smb/smb-759.40.1/ = = > >=20 > =46rom what I can tell it looks like the mount_smbfs tool originated = in FreeBSD, and was ported to other BSD=E2=80=99s? Or is FreeBSD using = this which has been abandoned by Linux? =20 >=20 > https://www.samba.org/samba/smbfs/ = > >=20 > Joe Maloney >=20 >> On Nov 14, 2015, at 4:10 PM, Rick Macklem > wrote: >>=20 >> Mario Lobo wrote: >>> On Fri, 13 Nov 2015 19:04:05 -0500 >>> Mark Saad wrote: >>>=20 >>>> Mario >>>> Can you share more about your setup . >>>> What filesystem is the samba share exported from ? >>>=20 >>> The shares tested were both from a FBSD (10.2-STABLE) samba4 and = Linux >>> (Centos) samba 3.6. >>>=20 >>>> What mount options >>>> on the filesystem level do you use ? >>>>=20 >>>=20 >>> smbfs rw,noatime,-N,-Iserverip 0 0 >>>=20 >>>> What version of samba , was it from ports or a package ? >>>>=20 >>>=20 >>> See above. >>>=20 >>>> On the samba level can you tell us about your config ? Have you = tried >>>> any of the tuning from https://calomel.org/samba_optimize.html >>>>=20 >>>=20 >>> Like I said, the problem is not with the server. >>>=20 >>>> Did you change any sysctls ? What did you set ? >>>>=20 >>>> Lastly what's the hardware like ; CPU, nic type , ram , etc >>>>=20 >>>=20 >>> I tried the same FBSD client on different hardware. Made no = difference. >>>=20 >> Did that different hardware have a different type of net interface = that >> uses a different net device driver? >>=20 >> I have no idea if smbfs can do the same thing, but both NFS and iSCSI >> can generate TCP TSO output segments of near 64K in data length and >> that can cause problems for some net device drivers. >> --> If the net interface has TSO enabled, try disabling it. >>=20 >> I never use smbfs, so I can't help more, rick >>=20 >>>=20 >>>=20 >>>> --- >>>> Mark Saad | nonesuch@longcount.org >>>>=20 >>>>> On Nov 13, 2015, at 6:13 PM, Mario Lobo wrote: >>>>>=20 >>>>> 2015-11-13 16:32 GMT-03:00 Allan Jude : >>>>>=20 >>>>>>> On 2015-11-13 14:25, Mario Lobo wrote: >>>>>>> Hi; >>>>>>>=20 >>>>>>> It seems no one in @questions had any info/pointers/interest on >>>>>>> this so I'm trying @hackers for some light. >>>>>>>=20 >>>>>>> Thanks, >>>>>>>=20 >>>>>>>=20 >>>>>>> Begin forwarded message: >>>>>>>=20 >>>>>>> Date: Wed, 11 Nov 2015 17:53:11 -0300 >>>>>>> From: Mario Lobo >>>>>>> To: freebsd-questions >>>>>>> Subject: FreeBSD smbfs horribly slow >>>>>>>=20 >>>>>>> Googling on this subject, I found: >>>>>> = http://lists.freebsd.org/pipermail/freebsd-questions/2005-September/098717= .html >>>>>>> = https://lists.freebsd.org/pipermail/freebsd-net/2013-January/034239.html >>>>>> = https://lists.freebsd.org/pipermail/freebsd-questions/2014-October/261804.= html >>>>>>>=20 >>>>>>> I am on 10.2-STABLE and using FreeBSD as a client to any amb = share >>>>>>> continues to be very slow. >>>>>>>=20 >>>>>>> The share is mounted through mount_smbfs. I tried smbnetfs = (fuse) >>>>>>> and it is just a tiny bit better but doesn't compare to other >>>>>>> clients (linux or win) when writing/reading files >>>>>>>=20 >>>>>>> It gets even worse if an application is doing operations with >>>>>>> variable size records inside a data file on the share. >>>>>>>=20 >>>>>>> Does anyone have any advice to improve this? >>>>>>>=20 >>>>>>> Thanks, >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> _______________________________________________ >>>>>>> freebsd-hackers@freebsd.org mailing list >>>>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>>>>> To unsubscribe, send any mail to " >>>>>> freebsd-hackers-unsubscribe@freebsd.org" >>>>>>=20 >>>>>> What kind of operations are you doing? >>>>>>=20 >>>>>> I just mounted a share from my windows desktop on my FreeBSD >>>>>> -CURRENT machine, and was able to write new files at 64 >>>>>> megabytes/s (roughly 1/2 the available gigabit/sec) >>>>>>=20 >>>>>> Reading it back only got 50 megabytes/s, not sure why. >>>>>>=20 >>>>>> -- >>>>>> Allan Jude >>>>> Which one is the server? Windows or FBSD? >>>>>=20 >>>>> I have no problems with either one being the server. The problem = is >>>>> when FBSD is the client. >>>>>=20 >>>>> I wrote a daemon that executes operations on old DBF/NTX (clipper) >>>>> files (Yeah, I know ... but that's what they have for 20+ years = ..). >>>>>=20 >>>>> Anyway, a site interacts with this daemon via tcp, with commands = to >>>>> add/delete/update records/indexes, as well as finding keys on the >>>>> indexxes. >>>>>=20 >>>>> I prepared a test that has several of these routines together on a >>>>> 10.2-STABLE machine. >>>>>=20 >>>>> Enough to say that when executing the tests with the files stored >>>>> locally, the whole test takes 3-4 seconds to complete. >>>>>=20 >>>>> When doing the same test with the files on a share on the same = wire >>>>> (1G connection, no matter which OS runs the share), the test takes >>>>> around 3:50 minutes to complete! >>>>>=20 >>>>> I am preparing a Centos VM and compiling the deamon on it to check >>>>> the results. >>>>>=20 >>>>> -- >>>>> Mario Lobo >>>>> http://www.mallavoodoo.com.br >>>>> FreeBSD since version 2.2.8 [not Pro-Audio.... YET!!] (99,7% >>>>> winfoes FREE) _______________________________________________ >>>>> freebsd-hackers@freebsd.org mailing list >>>>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>>>> To unsubscribe, send any mail to >>>>> "freebsd-hackers-unsubscribe@freebsd.org" >>>=20 >>>=20 >>>=20 >>> -- >>> Mario Lobo >>> http://www.mallavoodoo.com.br >>> FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] >>>=20 >>> "UNIX was not designed to stop you from doing stupid things, >>> because that would also stop you from doing clever things." >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >>>=20 >> _______________________________________________ >> freebsd-hackers@freebsd.org = > mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers = = > >> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org = = >" >=20 > _______________________________________________ > freebsd-hackers@freebsd.org = mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers = > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org = " From owner-freebsd-hackers@freebsd.org Sun Nov 15 06:42:05 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4EC97A2FFF0 for ; Sun, 15 Nov 2015 06:42:05 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 122C81CD0 for ; Sun, 15 Nov 2015 06:42:04 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id D50D3D3F7 for ; Sun, 15 Nov 2015 06:41:57 +0000 (UTC) Subject: Re: FreeBSD smbfs horribly slow To: freebsd-hackers@freebsd.org References: <20151113162548.61529137@Papi> <56463ACE.5020605@freebsd.org> <20151114115022.781c0bc1@Papi> <1312151904.87133792.1447539054621.JavaMail.zimbra@uoguelph.ca> <310B6D45-63E1-4012-BA35-8CB40CE9EBCF@pcbsd.org> <9044E3FC-BD0A-4F28-8AD3-98D743A99452@pcbsd.org> From: Allan Jude X-Enigmail-Draft-Status: N1110 Message-ID: <5648292F.6080304@freebsd.org> Date: Sun, 15 Nov 2015 01:41:51 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <9044E3FC-BD0A-4F28-8AD3-98D743A99452@pcbsd.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xxfLP5Untbn67uw2JbVg0cWkpSabhsAWR" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 06:42:05 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xxfLP5Untbn67uw2JbVg0cWkpSabhsAWR Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2015-11-14 20:13, Joe Maloney wrote: > Just to clarify what I was intending to ask I am curious about the stat= e, and health of the current smbfs code in FreeBSD. That is why I am try= ing to determine where it originated from, etc. If there might be a newe= r version of it, or if it=E2=80=99s still the best way of mounting a CIFS= share on FreeBSD. >=20 > Joe Maloney >=20 >> On Nov 14, 2015, at 7:02 PM, Joe Maloney wrote: >> >> I=E2=80=99ve noticed that with the freebsd version of mount_smbfs I am= not able to mount an airport disk. With FreeBSD I can use gvfs availabl= e in ports to get around that issue. >> >> https://github.com/freebsd/freebsd/tree/master/contrib/smbfs > >> >> However with the Mac OS X version of mount_smbfs I can mount an airpor= t disk. I realize this structure, and ASPL clobbering is pretty gross to= look at. Apologies in advance. I am curious if there is anything usefu= l to see here. >> >> http://opensource.apple.com/source/smb/smb-759.40.1/ = > >> >> From what I can tell it looks like the mount_smbfs tool originated in = FreeBSD, and was ported to other BSD=E2=80=99s? Or is FreeBSD using this = which has been abandoned by Linux? =20 >> >> https://www.samba.org/samba/smbfs/ > >> >> Joe Maloney >> If I am not mistaken, our SMBFS comes from here: http://sourceforge.net/projects/smbfs/ https://svnweb.freebsd.org/base/head/contrib/smbfs/README?view=3Dmarkup And was last updated in 2002. However, as I posted earlier, it seems to be relatively performant for me, in straight line read/write. I am do more testing if someone has a specific workload in mine. --=20 Allan Jude --xxfLP5Untbn67uw2JbVg0cWkpSabhsAWR Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJWSCk1AAoJEBmVNT4SmAt+st0P/AqtlT7GmLjwu101oxYg3iHm kKsK9QBspgv/FCvdtZv04i9HSm2T5BH2b5NuIK4js3EvbeUgP2/vivxQl8J6jTLn 7mC2CfTlEpeiaV5FaH7k+8FtPGW/i8FftLe9VzaaTjDsYJITTIrtQSAvoWE/9gZZ fjs4eUGNTpGN92sQF33F9M6atOv/SCj6h/OI4oWDR7KZgjH/R/SzXtSe/k6tmX1O yx7ac8SqbbVG2iIOZIw/kn5ueU2kvLpCxWJ2DLJU4WvPxlCQnsIuGlBfLspn9Je7 oljRFnH/C2nL7UgMZp+KwSZlMa4/TCN0P7ZoJBMRjKlepdipswxsRs1ZHqYoR25+ 98OKwhIUErEzYAAaiG7ge1rhHdxuQfAr4wHAjbzJMnYy0lhLCy0hQXgUdbaIpxDZ IGKKiTrNoJ2fBclzCT5uz1kmqN22kRE32epiJptcFKwdSdf68rJzZ4eP5Wc+MKOO 6RPV0RDhKkDW1nRoRi9jO3+m1hBpaMOk40MlFDEbluQ5mWCBPajfwyU5+qWT0EgT SN8tMUn6Q3UbUyMufhQ6WIeOuXXxonPmWdoZ7Shssaj4TmxmcbvTWUiF1nT3vnHZ tVHcEQsUe0ykSDqeay2FiCuBErl7I9GOzShWXmUvc+yHsz9tqaZeM0QF2dhqnckT zX06V7sn9DaGGBgOTYtt =r3lu -----END PGP SIGNATURE----- --xxfLP5Untbn67uw2JbVg0cWkpSabhsAWR-- From owner-freebsd-hackers@freebsd.org Sun Nov 15 09:23:06 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44B82A2FB20 for ; Sun, 15 Nov 2015 09:23:06 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3392B109F for ; Sun, 15 Nov 2015 09:23:06 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id 2F130A2FB1F; Sun, 15 Nov 2015 09:23:06 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2DA96A2FB1E for ; Sun, 15 Nov 2015 09:23:06 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) by mx1.freebsd.org (Postfix) with ESMTP id DF9B0109E for ; Sun, 15 Nov 2015 09:23:05 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from chamsa.cs.huji.ac.il ([132.65.80.19]) by kabab.cs.huji.ac.il with esmtp id 1ZxtWR-000IgW-Ji for hackers@freebsd.org; Sun, 15 Nov 2015 11:22:55 +0200 From: Daniel Braniss Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: kqueue of a nfs mounted file not working Message-Id: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> Date: Sun, 15 Nov 2015 11:22:55 +0200 To: hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 09:23:06 -0000 HI, I=E2=80=99m writing a program to monitor a file using kqueue(2), if the = file is local all is OK, but if the file is via a nfs mounted fs, it only works once. stat shows the file growing, but kevent is not triggered. bug or feature? danny From owner-freebsd-hackers@freebsd.org Sun Nov 15 15:55:01 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18BCEA2F690 for ; Sun, 15 Nov 2015 15:55:01 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id F11241533 for ; Sun, 15 Nov 2015 15:55:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id EE366A2F68F; Sun, 15 Nov 2015 15:55:00 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EDD8EA2F68E for ; Sun, 15 Nov 2015 15:55:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 833F5152E for ; Sun, 15 Nov 2015 15:55:00 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id tAFFQaLK009148 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 15 Nov 2015 17:26:36 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua tAFFQaLK009148 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id tAFFQaTh009147; Sun, 15 Nov 2015 17:26:36 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Sun, 15 Nov 2015 17:26:36 +0200 From: Konstantin Belousov To: Daniel Braniss Cc: hackers@freebsd.org Subject: Re: kqueue of a nfs mounted file not working Message-ID: <20151115152635.GB5854@kib.kiev.ua> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Nov 2015 15:55:01 -0000 On Sun, Nov 15, 2015 at 11:22:55AM +0200, Daniel Braniss wrote: > HI, > I???m writing a program to monitor a file using kqueue(2), if the file is local > all is OK, but if the file is via a nfs mounted fs, it only works once. > stat shows the file growing, but kevent is not triggered. Does file grow due to local changes on the nfs client, or some other client changes the file, while your client tries to get kevent notifications ? From owner-freebsd-hackers@freebsd.org Mon Nov 16 00:55:21 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6BB4CA30EA8 for ; Mon, 16 Nov 2015 00:55:21 +0000 (UTC) (envelope-from mark@heily.com) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3F4EA19C3 for ; Mon, 16 Nov 2015 00:55:21 +0000 (UTC) (envelope-from mark@heily.com) Received: by igvg19 with SMTP id g19so65846614igv.1 for ; Sun, 15 Nov 2015 16:55:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heily_com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to:content-type; bh=C2an87fG0Gg19W+jaHQDCNWkWC+hjUaf41vKUXy5qro=; b=H17fh6t94iDqJ0h/py5TZquIZk9Di8frz+frIx+k9kjCMaaHkmY/qo+5bsuQOYlrT6 WdyfjUBgkdZueefkWmol0BZSOeYF6/soVXGSjk/YzdZrts9Rb2hG0wVgbD3S3tw/X0FN qG5w/a0VFZQE0DsiVio5dRNFIV9KA2uc6pocnH5UIbJaDAA2OQWbhafx0Ra3hDeffYtq FKbdcIUUzANbOvGrICS1Tt42fCVOA8pbA3VDHcjouo/7M/lpuI+wVRYSBSEhL46GtGDi p0/sMhT7oKQmEjbhFXF4MAlgsnl+ZQ8E/l3GwJf8wh9udkjjuhqQgoGGazoCWqPGW5Vt BGRQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=C2an87fG0Gg19W+jaHQDCNWkWC+hjUaf41vKUXy5qro=; b=H9LVCdIYd3nLDO1AtFgrvAvt4XlZDEwd5azLPUkVAtYifUVJH5YHxBPPtvEpR6NsbX VbbTJyeTcOO2FeDjdhYQyMc2di5uiPfMrSK66EFkN/3qfUQrr6x7NtcZ57dvSsV8vtJE Gv7HrVVodqn6nQcDj3w+GEk6JxiVi9gEU7GE8n1wDNxrWikOTktcvkWOTG3ZuFrcK9Cm 2jw3dH5hVPXaQYNWnX6ctQJ2EgRJwFd/qp7LwB/bSxRArh5ECXEJn/9zJh/qjpxBoIaM ttmj1T1swpZMrV0bRXfARi0DvopANWXvmDaFXIfJoITipIfyCcxSOPcCeu5tSY0NdZIQ qD6A== X-Gm-Message-State: ALoCoQkZK5uOBJ031oAE22UWw63ogRAf0svhEwRlMUN3ibt40UOuwp2K6YmXhN3JjOZ41bSjFrOL MIME-Version: 1.0 X-Received: by 10.50.136.226 with SMTP id qd2mr14459857igb.37.1447635320634; Sun, 15 Nov 2015 16:55:20 -0800 (PST) Received: by 10.79.84.199 with HTTP; Sun, 15 Nov 2015 16:55:20 -0800 (PST) X-Originating-IP: [71.70.169.30] Date: Sun, 15 Nov 2015 19:55:20 -0500 Message-ID: Subject: relaunchd: a portable clone of launchd From: Mark Heily To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 00:55:21 -0000 I've written a clone of the launchd framework found in Mac OS X [1]. It's called "relaunchd" and I would like to some help improving it and getting it added to the FreeBSD ports tree [2]. Here's the source code: https://github.com/mheily/relaunchd One of the coolest things I've been able to do with it is to use socket activation to launch an unmodified version of Apache inside of a jail, pass it a socket descriptor bound to port 80 from the primary network interface outside of the jail, and have it "just work" and start serving web content using the pre-existing socket descriptor. This eliminates the need to setup a cumbersome NAT and port forwarding mechanism for each jail [3]. This is a completely separate line of development from the work that the NextBSD folks are doing to port the published Apple source code for launchd and all of it's dependencies. I'd be happy to answer questions about relaunchd, and welcome contributions from anyone who wants to help make launchd on FreeBSD a reality. Regards, - Mark [1] https://en.wikipedia.org/wiki/Launchd [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204240 [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ From owner-freebsd-hackers@freebsd.org Mon Nov 16 01:17:51 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E2CDBA2F2FB for ; Mon, 16 Nov 2015 01:17:50 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) Received: from barracuda.ixsystems.com (mail.ixsystems.com [69.198.165.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BB9431272 for ; Mon, 16 Nov 2015 01:17:49 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) X-ASG-Debug-ID: 1447636667-08ca040e840df30002-P5m3U7 Received: from [10.0.1.8] (ip72-209-175-134.ks.ks.cox.net [72.209.175.134]) by barracuda.ixsystems.com with ESMTP id mI9R69DFZrdH9sLT (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 15 Nov 2015 17:17:48 -0800 (PST) X-Barracuda-Envelope-From: jmaloney@pcbsd.org X-Barracuda-AUTH-User: jmaloney@pcbsd.org X-Barracuda-Apparent-Source-IP: 72.209.175.134 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: relaunchd: a portable clone of launchd From: Joe Maloney X-ASG-Orig-Subj: Re: relaunchd: a portable clone of launchd In-Reply-To: Date: Sun, 15 Nov 2015 19:17:47 -0600 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <21B2B211-C52C-4202-BC5F-A190B9C12CD3@pcbsd.org> References: To: Mark Heily X-Mailer: Apple Mail (2.3096.5) X-Barracuda-Connect: ip72-209-175-134.ks.ks.cox.net[72.209.175.134] X-Barracuda-Start-Time: 1447636668 X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA X-Barracuda-URL: https://10.2.0.41:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests= X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.24424 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 01:17:51 -0000 Awesome. Thank you! I will definitely be trying this out. One = question. Are there any plans to convert this work over from json to = UCL which FreeBSD uses for things like pkg? It is my understanding that = UCL can parse json anyway, and is the preferred format for FreeBSD from = what I can tell? Joe Maloney > On Nov 15, 2015, at 6:55 PM, Mark Heily wrote: >=20 > I've written a clone of the launchd framework found in Mac OS X [1]. > It's called "relaunchd" and I would like to some help improving it and > getting it added to the FreeBSD ports tree [2]. >=20 > Here's the source code: >=20 > https://github.com/mheily/relaunchd >=20 > One of the coolest things I've been able to do with it is to use > socket activation to launch an unmodified version of Apache inside of > a jail, pass it a socket descriptor bound to port 80 from the primary > network interface outside of the jail, and have it "just work" and > start serving web content using the pre-existing socket descriptor. > This eliminates the need to setup a cumbersome NAT and port forwarding > mechanism for each jail [3]. >=20 > This is a completely separate line of development from the work that > the NextBSD folks are doing to port the published Apple source code > for launchd and all of it's dependencies. >=20 > I'd be happy to answer questions about relaunchd, and welcome > contributions from anyone who wants to help make launchd on FreeBSD a > reality. >=20 > Regards, >=20 > - Mark >=20 > [1] https://en.wikipedia.org/wiki/Launchd > [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204240 > [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Mon Nov 16 01:27:52 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 97034A2F54A for ; Mon, 16 Nov 2015 01:27:52 +0000 (UTC) (envelope-from mark@heily.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5B32C1845 for ; Mon, 16 Nov 2015 01:27:52 +0000 (UTC) (envelope-from mark@heily.com) Received: by iofh3 with SMTP id h3so146035296iof.3 for ; Sun, 15 Nov 2015 17:27:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heily_com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=s2lJZBoXN3tr27pamm6H1Nk6iq7kb3sRoODSR+l5XsM=; b=n1tx/W1S9NfTh3r+sNN3bhU+xPUcwNaKZPa5EiiL/sbnW0ZQzrdXDa1MEoji+ROTVI 8mBIqnaHLSQAG47JD+Z/AHPOjkO+6UZvZuJ0IkL9ae4yLE3PpbLlYJSwagalXA1S3hCl JhCEa3hY6sYzxCvxWmtaWOjIpUxts0ofqz6z9Do2fPZt/xxqwVbhdv4223G+9JOL9cHz 81dtGxAgreiJHP0Ch4aUQjljw9WxgTZmz+XttEpLZXmETnkVdJaSMMOc9T30lqR9fXoS qns+yRSfNeyCyZMJCerSz6Eq1O0C8mBvuGNJevKrtF0P0nUD7YKW+5l5JBHT0BZrq6vk QoIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=s2lJZBoXN3tr27pamm6H1Nk6iq7kb3sRoODSR+l5XsM=; b=HQBihhzQH2zSH95lV4o5a4LDypifvtYeAQnMYe8dDoanR7L7eTm0f/i4SIAYclN+xP HLVwsbWLZaU2Js4Eg5L/kZ/Gw0vJm1E/fhoC2lS6JWRpybMWH1Y4UdxTacufRe63bBwn PMVtEPkVo5GJ1RjYnAyInzT5Tb0groWe+Q3hgf+H9DKvvTZ8m+Ti2Y3iP8kBCU9vKgsa JpDKKtkP+YTA+s2YjY11yY0jnWE2Dgl8JFFxsM2MFzCFgRt7Dnhhtm6EhTob+MqkuwQ6 68QC+Rf6e0gpOWjQgxgjzcublmRoUFL3hHuDFpucqHwa4T7JQzxAmI2lxO7+S8HYaSHi LHsQ== X-Gm-Message-State: ALoCoQlsKrsk5mSZvvMoKhM7vcGUd81GeGNyhBgyhAKf4bqxHFmV4htWqVDx1C6spLXwxeJ6PwvG MIME-Version: 1.0 X-Received: by 10.107.186.132 with SMTP id k126mr28382869iof.158.1447637271563; Sun, 15 Nov 2015 17:27:51 -0800 (PST) Received: by 10.79.84.199 with HTTP; Sun, 15 Nov 2015 17:27:51 -0800 (PST) X-Originating-IP: [71.70.169.30] In-Reply-To: <21B2B211-C52C-4202-BC5F-A190B9C12CD3@pcbsd.org> References: <21B2B211-C52C-4202-BC5F-A190B9C12CD3@pcbsd.org> Date: Sun, 15 Nov 2015 20:27:51 -0500 Message-ID: Subject: Re: relaunchd: a portable clone of launchd From: Mark Heily To: Joe Maloney Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 01:27:52 -0000 On Sun, Nov 15, 2015 at 8:17 PM, Joe Maloney wrote: > Awesome. Thank you! I will definitely be trying this out. One question.= Are there any plans to convert this work over from json to UCL which Free= BSD uses for things like pkg? It is my understanding that UCL can parse js= on anyway, and is the preferred format for FreeBSD from what I can tell? > Yes, I do plan to migrate from JSON to UCL, and there's an open ticket in GitHub about it: https://github.com/mheily/relaunchd/issues/1 However, in terms of priority, it's not at the top of my list. Before rewriting the parser to use UCL, I'd like to finish implementing the missing functionality documented in the README: * unloading jobs via launchctl * cron functionality - StartInterval, StartCalendarInterval * file and directory watches - WatchPaths, QueueDirectories * restarting jobs if they crash - TimeOut, ExitTimeout, KeepAliveTimeout, ThrottleInterval * resource limits - SoftResourceLimits, HardResourceLimits * miscellaneous - LaunchOnlyOnce, inetdCompatibility, EnableGlobbing, RunAtLoad, Umask If anyone wants to help implement these missing pieces, or if you enjoy rewriting parsers and want to play around with UCL, let me know. > Joe Maloney > >> On Nov 15, 2015, at 6:55 PM, Mark Heily wrote: >> >> I've written a clone of the launchd framework found in Mac OS X [1]. >> It's called "relaunchd" and I would like to some help improving it and >> getting it added to the FreeBSD ports tree [2]. >> >> Here's the source code: >> >> https://github.com/mheily/relaunchd >> >> One of the coolest things I've been able to do with it is to use >> socket activation to launch an unmodified version of Apache inside of >> a jail, pass it a socket descriptor bound to port 80 from the primary >> network interface outside of the jail, and have it "just work" and >> start serving web content using the pre-existing socket descriptor. >> This eliminates the need to setup a cumbersome NAT and port forwarding >> mechanism for each jail [3]. >> >> This is a completely separate line of development from the work that >> the NextBSD folks are doing to port the published Apple source code >> for launchd and all of it's dependencies. >> >> I'd be happy to answer questions about relaunchd, and welcome >> contributions from anyone who wants to help make launchd on FreeBSD a >> reality. >> >> Regards, >> >> - Mark >> >> [1] https://en.wikipedia.org/wiki/Launchd >> [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204240 >> [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.or= g" > From owner-freebsd-hackers@freebsd.org Mon Nov 16 01:30:31 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0FCB4A2F688 for ; Mon, 16 Nov 2015 01:30:31 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) Received: from barracuda.ixsystems.com (mail.ixsystems.com [69.198.165.135]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "*.ixsystems.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E14701AE2 for ; Mon, 16 Nov 2015 01:30:30 +0000 (UTC) (envelope-from jmaloney@pcbsd.org) X-ASG-Debug-ID: 1447637428-08ca040e850ddb0002-P5m3U7 Received: from [10.0.1.8] (ip72-209-175-134.ks.ks.cox.net [72.209.175.134]) by barracuda.ixsystems.com with ESMTP id pz5ORFVwuVnGqIiZ (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 15 Nov 2015 17:30:29 -0800 (PST) X-Barracuda-Envelope-From: jmaloney@pcbsd.org X-Barracuda-AUTH-User: jmaloney@pcbsd.org X-Barracuda-Apparent-Source-IP: 72.209.175.134 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: relaunchd: a portable clone of launchd From: Joe Maloney X-ASG-Orig-Subj: Re: relaunchd: a portable clone of launchd In-Reply-To: Date: Sun, 15 Nov 2015 19:30:28 -0600 Cc: freebsd-hackers@freebsd.org Message-Id: References: <21B2B211-C52C-4202-BC5F-A190B9C12CD3@pcbsd.org> To: Mark Heily X-Mailer: Apple Mail (2.3096.5) X-Barracuda-Connect: ip72-209-175-134.ks.ks.cox.net[72.209.175.134] X-Barracuda-Start-Time: 1447637428 X-Barracuda-Encrypted: ECDHE-RSA-AES256-SHA X-Barracuda-URL: https://10.2.0.41:443/cgi-mod/mark.cgi X-Virus-Scanned: by bsmtpd at ixsystems.com X-Barracuda-BRTS-Status: 1 X-Barracuda-Spam-Score: 0.00 X-Barracuda-Spam-Status: No, SCORE=0.00 using global scores of TAG_LEVEL=1000.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=8.0 tests=HTML_MESSAGE X-Barracuda-Spam-Report: Code version 3.2, rules version 3.2.3.24425 Rule breakdown below pts rule name description ---- ---------------------- -------------------------------------------------- 0.00 HTML_MESSAGE BODY: HTML included in message Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 01:30:31 -0000 I was going to work on converting this xml version to UCL anyway. =20 https://github.com/pkgdemon/launchd_xml = I will see what I can do to help if someone else doesn=E2=80=99t get to = it before I do. Joe Maloney > On Nov 15, 2015, at 7:27 PM, Mark Heily wrote: >=20 > On Sun, Nov 15, 2015 at 8:17 PM, Joe Maloney = wrote: >> Awesome. Thank you! I will definitely be trying this out. One = question. Are there any plans to convert this work over from json to = UCL which FreeBSD uses for things like pkg? It is my understanding that = UCL can parse json anyway, and is the preferred format for FreeBSD from = what I can tell? >>=20 >=20 > Yes, I do plan to migrate from JSON to UCL, and there's an open ticket > in GitHub about it: >=20 > https://github.com/mheily/relaunchd/issues/1 >=20 > However, in terms of priority, it's not at the top of my list. Before > rewriting the parser to use UCL, I'd like to finish implementing the > missing functionality documented in the README: >=20 > * unloading jobs via launchctl > * cron functionality - StartInterval, StartCalendarInterval > * file and directory watches - WatchPaths, QueueDirectories > * restarting jobs if they crash - TimeOut, ExitTimeout, > KeepAliveTimeout, ThrottleInterval > * resource limits - SoftResourceLimits, HardResourceLimits > * miscellaneous - LaunchOnlyOnce, inetdCompatibility, EnableGlobbing, > RunAtLoad, Umask >=20 > If anyone wants to help implement these missing pieces, or if you > enjoy rewriting parsers and want to play around with UCL, let me know. >=20 >> Joe Maloney >>=20 >>> On Nov 15, 2015, at 6:55 PM, Mark Heily wrote: >>>=20 >>> I've written a clone of the launchd framework found in Mac OS X [1]. >>> It's called "relaunchd" and I would like to some help improving it = and >>> getting it added to the FreeBSD ports tree [2]. >>>=20 >>> Here's the source code: >>>=20 >>> https://github.com/mheily/relaunchd >>>=20 >>> One of the coolest things I've been able to do with it is to use >>> socket activation to launch an unmodified version of Apache inside = of >>> a jail, pass it a socket descriptor bound to port 80 from the = primary >>> network interface outside of the jail, and have it "just work" and >>> start serving web content using the pre-existing socket descriptor. >>> This eliminates the need to setup a cumbersome NAT and port = forwarding >>> mechanism for each jail [3]. >>>=20 >>> This is a completely separate line of development from the work that >>> the NextBSD folks are doing to port the published Apple source code >>> for launchd and all of it's dependencies. >>>=20 >>> I'd be happy to answer questions about relaunchd, and welcome >>> contributions from anyone who wants to help make launchd on FreeBSD = a >>> reality. >>>=20 >>> Regards, >>>=20 >>> - Mark >>>=20 >>> [1] https://en.wikipedia.org/wiki/Launchd >>> [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204240 >>> [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >>=20 From owner-freebsd-hackers@freebsd.org Mon Nov 16 07:08:18 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3B938A30B54 for ; Mon, 16 Nov 2015 07:08:18 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 289451439 for ; Mon, 16 Nov 2015 07:08:18 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id 24CFDA30B51; Mon, 16 Nov 2015 07:08:18 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 23761A30B50 for ; Mon, 16 Nov 2015 07:08:18 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) by mx1.freebsd.org (Postfix) with ESMTP id C909F1438 for ; Mon, 16 Nov 2015 07:08:17 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from chamsa.cs.huji.ac.il ([132.65.80.19]) by kabab.cs.huji.ac.il with esmtp id 1ZyDtd-0009sj-BB; Mon, 16 Nov 2015 09:08:13 +0200 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: kqueue of a nfs mounted file not working From: Daniel Braniss In-Reply-To: <20151115152635.GB5854@kib.kiev.ua> Date: Mon, 16 Nov 2015 09:08:12 +0200 Cc: hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> To: Konstantin Belousov X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 07:08:18 -0000 > On 15 Nov 2015, at 17:26, Konstantin Belousov = wrote: >=20 > On Sun, Nov 15, 2015 at 11:22:55AM +0200, Daniel Braniss wrote: >> HI, >> I???m writing a program to monitor a file using kqueue(2), if the = file is local >> all is OK, but if the file is via a nfs mounted fs, it only works = once. >> stat shows the file growing, but kevent is not triggered. >=20 > Does file grow due to local changes on the nfs client, or some other > client changes the file, while your client tries to get kevent = notifications ? it gets updated by a host which has the file as local, so yes, it gets = updated by another client/host. From owner-freebsd-hackers@freebsd.org Mon Nov 16 14:00:25 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B1122A30591 for ; Mon, 16 Nov 2015 14:00:25 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 871A41ABD for ; Mon, 16 Nov 2015 14:00:25 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 84423A30590; Mon, 16 Nov 2015 14:00:25 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A0A2A3058F for ; Mon, 16 Nov 2015 14:00:25 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 20FCB1ABC for ; Mon, 16 Nov 2015 14:00:24 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:dtejxhX78hwWB907IaB1bzwXNdfV8LGtZVwlr6E/grcLSJyIuqrYZhGCt8tkgFKBZ4jH8fUM07OQ6PC9HzFfqsvd+Fk5M7VyFDY9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQka3CwN5K6zPF5LIiIzvjqbpq8CVPloD2Wb1SIgxBSv1hD2ZjtMRj4pmJ/R54TryiVwMRd5rw3h1L0mYhRf265T41pdi9yNNp6BprJYYAu2pN5g/GJBRCjUrNygf/sTttALYBV+D730aQ00diVxIHgrEqhjxGJb15HjUrO14jRObNs6+aLk/WjCv6u8/UhrhgyQDOjsR7WbYl8F0lKIdqxv39E83+JLdfIzAbKk2RajaZ95PHWc= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DPAQCL4ElW/61jaINeDoQAbwa+WgENgWQXCoUlSgKBchQBAQEBAQEBAYEJgi2CCAEBBAEBASArIAsQAgEIDgoCAg0ZAgIhBgEJJgIECAcEARwEh3gDEg2qKIsoDYRSAQEBAQEBAQMBAQEBAQEBARcEgQGFU4R+glOBaAEBBYMzgUQFjhGIN4UdhSB1g1CTF4Nhg3ACHwEBQoNGXCA0B4QDOoEHAQEB X-IronPort-AV: E=Sophos;i="5.20,303,1444708800"; d="scan'208";a="250642909" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 16 Nov 2015 09:00:10 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 391C115F56D; Mon, 16 Nov 2015 09:00:10 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 6wv81vn_iDAM; Mon, 16 Nov 2015 09:00:09 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id C7B8015F56E; Mon, 16 Nov 2015 09:00:09 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 34Gwvo0NMREO; Mon, 16 Nov 2015 09:00:09 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 9A84415F56D; Mon, 16 Nov 2015 09:00:09 -0500 (EST) Date: Mon, 16 Nov 2015 09:00:09 -0500 (EST) From: Rick Macklem To: Daniel Braniss Cc: Konstantin Belousov , hackers@freebsd.org Message-ID: <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> In-Reply-To: <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> Subject: Re: kqueue of a nfs mounted file not working MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.11] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF34 (Win)/8.0.9_GA_6191) Thread-Topic: kqueue of a nfs mounted file not working Thread-Index: UtLIGiQ9lUEpiyCibLNTP1qc8D2nPQ== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 14:00:25 -0000 Daniel Braniss wrote: > > > On 15 Nov 2015, at 17:26, Konstantin Belousov wrote: > > > > On Sun, Nov 15, 2015 at 11:22:55AM +0200, Daniel Braniss wrote: > >> HI, > >> I???m writing a program to monitor a file using kqueue(2), if the file is > >> local > >> all is OK, but if the file is via a nfs mounted fs, it only works once. > >> stat shows the file growing, but kevent is not triggered. > > > > Does file grow due to local changes on the nfs client, or some other > > client changes the file, while your client tries to get kevent > > notifications ? > > it gets updated by a host which has the file as local, so yes, it gets > updated > by another client/host. > Hmm, I am not surprised that this doesn't work. The only indication to the client that the file has changed on the server is a change in the file's attributes when they're acquired (via a Getattr RPC or similar) from the server. There is a vfs operation called VFS_SYSCTL(). This isn't implemented on the current NFS client. It was implemented on the old one, but only for NFS locking events and I didn't understand what needed to be done, so I didn't do it. Kostik, do you know if there is a VFS_SYSCTL() call done when the kevent stuff is probing for a file size change? (Or does it not probe and events get triggered via the write syscall or ???) I took a quick look at the kevent stuff, but admit I got lost and couldn't figure out what triggered events being logged? Also, is the event for "file growing" or "file changed"? If it is the latter, all the NFS client can do is look for a change in the file's modify time and this is often at a resolution of 1sec., which implies that a change within the same second as the previous one may not be noticed. (NFSv4 has a Change attribute that is always guaranteed to change, but that is only NFSv4.) Also, you see metadata changes as well as data changes, at least for the NFSv4 attribute. rick > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Mon Nov 16 14:14:45 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 455A3A309D4 for ; Mon, 16 Nov 2015 14:14:45 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2D0F11553 for ; Mon, 16 Nov 2015 14:14:45 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 2A04BA309D3; Mon, 16 Nov 2015 14:14:45 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 28C4FA309D2 for ; Mon, 16 Nov 2015 14:14:45 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D17A71551 for ; Mon, 16 Nov 2015 14:14:44 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1ZyKYD-000F3r-J7; Mon, 16 Nov 2015 17:14:33 +0300 Date: Mon, 16 Nov 2015 17:14:33 +0300 From: Slawa Olhovchenkov To: Rick Macklem Cc: hackers@freebsd.org Subject: NFSv4 details and documentations Message-ID: <20151116141433.GA31314@zxy.spb.ru> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 14:14:45 -0000 On Mon, Nov 16, 2015 at 09:00:09AM -0500, Rick Macklem wrote: > There is a vfs operation called VFS_SYSCTL(). This isn't implemented on > the current NFS client. It was implemented on the old one, but only for > NFS locking events and I didn't understand what needed to be done, so I > didn't do it. Rick, I am try to play with NFSv4 and Kerberos and see lack of documentation. For example, nowhere documented that access to NFSv4 mount do by NFSv3 rules. I.e. I need have /etc/exports with TWO lines: V4: /NFS -sec=krb5i /NFS -sec=krb5i W/o second lines I got 10020 error (for NFSv4 mount). What current status Kerberos support in NFS client/server? I found many posts and wiki pages about lack some functionality, but also see many works from you. Can you give some examples for kerberoized setup, with support cron jobs? From owner-freebsd-hackers@freebsd.org Mon Nov 16 15:15:32 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63D05A305B8 for ; Mon, 16 Nov 2015 15:15:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4547F12CD for ; Mon, 16 Nov 2015 15:15:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 439BAA305B7; Mon, 16 Nov 2015 15:15:32 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 432CAA305B6 for ; Mon, 16 Nov 2015 15:15:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C3E9B12CC for ; Mon, 16 Nov 2015 15:15:31 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from tom.home (kostik@localhost [127.0.0.1]) by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id tAGFFDP9078596 (version=TLSv1 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 16 Nov 2015 17:15:13 +0200 (EET) (envelope-from kostikbel@gmail.com) DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua tAGFFDP9078596 Received: (from kostik@localhost) by tom.home (8.15.2/8.15.2/Submit) id tAGFFDd0078586; Mon, 16 Nov 2015 17:15:13 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 16 Nov 2015 17:15:13 +0200 From: Konstantin Belousov To: Rick Macklem Cc: Daniel Braniss , hackers@freebsd.org Subject: Re: kqueue of a nfs mounted file not working Message-ID: <20151116151513.GF5854@kib.kiev.ua> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> User-Agent: Mutt/1.5.24 (2015-08-30) X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00, DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no autolearn_force=no version=3.4.1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 15:15:32 -0000 On Mon, Nov 16, 2015 at 09:00:09AM -0500, Rick Macklem wrote: > Daniel Braniss wrote: > > > > > On 15 Nov 2015, at 17:26, Konstantin Belousov wrote: > > > > > > On Sun, Nov 15, 2015 at 11:22:55AM +0200, Daniel Braniss wrote: > > >> HI, > > >> I???m writing a program to monitor a file using kqueue(2), if the file is > > >> local > > >> all is OK, but if the file is via a nfs mounted fs, it only works once. > > >> stat shows the file growing, but kevent is not triggered. > > > > > > Does file grow due to local changes on the nfs client, or some other > > > client changes the file, while your client tries to get kevent > > > notifications ? > > > > it gets updated by a host which has the file as local, so yes, it gets > > updated > > by another client/host. > > > Hmm, I am not surprised that this doesn't work. The only indication to the > client that the file has changed on the server is a change in the file's > attributes when they're acquired (via a Getattr RPC or similar) from the server. > > There is a vfs operation called VFS_SYSCTL(). This isn't implemented on > the current NFS client. It was implemented on the old one, but only for > NFS locking events and I didn't understand what needed to be done, so I > didn't do it. You probably mean VOP_KQFILTER, not VFS_SYSCTL(). BTW, the later is only used by nfs and I do not quite see why its functionality not subsumed by the mount options. WRT VOP_KQFILTER, the default implementation is adequate. What is missed for NFS is the knote activation when the code notes that the cached metadata is invalidated by server. > Kostik, do you know if there is a VFS_SYSCTL() call done when the kevent > stuff is probing for a file size change? (Or does it not probe and events > get triggered via the write syscall or ???) I took a quick look at the kevent > stuff, but admit I got lost and couldn't figure out what triggered events > being logged? > > Also, is the event for "file growing" or "file changed"? > If it is the latter, all the NFS client can do is look for a change in > the file's modify time and this is often at a resolution of 1sec., which > implies that a change within the same second as the previous one may not > be noticed. (NFSv4 has a Change attribute that is always guaranteed to > change, but that is only NFSv4.) Also, you see metadata changes as well > as data changes, at least for the NFSv4 attribute. Please look at the sys/kern/vfs_subr.c lines 4296-4419. There is a bunch of the post-VOP hooks which are executed after the filesystem VOP method was executed. You would see the complete list of the notifications which are sent, and the way they are sent, by calling VFS_KNOTE{_LOCKED}(vp, NOTE_XXX). Similar calls should be spread over the nfs client code when the attribute cache entries are deleted, possibly comparing old and new values to select proper notification. But you are of course right that client cannot fully implement the notifications without the server notifying it, so whatever efforts are done for NFSv3, there are definitely will be cases which cannot work. I do not know NFSv4 enough to make similar statement, but I think something would prevent the complete implementation, e.g. for rename. This makes me wonder should we need to add the calls to VFS_KNOTE() into the nfs client, at all. It is similar to lockd/nolockd options, in that the client might be not interested in the server or other clients updates, only in the local notifications. This plus the fact that the feature cannot have complete implementation, raises the question. From owner-freebsd-hackers@freebsd.org Mon Nov 16 15:41:02 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3074FA30F9A for ; Mon, 16 Nov 2015 15:41:02 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 07FD718C6 for ; Mon, 16 Nov 2015 15:41:02 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 03B7DA30F99; Mon, 16 Nov 2015 15:41:02 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DEF90A30F98 for ; Mon, 16 Nov 2015 15:41:01 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 8EFE718C5 for ; Mon, 16 Nov 2015 15:41:01 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:D9X/bR+VLgcjYf9uRHKM819IXTAuvvDOBiVQ1KB91u4cTK2v8tzYMVDF4r011RmSDdidtq0P1LGempujcFJDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXsq3G/pQQfBg/4fVIsYL+lR8iP0I/ojKibwN76XUZhvHKFe7R8LRG7/036l/I9ps9cEJs30QbDuXBSeu5blitCLFOXmAvgtI/rpMYwu3cYh/V0zMpJTqyyWKA4SqJTDDkgMGcrrJnwsQbrXxueoGAEWCMMj0wbLRLC6UTAX5zy+g7zvel51SzSadfzRLs3XTmnx7psRwLljD8HcTUwpjKEwvdshb5W9Ury7yd0xJTZNdmY X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DZAQD390lW/61jaINehA5vBr5aAQ2BCARYFwqFJUoCgXYUAQEBAQEBAQGBCYItggcBAQEDAQEBASArIAsFCwIBCA4KAgINBQETAgInAQkmAgQIBwQBHASIBQgNA6ojkAoBAQEBAQEBAwEBAQEBAQEBFwSBAYVThH6EOwEBBWEBglGBRAWOEYg3hR2FICSEIZIWiFICHwEBQoQiIDQHg3wHFyOBBwEBAQ X-IronPort-AV: E=Sophos;i="5.20,303,1444708800"; d="scan'208";a="250665094" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 16 Nov 2015 10:40:59 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 146D615F56D; Mon, 16 Nov 2015 10:41:00 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id jPeJhXMuvGI5; Mon, 16 Nov 2015 10:40:59 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id A58C415F577; Mon, 16 Nov 2015 10:40:59 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id fxkMahbZcp0O; Mon, 16 Nov 2015 10:40:59 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 89D5D15F56D; Mon, 16 Nov 2015 10:40:59 -0500 (EST) Date: Mon, 16 Nov 2015 10:40:59 -0500 (EST) From: Rick Macklem To: Slawa Olhovchenkov Cc: hackers@freebsd.org Message-ID: <1489367909.88538127.1447688459383.JavaMail.zimbra@uoguelph.ca> In-Reply-To: <20151116141433.GA31314@zxy.spb.ru> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> <20151116141433.GA31314@zxy.spb.ru> Subject: Re: NFSv4 details and documentations MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.12] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF34 (Win)/8.0.9_GA_6191) Thread-Topic: NFSv4 details and documentations Thread-Index: TzBIzyoz1mCRPJh5uGJZHDLn7ZD8gg== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 15:41:02 -0000 Slawa Olhovchenkov wrote: > On Mon, Nov 16, 2015 at 09:00:09AM -0500, Rick Macklem wrote: > > > There is a vfs operation called VFS_SYSCTL(). This isn't implemented on > > the current NFS client. It was implemented on the old one, but only for > > NFS locking events and I didn't understand what needed to be done, so I > > didn't do it. > > Rick, I am try to play with NFSv4 and Kerberos and see lack of > documentation. For example, nowhere documented that access to NFSv4 > mount do by NFSv3 rules. I.e. I need have /etc/exports with TWO lines: > > V4: /NFS -sec=krb5i > /NFS -sec=krb5i > > W/o second lines I got 10020 error (for NFSv4 mount). > Well, "man exports" does try and say this (and I've reworded it several times), but it is confusing. In simple terms, the "V4:" line does not export any file system and needs to be added to whatever you export via other lines. > What current status Kerberos support in NFS client/server? I found > many posts and wiki pages about lack some functionality, but also see > many works from you. > The main limitation (which comes from the fact that the RPCSEC_GSS implementation is version 1) is that it expects to use DES, which requires "weak authentication" to be enabled. Although parts about adding patches for initiator credentials no longer applies, this is still fairly useful. https://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup Anyone willing to improve/update this is more than welcome to do so. (I, personally, haven't set up a Kerberized NFS for a couple of years and I hate fiddling with it. When something isn't working, isolating the problem can be very difficult.) Good luck with it, rick ps: I put it on google as a wiki so anyone could update it, but I don't think anyone ever has. As I recall, anyone with a google login can update it. > Can you give some examples for kerberoized setup, with support cron > jobs? > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Mon Nov 16 15:57:15 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 491E3A30376 for ; Mon, 16 Nov 2015 15:57:15 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 30FCC128F for ; Mon, 16 Nov 2015 15:57:15 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id 2CA69A30374; Mon, 16 Nov 2015 15:57:15 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1240EA30370 for ; Mon, 16 Nov 2015 15:57:15 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BE486128E for ; Mon, 16 Nov 2015 15:57:14 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1ZyM9X-000IKm-2v; Mon, 16 Nov 2015 18:57:11 +0300 Date: Mon, 16 Nov 2015 18:57:11 +0300 From: Slawa Olhovchenkov To: Rick Macklem Cc: hackers@freebsd.org Subject: Re: NFSv4 details and documentations Message-ID: <20151116155710.GB31314@zxy.spb.ru> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> <20151116141433.GA31314@zxy.spb.ru> <1489367909.88538127.1447688459383.JavaMail.zimbra@uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1489367909.88538127.1447688459383.JavaMail.zimbra@uoguelph.ca> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 15:57:15 -0000 On Mon, Nov 16, 2015 at 10:40:59AM -0500, Rick Macklem wrote: > Slawa Olhovchenkov wrote: > > On Mon, Nov 16, 2015 at 09:00:09AM -0500, Rick Macklem wrote: > > > > > There is a vfs operation called VFS_SYSCTL(). This isn't implemented on > > > the current NFS client. It was implemented on the old one, but only for > > > NFS locking events and I didn't understand what needed to be done, so I > > > didn't do it. > > > > Rick, I am try to play with NFSv4 and Kerberos and see lack of > > documentation. For example, nowhere documented that access to NFSv4 > > mount do by NFSv3 rules. I.e. I need have /etc/exports with TWO lines: > > > > V4: /NFS -sec=krb5i > > /NFS -sec=krb5i > > > > W/o second lines I got 10020 error (for NFSv4 mount). > > > Well, "man exports" does try and say this (and I've reworded it several times), > but it is confusing. In simple terms, the "V4:" line does not export any file system > and needs to be added to whatever you export via other lines. As I read this: adding '/NFS 127.0.0.1' is enough and secured. But this is wrong: not only exported, access control too. May be for NFS guru this is trivia, but for ordinary users this is confused. > > What current status Kerberos support in NFS client/server? I found > > many posts and wiki pages about lack some functionality, but also see > > many works from you. > > > The main limitation (which comes from the fact that the RPCSEC_GSS implementation > is version 1) is that it expects to use DES, which requires "weak authentication" > to be enabled. Although parts about adding patches for initiator credentials no longer > applies, this is still fairly useful. Hmm, I am have setup Kerberized NFS w/o "weak authentication" to be enabled, with mounted as 'nfsv4,intr,soft,sec=krb5i,allgssname,gssname=root'. What is requred DES in RPCSEC_GSS? (for me as user, how I can see what broken? some commands don't working or something else?) > https://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup Yes, I am talk about this. > Anyone willing to improve/update this is more than welcome to do so. (I, personally, > haven't set up a Kerberized NFS for a couple of years and I hate fiddling with it. > When something isn't working, isolating the problem can be very difficult.) Yes, I am already see it. > Good luck with it, rick > ps: I put it on google as a wiki so anyone could update it, but I don't think > anyone ever has. As I recall, anyone with a google login can update it. > > > Can you give some examples for kerberoized setup, with support cron > > jobs? > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@freebsd.org Mon Nov 16 23:00:20 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5E21BA31F25 for ; Mon, 16 Nov 2015 23:00:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 31A0811D7 for ; Mon, 16 Nov 2015 23:00:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 2D83AA31F24; Mon, 16 Nov 2015 23:00:20 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1225BA31F23 for ; Mon, 16 Nov 2015 23:00:20 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 9A7C211D6 for ; Mon, 16 Nov 2015 23:00:19 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:0mrMfB8tf7HpZ/9uRHKM819IXTAuvvDOBiVQ1KB80uMcTK2v8tzYMVDF4r011RmSDdidtqIP0rCempujcFJDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXsq3G/pQQfBg/4fVIsYL+lR8iP34/ujaibwN76XUZhvHKFe7R8LRG7/036l/I9ps9cEJs30QbDuXBSeu5blitCLFOXmAvgtI/rpMYwu3cYhvQ66sQVUbnmZ79qCvtcDS86KCY7/sDmvwLPCwyV6TwZW2QSlxNORAzE9w37WJn29SXgu+d3wyXfPcT9Tr0uQmee6PJQTBb3gW8gMz4+7mrXh8pzi7wT9AmluDRt05+Se5mfcuBjKPDzZ9QfEFBAVcUZciVKAYexasNbFe8INuVcoozVulwBsBa6HQnqD+q5mWwAvWP/waBvi7dpKgrBxgF1R98= X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2DQAQBTX0pW/61jaINdhA5vBr5bAQ2BCARZFwqFJUoCgX8UAQEBAQEBAQGBCYItggcBAQEDAQEBASArIAsFCwIBCA4KAgINBQETAgInAQkmAgQIBwQBHASIBQgNA6pDkEQBAQEBAQEBAwEBAQEBAQEYBIEBhVOEfoQ7AQEFYQGCUYFEBY4RiDeFHYUgJIQhh2WKMYhSAh8BAUKCDiCBdCA0B4M7BxcjgQcBAQE X-IronPort-AV: E=Sophos;i="5.20,304,1444708800"; d="scan'208";a="250754207" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 16 Nov 2015 18:00:17 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 3A3B415F565; Mon, 16 Nov 2015 18:00:17 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id tlmVue1rx2lp; Mon, 16 Nov 2015 18:00:16 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 7FCB615F56D; Mon, 16 Nov 2015 18:00:16 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id jANM795qXjtY; Mon, 16 Nov 2015 18:00:16 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 6433C15F565; Mon, 16 Nov 2015 18:00:16 -0500 (EST) Date: Mon, 16 Nov 2015 18:00:16 -0500 (EST) From: Rick Macklem To: Slawa Olhovchenkov Cc: hackers@freebsd.org Message-ID: <1312967974.89238067.1447714816355.JavaMail.zimbra@uoguelph.ca> In-Reply-To: <20151116155710.GB31314@zxy.spb.ru> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> <20151116141433.GA31314@zxy.spb.ru> <1489367909.88538127.1447688459383.JavaMail.zimbra@uoguelph.ca> <20151116155710.GB31314@zxy.spb.ru> Subject: Re: NFSv4 details and documentations MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF34 (Win)/8.0.9_GA_6191) Thread-Topic: NFSv4 details and documentations Thread-Index: rf0AjEdX2Am4mq6e8kNX6+GVmwAOcg== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 23:00:20 -0000 Slawa Olhovchenkov wrote: > On Mon, Nov 16, 2015 at 10:40:59AM -0500, Rick Macklem wrote: > > > Slawa Olhovchenkov wrote: > > > On Mon, Nov 16, 2015 at 09:00:09AM -0500, Rick Macklem wrote: > > > > > > > There is a vfs operation called VFS_SYSCTL(). This isn't implemented on > > > > the current NFS client. It was implemented on the old one, but only for > > > > NFS locking events and I didn't understand what needed to be done, so I > > > > didn't do it. > > > > > > Rick, I am try to play with NFSv4 and Kerberos and see lack of > > > documentation. For example, nowhere documented that access to NFSv4 > > > mount do by NFSv3 rules. I.e. I need have /etc/exports with TWO lines: > > > > > > V4: /NFS -sec=krb5i > > > /NFS -sec=krb5i > > > > > > W/o second lines I got 10020 error (for NFSv4 mount). > > > > > Well, "man exports" does try and say this (and I've reworded it several > > times), > > but it is confusing. In simple terms, the "V4:" line does not export any > > file system > > and needs to be added to whatever you export via other lines. > > As I read this: adding '/NFS 127.0.0.1' is enough and secured. This would export the mount to the local machine only (127.0.0.1 is localhost). That is true of NFSv3 as well. If you get the exports working for NFSv3 (which can be used with Kerberos, you don't need NFSv4 ot use Kerberos), then you just add the "V4: .." line to define where in the server's file system that the NFSv4 root is. > But this is wrong: not only exported, access control too. > May be for NFS guru this is trivia, but for ordinary users this is confused. > > > > What current status Kerberos support in NFS client/server? I found > > > many posts and wiki pages about lack some functionality, but also see > > > many works from you. > > > > > The main limitation (which comes from the fact that the RPCSEC_GSS > > implementation > > is version 1) is that it expects to use DES, which requires "weak > > authentication" > > to be enabled. Although parts about adding patches for initiator > > credentials no longer > > applies, this is still fairly useful. > > Hmm, I am have setup Kerberized NFS w/o "weak authentication" to be > enabled, with mounted as > 'nfsv4,intr,soft,sec=krb5i,allgssname,gssname=root'. What is requred > DES in RPCSEC_GSS? (for me as user, how I can see what broken? some > commands don't working or something else?) > Well, if the mount is working, you aren't broken. I do recommend against using "soft" or "intr" on NFSv4 mounts, because the locking stuff (which includes file opens) breaks if an RPC gets interrupted. That is on one of the man pages, maybe "man nfsv4". Usually you can't create the keytab entries unless you enable weak authentication, but if you've gotten it working, be happy;-) (DES is used for krb5p and none of the Kerberized NFS stuff works for excryption types with larger keys than 8 bytes, from what I know. I always used des-cbc-crc, because that is what all clients/servers are supposed to support. Once you move away from that, you are experimenting and it works or not.) Have fun with it, rick > > https://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > > Yes, I am talk about this. > > > Anyone willing to improve/update this is more than welcome to do so. (I, > > personally, > > haven't set up a Kerberized NFS for a couple of years and I hate fiddling > > with it. > > When something isn't working, isolating the problem can be very difficult.) > > Yes, I am already see it. > > > Good luck with it, rick > > ps: I put it on google as a wiki so anyone could update it, but I don't > > think > > anyone ever has. As I recall, anyone with a google login can update it. > > > > > Can you give some examples for kerberoized setup, with support cron > > > jobs? > > > _______________________________________________ > > > freebsd-hackers@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > To unsubscribe, send any mail to > > > "freebsd-hackers-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Mon Nov 16 22:12:58 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A0500A3194A for ; Mon, 16 Nov 2015 22:12:58 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8C98C1B23 for ; Mon, 16 Nov 2015 22:12:58 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: by mailman.ysv.freebsd.org (Postfix) id 8BB84A31949; Mon, 16 Nov 2015 22:12:58 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8B4F0A31948 for ; Mon, 16 Nov 2015 22:12:58 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 55A211B22 for ; Mon, 16 Nov 2015 22:12:58 +0000 (UTC) (envelope-from phk@phk.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.55.3]) by phk.freebsd.dk (Postfix) with ESMTP id AA07F4F418 for ; Mon, 16 Nov 2015 22:12:50 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.15.2/8.15.2) with ESMTP id tAGMCoex049035 for ; Mon, 16 Nov 2015 22:12:50 GMT (envelope-from phk@phk.freebsd.dk) To: hackers@freebsd.org Subject: Getting rid of 2*Njail sendmail processes From: Poul-Henning Kamp MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <49025.1447711969.1@critter.freebsd.dk> Date: Mon, 16 Nov 2015 22:12:50 +0000 Message-ID: <49034.1447711970@critter.freebsd.dk> X-Mailman-Approved-At: Mon, 16 Nov 2015 23:12:51 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Nov 2015 22:12:58 -0000 It has always bothered me to no end, to have to run two sendmail processes in jails, just to be able to get the cron emails. Tonight I figured out how to avoid that: In the hosts rc.conf: sendmail_enable=YES That makes sendmail listen to *:25 In the jails rc.conf: sendmail_enable=NONE Add the magic sauce: Put all jail hostnames into the hosts /etc/mail/local-host-names The quick way: jls | awk '{print $3}' > /etc/mail/local-host-names That makes the hosts sendmail treat all the jails as itself. Clean up, from the host: killall sendmail sh /etc/rc.d/sendmail start Congratulations: You just got rid of 2*Njail sendmail processes. Obviously this doesn't allow you to receive email in the jails, so it is not a general solution for all jails, but only for the very common case where the only email activity is out of the jails. Poul-Henning PS: Somebody please stick this in the relevant handbooks/docs... -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. From owner-freebsd-hackers@freebsd.org Tue Nov 17 00:07:41 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5AFD9A30FBB for ; Tue, 17 Nov 2015 00:07:41 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 473E618E6 for ; Tue, 17 Nov 2015 00:07:41 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: by mailman.ysv.freebsd.org (Postfix) id 425DDA30FBA; Tue, 17 Nov 2015 00:07:41 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 41F74A30FB9 for ; Tue, 17 Nov 2015 00:07:41 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.115.13.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8878718E5 for ; Tue, 17 Nov 2015 00:07:40 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: (qmail 17961 invoked from network); 17 Nov 2015 00:07:30 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with ESMTPS (DHE-RSA-AES128-SHA encrypted); 17 Nov 2015 00:07:30 -0000 Subject: Re: Getting rid of 2*Njail sendmail processes To: Poul-Henning Kamp , hackers@freebsd.org References: <49034.1447711970@critter.freebsd.dk> From: Dirk Engling Message-ID: <564A6FC1.8030102@erdgeist.org> Date: Tue, 17 Nov 2015 01:07:29 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <49034.1447711970@critter.freebsd.dk> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 00:07:41 -0000 On 16.11.15 23:12, Poul-Henning Kamp wrote: > It has always bothered me to no end, to have to run two sendmail > processes in jails, just to be able to get the cron emails. I usually disable sendmail alltogether and put daily_output="/var/log/daily.log" weekly_output="/var/log/weekly.log" monthly_output="/var/log/monthly.log" daily_status_security_output="/var/log/daily_status_security.log" into my periodic.conf. This is where I think it should've gone in the first place unless you're very sure you want some smtp daemon running in your jails. erdgeist From owner-freebsd-hackers@freebsd.org Tue Nov 17 02:05:36 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AA59BA30C05 for ; Tue, 17 Nov 2015 02:05:36 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 8F74F1F91 for ; Tue, 17 Nov 2015 02:05:36 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id 8BFDDA30C04; Tue, 17 Nov 2015 02:05:36 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 71A2EA30C03 for ; Tue, 17 Nov 2015 02:05:36 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: from elvis.mu.org (elvis.mu.org [IPv6:2001:470:1f05:b76::196]) by mx1.freebsd.org (Postfix) with ESMTP id 600ED1F90 for ; Tue, 17 Nov 2015 02:05:36 +0000 (UTC) (envelope-from alfred@freebsd.org) Received: from Alfreds-MacBook-Pro-2.local (unknown [IPv6:2601:645:8004:7515:6d56:aa8e:b437:27b3]) by elvis.mu.org (Postfix) with ESMTPSA id 27827345A916; Mon, 16 Nov 2015 18:05:36 -0800 (PST) Subject: Re: kqueue of a nfs mounted file not working To: Rick Macklem , Daniel Braniss References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> Cc: Konstantin Belousov , hackers@freebsd.org From: Alfred Perlstein Organization: FreeBSD Message-ID: <564A8B6F.3080009@freebsd.org> Date: Mon, 16 Nov 2015 18:05:35 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 02:05:36 -0000 On 11/16/15 6:00 AM, Rick Macklem wrote: > Daniel Braniss wrote: >>> On 15 Nov 2015, at 17:26, Konstantin Belousov wrote: >>> >>> On Sun, Nov 15, 2015 at 11:22:55AM +0200, Daniel Braniss wrote: >>>> HI, >>>> I???m writing a program to monitor a file using kqueue(2), if the file is >>>> local >>>> all is OK, but if the file is via a nfs mounted fs, it only works once. >>>> stat shows the file growing, but kevent is not triggered. >>> Does file grow due to local changes on the nfs client, or some other >>> client changes the file, while your client tries to get kevent >>> notifications ? >> it gets updated by a host which has the file as local, so yes, it gets >> updated >> by another client/host. >> > Hmm, I am not surprised that this doesn't work. The only indication to the > client that the file has changed on the server is a change in the file's > attributes when they're acquired (via a Getattr RPC or similar) from the server. > > There is a vfs operation called VFS_SYSCTL(). This isn't implemented on > the current NFS client. It was implemented on the old one, but only for > NFS locking events and I didn't understand what needed to be done, so I > didn't do it. > Kostik, do you know if there is a VFS_SYSCTL() call done when the kevent > stuff is probing for a file size change? (Or does it not probe and events > get triggered via the write syscall or ???) I took a quick look at the kevent > stuff, but admit I got lost and couldn't figure out what triggered events > being logged? > > Also, is the event for "file growing" or "file changed"? > If it is the latter, all the NFS client can do is look for a change in > the file's modify time and this is often at a resolution of 1sec., which > implies that a change within the same second as the previous one may not > be noticed. (NFSv4 has a Change attribute that is always guaranteed to > change, but that is only NFSv4.) Also, you see metadata changes as well > as data changes, at least for the NFSv4 attribute. > > rick > Hello Rick, I implemented the VFS_SYSCTL work in NFS. The goal was to allow a path to query filesystems via sysctl. This was used in OS X to provide a way to query the filesystem for "events". https://github.com/opensource-apple/xnu/blob/10.10/bsd/nfs/nfs_vfsops.c#L5188 For NFS you want to inform the user that an nfs filesystem is down, or the locking daemon is down. That was inside a GUI you can pop up a dialog box to allow the user to force-unmount or turn off locking. Image you're connected to multiple NFS shares inside of X11 or whatever windowing system you have. Then there is a network outage. You'll want to know which filesystems are not responding and why. -Alfred -Alfred From owner-freebsd-hackers@freebsd.org Tue Nov 17 03:33:05 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B7413A31CB0 for ; Tue, 17 Nov 2015 03:33:05 +0000 (UTC) (envelope-from benno@jeamland.net) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 849441C66 for ; Tue, 17 Nov 2015 03:33:05 +0000 (UTC) (envelope-from benno@jeamland.net) Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 27CFE20282 for ; Mon, 16 Nov 2015 22:32:58 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Mon, 16 Nov 2015 22:32:58 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=jeamland.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=x8XjqoGoDCbBPqed5ccRncILj9U=; b=uWks6F ZpqPd2vMTqMgMKTM0f+S2YIqQgqx8lzXJeGcdSvM6ZF9XfKNaSBzY8gjtYSiokRA bFphFMsw8Roix6PSxdNaGNVYyzssvNCSeo8+DBwYhtlEjltWVjPWUyddBQDZlw/k A3q5hqFkLQP91EsO9NbsU/aaHn/E8aesZvOjk= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=x8XjqoGoDCbBPqe d5ccRncILj9U=; b=HBrghNMd6uUIuLBjSriyS5GqITrji9wmljvybjIgi9tbT02 Mo2tRSO/O24rap7vzPVt7cFY+a3a+BN3xs4+uiwNRzMbj4WTcAzBttmzoTM1YMp3 zC8gOoH137D32r0CSE2zcTD3QHS7R64xQd2trWjL2XXWbUCrvKF/AIhhj0x4= X-Sasl-enc: moqtjO0Y/6Pp9/rh2iLA8uC5bnIDqJyMvi7IYgigqqob 1447731177 Received: from [50.95.84.177] (unknown [50.95.84.177]) by mail.messagingengine.com (Postfix) with ESMTPA id AFE37C018F9; Mon, 16 Nov 2015 22:32:57 -0500 (EST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: relaunchd: a portable clone of launchd From: Benno Rice In-Reply-To: Date: Mon, 16 Nov 2015 21:32:56 -0600 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Mark Heily X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 03:33:05 -0000 Hi Mark! Are you also looking at constructing equivalents to things like notifyd, = configd and asld? What are you using as your comms/RPC framework, if = anything? Thanks, Benno. > On Nov 15, 2015, at 18:55, Mark Heily wrote: >=20 > I've written a clone of the launchd framework found in Mac OS X [1]. > It's called "relaunchd" and I would like to some help improving it and > getting it added to the FreeBSD ports tree [2]. >=20 > Here's the source code: >=20 > https://github.com/mheily/relaunchd >=20 > One of the coolest things I've been able to do with it is to use > socket activation to launch an unmodified version of Apache inside of > a jail, pass it a socket descriptor bound to port 80 from the primary > network interface outside of the jail, and have it "just work" and > start serving web content using the pre-existing socket descriptor. > This eliminates the need to setup a cumbersome NAT and port forwarding > mechanism for each jail [3]. >=20 > This is a completely separate line of development from the work that > the NextBSD folks are doing to port the published Apple source code > for launchd and all of it's dependencies. >=20 > I'd be happy to answer questions about relaunchd, and welcome > contributions from anyone who wants to help make launchd on FreeBSD a > reality. >=20 > Regards, >=20 > - Mark >=20 > [1] https://en.wikipedia.org/wiki/Launchd > [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204240 > [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Tue Nov 17 04:13:35 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A6A66A311DA for ; Tue, 17 Nov 2015 04:13:35 +0000 (UTC) (envelope-from jim@netgate.com) Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6B4611A7B for ; Tue, 17 Nov 2015 04:13:35 +0000 (UTC) (envelope-from jim@netgate.com) Received: by oiww189 with SMTP id w189so95413915oiw.3 for ; Mon, 16 Nov 2015 20:13:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netgate.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iFEbBzFQh6kT9OMpfS1CGr2Ou/91XdbacDlvKJrBD9Y=; b=DaWIAPRH42a7rq8yYwdV7agOCQQyl1K6VBf6C/KZXyEQlPXHmW/7tY+f7/Dnu33LkQ MucLjQmT05atJ8QUAi+yJYT3C1m+p2oUJMch/cZQWCffFgi6uwdVle8kNdAUoZZlNVxF kRXVlA2dml1oBoUwemReTaze/XP8fxO1rOqN0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=iFEbBzFQh6kT9OMpfS1CGr2Ou/91XdbacDlvKJrBD9Y=; b=lUX4YA1ft3TPqfcAgg0n67mQAA7SPUUMDK8Th7n9soF+9xAcs+xMCu9rdnFCBUf00m jE/17/r63dGJByt8wFe84Bu8fh99oO+de1+MsxujDISH3lEKw/Sdhca8/tXkb4ThDOwN xguUWy5d8dvRwOFf5u4gtjG+fB8tKsOd15zt+7XaKsshU0rTWphqm5Unr4EPw4MHLPc4 kfnUO+87OdUt+1uxAKiOiaZ6HF5EnwHY2iFdo4G6QohsW/97rTTLeAUifI3vOmrxTeNB wUV1hCZEtb6/mVo2muFOdX6VnvrXhHLd38zSxUmHEfbV+88GSFNQiJm8VvYUlIV9Bc3T NIHw== X-Gm-Message-State: ALoCoQlMZ9d6vRUtZPKN2nJp5w8nryV4Q4e8fJaT84B9iCpzWWs1Au/p1nmKuHkAoF1bu+hxjFxb X-Received: by 10.202.63.130 with SMTP id m124mr15108706oia.80.1447733614517; Mon, 16 Nov 2015 20:13:34 -0800 (PST) Received: from ?IPv6:2610:160:11:33:8d95:3271:ac78:130e? ([2610:160:11:33:8d95:3271:ac78:130e]) by smtp.gmail.com with ESMTPSA id s203sm13451433ois.29.2015.11.16.20.13.31 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Nov 2015 20:13:32 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: relaunchd: a portable clone of launchd From: Jim Thompson In-Reply-To: Date: Mon, 16 Nov 2015 22:13:30 -0600 Cc: Mark Heily , freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3219A8F9-84F0-4A5B-8D22-755FD741032D@netgate.com> References: To: Benno Rice X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 04:13:35 -0000 > On Nov 16, 2015, at 9:32 PM, Benno Rice wrote: >=20 > Hi Mark! >=20 > Are you also looking at constructing equivalents to things like = notified, heh: https://github.com/mheily/stated =20 Mass rename of "notify" to =E2=80=9Cstate=E2=80=9D (22 days ago) = https://github.com/mheily/stated/commit/7d1abc85180312421505bd6cda93f82672= baacb9 > configd and asld? What are you using as your comms/RPC framework, if = anything? >=20 > Thanks, > Benno. >=20 >> On Nov 15, 2015, at 18:55, Mark Heily wrote: >>=20 >> I've written a clone of the launchd framework found in Mac OS X [1]. >> It's called "relaunchd" and I would like to some help improving it = and >> getting it added to the FreeBSD ports tree [2]. >>=20 >> Here's the source code: >>=20 >> https://github.com/mheily/relaunchd >>=20 >> One of the coolest things I've been able to do with it is to use >> socket activation to launch an unmodified version of Apache inside of >> a jail, pass it a socket descriptor bound to port 80 from the primary >> network interface outside of the jail, and have it "just work" and >> start serving web content using the pre-existing socket descriptor. >> This eliminates the need to setup a cumbersome NAT and port = forwarding >> mechanism for each jail [3]. >>=20 >> This is a completely separate line of development from the work that >> the NextBSD folks are doing to port the published Apple source code >> for launchd and all of it's dependencies. >>=20 >> I'd be happy to answer questions about relaunchd, and welcome >> contributions from anyone who wants to help make launchd on FreeBSD a >> reality. >>=20 >> Regards, >>=20 >> - Mark >>=20 >> [1] https://en.wikipedia.org/wiki/Launchd >> [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D204240 >> [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Tue Nov 17 05:18:26 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E9610A31AF8 for ; Tue, 17 Nov 2015 05:18:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CD0AC1233 for ; Tue, 17 Nov 2015 05:18:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id CB09CA31AF6; Tue, 17 Nov 2015 05:18:25 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C9A59A31AF4 for ; Tue, 17 Nov 2015 05:18:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 793011232 for ; Tue, 17 Nov 2015 05:18:25 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1ZyYeq-0008zJ-FF; Tue, 17 Nov 2015 08:18:20 +0300 Date: Tue, 17 Nov 2015 08:18:20 +0300 From: Slawa Olhovchenkov To: Rick Macklem Cc: hackers@freebsd.org Subject: Re: NFSv4 details and documentations Message-ID: <20151117051820.GD31314@zxy.spb.ru> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> <20151116141433.GA31314@zxy.spb.ru> <1489367909.88538127.1447688459383.JavaMail.zimbra@uoguelph.ca> <20151116155710.GB31314@zxy.spb.ru> <1312967974.89238067.1447714816355.JavaMail.zimbra@uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1312967974.89238067.1447714816355.JavaMail.zimbra@uoguelph.ca> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 05:18:26 -0000 On Mon, Nov 16, 2015 at 06:00:16PM -0500, Rick Macklem wrote: > Slawa Olhovchenkov wrote: > > On Mon, Nov 16, 2015 at 10:40:59AM -0500, Rick Macklem wrote: > > > > > Slawa Olhovchenkov wrote: > > > > On Mon, Nov 16, 2015 at 09:00:09AM -0500, Rick Macklem wrote: > > > > > > > > > There is a vfs operation called VFS_SYSCTL(). This isn't implemented on > > > > > the current NFS client. It was implemented on the old one, but only for > > > > > NFS locking events and I didn't understand what needed to be done, so I > > > > > didn't do it. > > > > > > > > Rick, I am try to play with NFSv4 and Kerberos and see lack of > > > > documentation. For example, nowhere documented that access to NFSv4 > > > > mount do by NFSv3 rules. I.e. I need have /etc/exports with TWO lines: > > > > > > > > V4: /NFS -sec=krb5i > > > > /NFS -sec=krb5i > > > > > > > > W/o second lines I got 10020 error (for NFSv4 mount). > > > > > > > Well, "man exports" does try and say this (and I've reworded it several > > > times), > > > but it is confusing. In simple terms, the "V4:" line does not export any > > > file system > > > and needs to be added to whatever you export via other lines. > > > > As I read this: adding '/NFS 127.0.0.1' is enough and secured. > This would export the mount to the local machine only (127.0.0.1 is localhost). > That is true of NFSv3 as well. If you get the exports working for NFSv3 (which > can be used with Kerberos, you don't need NFSv4 ot use Kerberos), then you just > add the "V4: .." line to define where in the server's file system that the NFSv4 > root is. I am like only one string 'V4: /NFS -sec=krb5i' and don't need NFSv3 at all. But I see this is imposible and documentation don't clearly describe this. Im try point this to documentation weaknes: NF3v3 permissions checks for NFSv4 mounts. > > But this is wrong: not only exported, access control too. > > May be for NFS guru this is trivia, but for ordinary users this is confused. > > > > > > What current status Kerberos support in NFS client/server? I found > > > > many posts and wiki pages about lack some functionality, but also see > > > > many works from you. > > > > > > > The main limitation (which comes from the fact that the RPCSEC_GSS > > > implementation > > > is version 1) is that it expects to use DES, which requires "weak > > > authentication" > > > to be enabled. Although parts about adding patches for initiator > > > credentials no longer > > > applies, this is still fairly useful. > > > > Hmm, I am have setup Kerberized NFS w/o "weak authentication" to be > > enabled, with mounted as > > 'nfsv4,intr,soft,sec=krb5i,allgssname,gssname=root'. What is requred > > DES in RPCSEC_GSS? (for me as user, how I can see what broken? some > > commands don't working or something else?) > > > Well, if the mount is working, you aren't broken. I do recommend against > using "soft" or "intr" on NFSv4 mounts, because the locking stuff W/o this I can got blocked client site, that can be recovered only by reboot. This is lack of unix architecture -- uniterrable open/close/disk IO. > (which includes file opens) breaks if an RPC gets interrupted. > That is on one of the man pages, maybe "man nfsv4". > > Usually you can't create the keytab entries unless you enable weak authentication, > but if you've gotten it working, be happy;-) > (DES is used for krb5p and none of the Kerberized NFS stuff works for > excryption types with larger keys than 8 bytes, from what I know. I > always used des-cbc-crc, because that is what all clients/servers are > supposed to support. Once you move away from that, you are experimenting > and it works or not.) This is worked, mount seccess and I can access NFS share from my user account. May be later I can see some problems? > Have fun with it, rick > > > > https://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > > > > Yes, I am talk about this. > > > > > Anyone willing to improve/update this is more than welcome to do so. (I, > > > personally, > > > haven't set up a Kerberized NFS for a couple of years and I hate fiddling > > > with it. > > > When something isn't working, isolating the problem can be very difficult.) > > > > Yes, I am already see it. > > > > > Good luck with it, rick > > > ps: I put it on google as a wiki so anyone could update it, but I don't > > > think > > > anyone ever has. As I recall, anyone with a google login can update it. > > > > > > > Can you give some examples for kerberoized setup, with support cron > > > > jobs? > > > > _______________________________________________ > > > > freebsd-hackers@freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > > To unsubscribe, send any mail to > > > > "freebsd-hackers-unsubscribe@freebsd.org" > > > > > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@freebsd.org Tue Nov 17 08:42:46 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39AB6A2E621 for ; Tue, 17 Nov 2015 08:42:46 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EF3F21922 for ; Tue, 17 Nov 2015 08:42:45 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-231-48.lns20.per1.internode.on.net [121.45.231.48]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id tAH8gZ2X026337 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 17 Nov 2015 00:42:38 -0800 (PST) (envelope-from julian@freebsd.org) Subject: Re: relaunchd: a portable clone of launchd To: Mark Heily , freebsd-hackers@freebsd.org References: From: Julian Elischer Message-ID: <564AE875.9010607@freebsd.org> Date: Tue, 17 Nov 2015 16:42:29 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 08:42:46 -0000 On 11/16/15 8:55 AM, Mark Heily wrote: > I've written a clone of the launchd framework found in Mac OS X [1]. > It's called "relaunchd" and I would like to some help improving it and > getting it added to the FreeBSD ports tree [2]. It would appear we have an embarrassment of riches. Someone correct me if I'm wrong but we have: * nosh * actual launchd with jkh's project * now relaunchd and of course some people like the flexibility and debugability of rc.d and are improving these. Can someone more connected with these projects please sumarise what's going on and maybe we can find a set of people with egos flexible enough that we can maybe figure out the stengths of each of these and maybe make something truely great? > > Here's the source code: > > https://github.com/mheily/relaunchd > > One of the coolest things I've been able to do with it is to use > socket activation to launch an unmodified version of Apache inside of > a jail, pass it a socket descriptor bound to port 80 from the primary > network interface outside of the jail, and have it "just work" and > start serving web content using the pre-existing socket descriptor. > This eliminates the need to setup a cumbersome NAT and port forwarding > mechanism for each jail [3]. > > This is a completely separate line of development from the work that > the NextBSD folks are doing to port the published Apple source code > for launchd and all of it's dependencies. > > I'd be happy to answer questions about relaunchd, and welcome > contributions from anyone who wants to help make launchd on FreeBSD a > reality. > > Regards, > > - Mark > > [1] https://en.wikipedia.org/wiki/Launchd > [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204240 > [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Tue Nov 17 08:56:22 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F465A2ED44 for ; Tue, 17 Nov 2015 08:56:22 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10]) by mx1.freebsd.org (Postfix) with ESMTP id CFEE113DE; Tue, 17 Nov 2015 08:56:21 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from email.rdsor.ro (ftp.rdsor.ro [193.231.238.4]) by mail.rdsor.ro (Postfix) with ESMTP id 58BAA1269F; Tue, 17 Nov 2015 10:56:19 +0200 (EET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Tue, 17 Nov 2015 10:56:26 +0200 From: dan_partelly To: Julian Elischer Cc: Mark Heily , Subject: Re: relaunchd: a portable clone of launchd In-Reply-To: <564AE875.9010607@freebsd.org> References: <564AE875.9010607@freebsd.org> Message-ID: X-Sender: dan_partelly@rdsor.ro User-Agent: RoundCube Webmail/0.4-beta X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 08:56:22 -0000 There is also svc(8) in DragonflyBSD which could be ported to FreeBSD 10.2+ thanks to new proctl(2) reaper facilities. svc(8) could form the base of a Solaris SMF like facility in the future. It doesn't do much yet, but IMO M. Dillon had the right idea when he wrote it. It is extensible, and plays well IMO with exiting init. On Tue, 17 Nov 2015 16:42:29 +0800, Julian Elischer wrote: > On 11/16/15 8:55 AM, Mark Heily wrote: >> I've written a clone of the launchd framework found in Mac OS X [1]. >> It's called "relaunchd" and I would like to some help improving it and >> getting it added to the FreeBSD ports tree [2]. > It would appear we have an embarrassment of riches. > Someone correct me if I'm wrong but we have: > * nosh > * actual launchd with jkh's project > * now relaunchd > and of course some people like the flexibility and debugability of > rc.d and are improving these. > > Can someone more connected with these projects please sumarise what's > going on and maybe we can find a set of people with egos flexible enough > that we can maybe figure out the stengths of each of these and maybe > make something truely great? > > >> >> Here's the source code: >> >> https://github.com/mheily/relaunchd >> >> One of the coolest things I've been able to do with it is to use >> socket activation to launch an unmodified version of Apache inside of >> a jail, pass it a socket descriptor bound to port 80 from the primary >> network interface outside of the jail, and have it "just work" and >> start serving web content using the pre-existing socket descriptor. >> This eliminates the need to setup a cumbersome NAT and port forwarding >> mechanism for each jail [3]. >> >> This is a completely separate line of development from the work that >> the NextBSD folks are doing to port the published Apple source code >> for launchd and all of it's dependencies. >> >> I'd be happy to answer questions about relaunchd, and welcome >> contributions from anyone who wants to help make launchd on FreeBSD a >> reality. >> >> Regards, >> >> - Mark >> >> [1] https://en.wikipedia.org/wiki/Launchd >> [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204240 >> [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to >> "freebsd-hackers-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Tue Nov 17 10:54:34 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 44BA5A2FB25 for ; Tue, 17 Nov 2015 10:54:34 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 023AE1A92; Tue, 17 Nov 2015 10:54:34 +0000 (UTC) (envelope-from outbackdingo@gmail.com) Received: by oixx65 with SMTP id x65so2553888oix.0; Tue, 17 Nov 2015 02:54:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=q0PZ4Q8Xvulf1aB6SC4zmXWOds6+aScN/53NKj6W7yg=; b=cccdUk3844393fMQWCQ+d7BvBu3G9GB0svRN+56n1iOXwdBWSAqNmieDWclIUTSmj5 wIffj2jyKHcQVICKacskB2yjL0xromoLOjct0dAdcf2ZHe/8Fxe0PPU9N95mDZFHVew0 hdseHuEiUJwXjqrT/NHfkm0DoeGPpintFURKhMtfaVfWCkyjFcd0er//u1+3545mwiqe keNAWrxSYCFjLtHT/IN6jOLx/UmZuFL6ShSBDHG3K3xjZzdHaaDuNZgwcQNpLmQwcFDk 5gBmItTecI6ZQ2PATDrIycaSAEIxOommd2wemomxVqYCyJ/IxL5PVx81LRghj8p5E8Gl MLqA== X-Received: by 10.202.187.138 with SMTP id l132mr12024228oif.49.1447757673269; Tue, 17 Nov 2015 02:54:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.202.58.2 with HTTP; Tue, 17 Nov 2015 02:53:53 -0800 (PST) In-Reply-To: <564AE875.9010607@freebsd.org> References: <564AE875.9010607@freebsd.org> From: Outback Dingo Date: Tue, 17 Nov 2015 21:53:53 +1100 Message-ID: Subject: Re: relaunchd: a portable clone of launchd To: Julian Elischer Cc: Mark Heily , freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 10:54:34 -0000 On Tue, Nov 17, 2015 at 7:42 PM, Julian Elischer wrote: > On 11/16/15 8:55 AM, Mark Heily wrote: > >> I've written a clone of the launchd framework found in Mac OS X [1]. >> It's called "relaunchd" and I would like to some help improving it and >> getting it added to the FreeBSD ports tree [2]. >> > It would appear we have an embarrassment of riches. > Someone correct me if I'm wrong but we have: > * nosh > * actual launchd with jkh's project > * now relaunchd > and of course some people like the flexibility and debugability of rc.d > and are improving these. > > Can someone more connected with these projects please sumarise what's > going on and maybe we can find a set of people with egos flexible enough > that we can maybe figure out the stengths of each of these and maybe make > something truely great? > > well... to sum it up.... originially there is launchd_xml which was completed in 2007, which i belive is the first working launchd port, then came along openrc ported and used by the archbsd, know knows as pacbsd guys, which is a side point but still a replacement. nosh appeared and seems to have some development, though also has opinions to continue into 2014, launchd is it current form with mach bits started in the trueos/freenas development plan, somewhere in mid-215 that got spun into NextBSD, then came wind of relaunchd. so there exists currently launchd_xml from 07 openrc nosh launchd/asld/notifyd and mach 2014 releaunchd and I know simply because I was connected to the original launchd_xml, and am connected to the current launchd NextBSD project as are others on the list. Hope this clears it up. > > > >> Here's the source code: >> >> https://github.com/mheily/relaunchd >> >> One of the coolest things I've been able to do with it is to use >> socket activation to launch an unmodified version of Apache inside of >> a jail, pass it a socket descriptor bound to port 80 from the primary >> network interface outside of the jail, and have it "just work" and >> start serving web content using the pre-existing socket descriptor. >> This eliminates the need to setup a cumbersome NAT and port forwarding >> mechanism for each jail [3]. >> >> This is a completely separate line of development from the work that >> the NextBSD folks are doing to port the published Apple source code >> for launchd and all of it's dependencies. >> >> I'd be happy to answer questions about relaunchd, and welcome >> contributions from anyone who wants to help make launchd on FreeBSD a >> reality. >> >> Regards, >> >> - Mark >> >> [1] https://en.wikipedia.org/wiki/Launchd >> [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204240 >> [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org >> " >> >> > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Tue Nov 17 12:53:16 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7E5DBA310A7 for ; Tue, 17 Nov 2015 12:53:16 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4E570190A for ; Tue, 17 Nov 2015 12:53:16 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: by mailman.ysv.freebsd.org (Postfix) id 4D9ADA310A6; Tue, 17 Nov 2015 12:53:16 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D2AEA310A5 for ; Tue, 17 Nov 2015 12:53:16 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id E2C3A1909 for ; Tue, 17 Nov 2015 12:53:15 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) IronPort-PHdr: 9a23:Muy+bR+IhThhu/9uRHKM819IXTAuvvDOBiVQ1KB82+4cTK2v8tzYMVDF4r011RmSDdidtqMP17CempujcFJDyK7JiGoFfp1IWk1NouQttCtkPvS4D1bmJuXhdS0wEZcKflZk+3amLRodQ56mNBXsq3G/pQQfBg/4fVIsYL+lR8iP3o/rjaibwN76XUZhvHKFe7R8LRG7/036l/I9ps9cEJs30QbDuXBSeu5blitCLFOXmAvgtI/rpMYwu3cYhvQ66sQVUbnmZ79qCvtcDS86KCY7/sDmvwLPCwyV6TwZW2QSlxNORAzE9w37WJn29SXgu+d3wyXfPcT9Tr0uQmef6bx2QkrolDsfLGx+t2XWkdBryqxBrR+rvBA5xJTbJ4ScNf57d6WaedIBWWtHUMEWWTZMD4mnY84PBuECMPxD/LX68mAKpAS3TS6oBOTxwT9FgHzxw+VuyOA+ORPWzUo7B9hIqmmC//vvM6JHa+G+z+HtxD7Aa/5TkWPn7YHDcRQspNmRWr1tfM7JyQ8kHlWW3R2rtYX5MmbNhaw2uG+B4r84WA== X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A2CAAgCVIktW/61jaINehA4sAUIGvloBDYEIBFkXCoUlSgKCAxQBAQEBAQEBAYEJgi2CBwEBAQMBAQEBICsgCxACAQgOBAYCAg0EAQETAgInAQkYDgIECAcEARwEiAUIDQOrI5BCAQEBAQEBBAEBAQEBAQEYBIEBhVOEfoQ0BwEBBVgJAYJRgUQFjhGIOIUhgm8HgiokhCGHZYoxiFICHwEBQoIOAx2BdCA0B4M5AgcXI4EHAQEB X-IronPort-AV: E=Sophos;i="5.20,307,1444708800"; d="scan'208";a="250902352" Received: from nipigon.cs.uoguelph.ca (HELO zcs1.mail.uoguelph.ca) ([131.104.99.173]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 17 Nov 2015 07:53:13 -0500 Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id C69D515F565; Tue, 17 Nov 2015 07:53:13 -0500 (EST) Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id u504fp2c1Ap4; Tue, 17 Nov 2015 07:53:12 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 83E6815F56D; Tue, 17 Nov 2015 07:53:12 -0500 (EST) X-Virus-Scanned: amavisd-new at zcs1.mail.uoguelph.ca Received: from zcs1.mail.uoguelph.ca ([127.0.0.1]) by localhost (zcs1.mail.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id dxYJf4HvcLGn; Tue, 17 Nov 2015 07:53:12 -0500 (EST) Received: from zcs1.mail.uoguelph.ca (zcs1.mail.uoguelph.ca [172.17.95.18]) by zcs1.mail.uoguelph.ca (Postfix) with ESMTP id 6791C15F565; Tue, 17 Nov 2015 07:53:12 -0500 (EST) Date: Tue, 17 Nov 2015 07:53:12 -0500 (EST) From: Rick Macklem To: Slawa Olhovchenkov Cc: hackers@freebsd.org Message-ID: <1391183052.90077969.1447764792244.JavaMail.zimbra@uoguelph.ca> In-Reply-To: <20151117051820.GD31314@zxy.spb.ru> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> <20151116141433.GA31314@zxy.spb.ru> <1489367909.88538127.1447688459383.JavaMail.zimbra@uoguelph.ca> <20151116155710.GB31314@zxy.spb.ru> <1312967974.89238067.1447714816355.JavaMail.zimbra@uoguelph.ca> <20151117051820.GD31314@zxy.spb.ru> Subject: Re: NFSv4 details and documentations MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.95.10] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - FF34 (Win)/8.0.9_GA_6191) Thread-Topic: NFSv4 details and documentations Thread-Index: tXGd0bKxhXmKH5JBXNlzWO4W6/MRWw== X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 12:53:16 -0000 Slawa Olhovchenkov wrote: > On Mon, Nov 16, 2015 at 06:00:16PM -0500, Rick Macklem wrote: > > > Slawa Olhovchenkov wrote: > > > On Mon, Nov 16, 2015 at 10:40:59AM -0500, Rick Macklem wrote: > > > > > > > Slawa Olhovchenkov wrote: > > > > > On Mon, Nov 16, 2015 at 09:00:09AM -0500, Rick Macklem wrote: > > > > > > > > > > > There is a vfs operation called VFS_SYSCTL(). This isn't > > > > > > implemented on > > > > > > the current NFS client. It was implemented on the old one, but only > > > > > > for > > > > > > NFS locking events and I didn't understand what needed to be done, > > > > > > so I > > > > > > didn't do it. > > > > > > > > > > Rick, I am try to play with NFSv4 and Kerberos and see lack of > > > > > documentation. For example, nowhere documented that access to NFSv4 > > > > > mount do by NFSv3 rules. I.e. I need have /etc/exports with TWO > > > > > lines: > > > > > > > > > > V4: /NFS -sec=krb5i > > > > > /NFS -sec=krb5i > > > > > > > > > > W/o second lines I got 10020 error (for NFSv4 mount). > > > > > > > > > Well, "man exports" does try and say this (and I've reworded it several > > > > times), > > > > but it is confusing. In simple terms, the "V4:" line does not export > > > > any > > > > file system > > > > and needs to be added to whatever you export via other lines. > > > > > > As I read this: adding '/NFS 127.0.0.1' is enough and secured. > > This would export the mount to the local machine only (127.0.0.1 is > > localhost). > > That is true of NFSv3 as well. If you get the exports working for NFSv3 > > (which > > can be used with Kerberos, you don't need NFSv4 ot use Kerberos), then you > > just > > add the "V4: .." line to define where in the server's file system that the > > NFSv4 > > root is. > > I am like only one string 'V4: /NFS -sec=krb5i' and don't need > NFSv3 at all. But I see this is imposible and documentation don't > clearly describe this. Im try point this to documentation weaknes: > NF3v3 permissions checks for NFSv4 mounts. > The only comment I will add is "They have never been NFSv3 permissions". They started out as NFSv2 permissions, because that was the only version there was. When NFSv3 was added, nothing changed, because the exports done for NFSv2 worked for NFSv3 as well. When NFSv4 came along, there was a need to add information, because NFSv4 combines the exported volumes into one directory tree and does operations that are not associated with any file, so the file system based exports don't cover those. Maybe I should have just done what Solaris did and make the NFSv4 root the root of the server's file system tree. But, instead, I added a line, so that the root could be put anywhere. (Linux put the root at the root of one of the file systems by adding a new option to an existing export line. As such, all three use the same exports for NFSv4 as NFSv3. Linux added an option to an existing export line, Solaris just put the root at the root and I added a new line.) All the information in the other export lines is still needed, so that what is exported can be limited to a subtree of the tree and, although most probably don't do so, how the files are exported can be varied from file system to file system within the tree (ro vs rw, for example). Although it does make it more complicated, some may need to do this. In general, there is always going to be "simple" vs "complicated/comprehensive". You could ever argue "complicated/comprehensive" is inevitable, because sooner or later someone needs to export in a way that isn't handled by the "simple" version and adds that. This repeats until you end up with "complex/complicated". Since FreeBSD likes backwards compatibility, redoing /etc/exports in a better was isn't an option (at least not an easy one). There was an open source altrenative to mountd called nfse which used a simpler (and better imho) way of doing exports. It never could go in the tree because it wasn't backwards compatible and the author requested it no longer be used a while back. (I am about to review a patch from someone that adds the capability for embedded whitespace in host names for /etc/exports, so it will probably be even more complicated soon.;-) All I can suggest is: 1 - Read "man exports" over and over again. After all these years, I still read it to remind myself of how it works. 2 - Any improvements w.r.t. documentation will be appreciated by others. If you post specific suggested changes to the man pages, someone can look at those for a possible commit. Otherwise there are doc people that may be able to incorporate what you write into the online documentation. (I'm not a doc guy, so I don't know the mechanisms, but I suspect posting it to a doc mailing list would be a starting point. rick > > > But this is wrong: not only exported, access control too. > > > May be for NFS guru this is trivia, but for ordinary users this is > > > confused. > > > > > > > > What current status Kerberos support in NFS client/server? I found > > > > > many posts and wiki pages about lack some functionality, but also see > > > > > many works from you. > > > > > > > > > The main limitation (which comes from the fact that the RPCSEC_GSS > > > > implementation > > > > is version 1) is that it expects to use DES, which requires "weak > > > > authentication" > > > > to be enabled. Although parts about adding patches for initiator > > > > credentials no longer > > > > applies, this is still fairly useful. > > > > > > Hmm, I am have setup Kerberized NFS w/o "weak authentication" to be > > > enabled, with mounted as > > > 'nfsv4,intr,soft,sec=krb5i,allgssname,gssname=root'. What is requred > > > DES in RPCSEC_GSS? (for me as user, how I can see what broken? some > > > commands don't working or something else?) > > > > > Well, if the mount is working, you aren't broken. I do recommend against > > using "soft" or "intr" on NFSv4 mounts, because the locking stuff > > W/o this I can got blocked client site, that can be recovered only by reboot. > This is lack of unix architecture -- uniterrable open/close/disk IO. > > > (which includes file opens) breaks if an RPC gets interrupted. > > That is on one of the man pages, maybe "man nfsv4". > > > > Usually you can't create the keytab entries unless you enable weak > > authentication, > > but if you've gotten it working, be happy;-) > > (DES is used for krb5p and none of the Kerberized NFS stuff works for > > excryption types with larger keys than 8 bytes, from what I know. I > > always used des-cbc-crc, because that is what all clients/servers are > > supposed to support. Once you move away from that, you are experimenting > > and it works or not.) > > This is worked, mount seccess and I can access NFS share from my user > account. > May be later I can see some problems? > > > Have fun with it, rick > > > > > > https://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > > > > > > Yes, I am talk about this. > > > > > > > Anyone willing to improve/update this is more than welcome to do so. > > > > (I, > > > > personally, > > > > haven't set up a Kerberized NFS for a couple of years and I hate > > > > fiddling > > > > with it. > > > > When something isn't working, isolating the problem can be very > > > > difficult.) > > > > > > Yes, I am already see it. > > > > > > > Good luck with it, rick > > > > ps: I put it on google as a wiki so anyone could update it, but I don't > > > > think > > > > anyone ever has. As I recall, anyone with a google login can update > > > > it. > > > > > > > > > Can you give some examples for kerberoized setup, with support cron > > > > > jobs? > > > > > _______________________________________________ > > > > > freebsd-hackers@freebsd.org mailing list > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > > > To unsubscribe, send any mail to > > > > > "freebsd-hackers-unsubscribe@freebsd.org" > > > > > > > > _______________________________________________ > > > freebsd-hackers@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > To unsubscribe, send any mail to > > > "freebsd-hackers-unsubscribe@freebsd.org" > > > > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Tue Nov 17 16:25:17 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A780BA31679 for ; Tue, 17 Nov 2015 16:25:17 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from mail.bsd4all.org (mail.bsd4all.org [78.47.125.12]) by mx1.freebsd.org (Postfix) with ESMTP id 6E0FB1E10 for ; Tue, 17 Nov 2015 16:25:17 +0000 (UTC) (envelope-from peter.blok@bsd4all.org) Received: from mail.bsd4all.org (localhost [127.0.0.1]) by mail.bsd4all.org (Postfix) with ESMTP id 87A442B1ED for ; Tue, 17 Nov 2015 17:25:16 +0100 (CET) X-Virus-Scanned: amavisd-new at bsd4all.org Received: from mail.bsd4all.org ([127.0.0.1]) by mail.bsd4all.org (newnas.bsd4all.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gaywOtGNHVhs for ; Tue, 17 Nov 2015 17:25:16 +0100 (CET) Received: from [192.168.1.64] (unknown [192.168.1.64]) by mail.bsd4all.org (Postfix) with ESMTPSA id 26B232B1E5 for ; Tue, 17 Nov 2015 17:25:16 +0100 (CET) From: Peter Blok Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: regression after FreeBSD-EN-15:17.libc Message-Id: Date: Tue, 17 Nov 2015 17:25:14 +0100 To: freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 16:25:17 -0000 Dear hackers, I have a strange problem with signal handling after the above errata was = implemented. It exposes itself after a slogin to a = FreeBSD-10.2-RELEASE-p7 and pressing Ctrl-C. It terminates the csh and = disconnects. This happens on two systems, one physical Octacore Atom and = on a virtual system at Hetzner. Both systems are in production and = amd64. Sources are in sync with svn. .cshrc is standard. I have tried to setup different test systems - one quad core Xeon and = one VMWare Fusion, running the exact same code, but they don=E2=80=99t = exhibit the problem. Besides the termination of the csh, I have seen corruptions in a db5 = database, after reboots. For example the sshguard database was garbled = after reboot. My suspicion is that it is signal related, caused by = reboot. This is why I am investigating further. I had a feeling it happened after the above errata change was = implemented. If I backout the changes everything works ok. If I put them = back in, it fails again. Checked the changes, but I can=E2=80=99t see anything wrong with them in = relation to the problem. Some other data points. - it doesn=E2=80=99t happen with ksh93 - it doesn=E2=80=99t happen after "exec csh -F=E2=80=9D which = doesn=E2=80=99t use vfork At one time I used ktrace and noticed the signal was delivered twice. I=E2=80=99ll make an exact clone of the Hetzner image and try to = reproduce it, but any other advice is welcome. Peter= From owner-freebsd-hackers@freebsd.org Tue Nov 17 17:09:28 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D7205A310A6 for ; Tue, 17 Nov 2015 17:09:28 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id BB0A41A70 for ; Tue, 17 Nov 2015 17:09:28 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: by mailman.ysv.freebsd.org (Postfix) id B740CA310A5; Tue, 17 Nov 2015 17:09:28 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5D71A310A4 for ; Tue, 17 Nov 2015 17:09:28 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 62C0B1A6F for ; Tue, 17 Nov 2015 17:09:28 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1Zyjkr-000O27-Ba; Tue, 17 Nov 2015 20:09:17 +0300 Date: Tue, 17 Nov 2015 20:09:17 +0300 From: Slawa Olhovchenkov To: Rick Macklem Cc: hackers@freebsd.org Subject: Re: NFSv4 details and documentations Message-ID: <20151117170917.GE31314@zxy.spb.ru> References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> <20151116141433.GA31314@zxy.spb.ru> <1489367909.88538127.1447688459383.JavaMail.zimbra@uoguelph.ca> <20151116155710.GB31314@zxy.spb.ru> <1312967974.89238067.1447714816355.JavaMail.zimbra@uoguelph.ca> <20151117051820.GD31314@zxy.spb.ru> <1391183052.90077969.1447764792244.JavaMail.zimbra@uoguelph.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1391183052.90077969.1447764792244.JavaMail.zimbra@uoguelph.ca> User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Nov 2015 17:09:29 -0000 On Tue, Nov 17, 2015 at 07:53:12AM -0500, Rick Macklem wrote: > > I am like only one string 'V4: /NFS -sec=krb5i' and don't need > > NFSv3 at all. But I see this is imposible and documentation don't > > clearly describe this. Im try point this to documentation weaknes: > > NF3v3 permissions checks for NFSv4 mounts. > > > The only comment I will add is "They have never been NFSv3 permissions". > They started out as NFSv2 permissions, because that was the only version > there was. When NFSv3 was added, nothing changed, because the exports done > for NFSv2 worked for NFSv3 as well. When NFSv4 came along, there was a need > to add information, because NFSv4 combines the exported volumes into one > directory tree and does operations that are not associated with any file, > so the file system based exports don't cover those. > > Maybe I should have just done what Solaris did and make the NFSv4 root the > root of the server's file system tree. But, instead, I added a line, so that > the root could be put anywhere. (Linux put the root at the root of one of the > file systems by adding a new option to an existing export line. As such, > all three use the same exports for NFSv4 as NFSv3. Linux added an option to > an existing export line, Solaris just put the root at the root and I added > a new line.) > > All the information in the other export lines is still needed, so that > what is exported can be limited to a subtree of the tree and, although > most probably don't do so, how the files are exported can be varied from > file system to file system within the tree (ro vs rw, for example). > Although it does make it more complicated, some may need to do this. Ahh, this is option for NFSv4! I think this sentention must be added to man page. I will be knotty senetetion about NFSv4 don't used mount in general and also possibility to disable NFSv2. I think about possibility to disable NFSv3. May bad. May be this is need to clarify in man page too? > In general, there is always going to be "simple" vs "complicated/comprehensive". > You could ever argue "complicated/comprehensive" is inevitable, because > sooner or later someone needs to export in a way that isn't handled by the > "simple" version and adds that. This repeats until you end up with > "complex/complicated". Since FreeBSD likes backwards compatibility, redoing > /etc/exports in a better was isn't an option (at least not an easy one). > There was an open source altrenative to mountd called nfse which used a > simpler (and better imho) way of doing exports. It never could go in the > tree because it wasn't backwards compatible and the author requested it > no longer be used a while back. > (I am about to review a patch from someone that adds the capability for > embedded whitespace in host names for /etc/exports, so it will probably > be even more complicated soon.;-) I am talk only about man page description. > All I can suggest is: > 1 - Read "man exports" over and over again. After all these years, I still > read it to remind myself of how it works. > 2 - Any improvements w.r.t. documentation will be appreciated by others. > If you post specific suggested changes to the man pages, someone can > look at those for a possible commit. > Otherwise there are doc people that may be able to incorporate what > you write into the online documentation. (I'm not a doc guy, so I > don't know the mechanisms, but I suspect posting it to a doc mailing > list would be a starting point. My english wery bad for suggestion. > rick > > > > > But this is wrong: not only exported, access control too. > > > > May be for NFS guru this is trivia, but for ordinary users this is > > > > confused. > > > > > > > > > > What current status Kerberos support in NFS client/server? I found > > > > > > many posts and wiki pages about lack some functionality, but also see > > > > > > many works from you. > > > > > > > > > > > The main limitation (which comes from the fact that the RPCSEC_GSS > > > > > implementation > > > > > is version 1) is that it expects to use DES, which requires "weak > > > > > authentication" > > > > > to be enabled. Although parts about adding patches for initiator > > > > > credentials no longer > > > > > applies, this is still fairly useful. > > > > > > > > Hmm, I am have setup Kerberized NFS w/o "weak authentication" to be > > > > enabled, with mounted as > > > > 'nfsv4,intr,soft,sec=krb5i,allgssname,gssname=root'. What is requred > > > > DES in RPCSEC_GSS? (for me as user, how I can see what broken? some > > > > commands don't working or something else?) > > > > > > > Well, if the mount is working, you aren't broken. I do recommend against > > > using "soft" or "intr" on NFSv4 mounts, because the locking stuff > > > > W/o this I can got blocked client site, that can be recovered only by reboot. > > This is lack of unix architecture -- uniterrable open/close/disk IO. > > > > > (which includes file opens) breaks if an RPC gets interrupted. > > > That is on one of the man pages, maybe "man nfsv4". > > > > > > Usually you can't create the keytab entries unless you enable weak > > > authentication, > > > but if you've gotten it working, be happy;-) > > > (DES is used for krb5p and none of the Kerberized NFS stuff works for > > > excryption types with larger keys than 8 bytes, from what I know. I > > > always used des-cbc-crc, because that is what all clients/servers are > > > supposed to support. Once you move away from that, you are experimenting > > > and it works or not.) > > > > This is worked, mount seccess and I can access NFS share from my user > > account. > > May be later I can see some problems? > > > > > Have fun with it, rick > > > > > > > > https://code.google.com/p/macnfsv4/wiki/FreeBSD8KerberizedNFSSetup > > > > > > > > Yes, I am talk about this. > > > > > > > > > Anyone willing to improve/update this is more than welcome to do so. > > > > > (I, > > > > > personally, > > > > > haven't set up a Kerberized NFS for a couple of years and I hate > > > > > fiddling > > > > > with it. > > > > > When something isn't working, isolating the problem can be very > > > > > difficult.) > > > > > > > > Yes, I am already see it. > > > > > > > > > Good luck with it, rick > > > > > ps: I put it on google as a wiki so anyone could update it, but I don't > > > > > think > > > > > anyone ever has. As I recall, anyone with a google login can update > > > > > it. > > > > > > > > > > > Can you give some examples for kerberoized setup, with support cron > > > > > > jobs? > > > > > > _______________________________________________ > > > > > > freebsd-hackers@freebsd.org mailing list > > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > > > > To unsubscribe, send any mail to > > > > > > "freebsd-hackers-unsubscribe@freebsd.org" > > > > > > > > > > _______________________________________________ > > > > freebsd-hackers@freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > > > To unsubscribe, send any mail to > > > > "freebsd-hackers-unsubscribe@freebsd.org" > > > > > > _______________________________________________ > > freebsd-hackers@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > > From owner-freebsd-hackers@freebsd.org Wed Nov 18 01:05:16 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3FBDFA32DB9 for ; Wed, 18 Nov 2015 01:05:16 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com [IPv6:2607:f8b0:4002:c07::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 035171EF3 for ; Wed, 18 Nov 2015 01:05:16 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: by ykdv3 with SMTP id v3so38715742ykd.0 for ; Tue, 17 Nov 2015 17:05:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=132ppOeQJJdakshpikSKwor6CP7vxuGqrjisPm/z3D8=; b=cWDNVnWvSX66ty8dYAgfS1zIl63geGqYyQ5LnQYdEeimxyxeDHvQYiw5GWKZwtyewm xJ/uD2Haueh4AsRJfckABRRsDmFoLVWFMr6k+qKN+5Yz+zTRh0Dd/uYydfEfJ3nxv5qJ PoiKi7jm6aK2Yxl8U2KGAvFiNBVguWSK8rv09sMA34tuKxJ0OY7zfYU5qxLVOanNVszW xok4vLLH9dOrDLsglabrh+mzMdFmfdKx7sG4UBVKGGFoL+5NSFOgJEcSpDRFT4m3TlHQ 0+nvU3i2PrwHG/TNr5j2t2vrIvi6xK0lJeqiu/Q7IdBzFkpXyAphFw0fG65crwa2+9Z5 Svhg== MIME-Version: 1.0 X-Received: by 10.129.89.4 with SMTP id n4mr32240432ywb.2.1447808715063; Tue, 17 Nov 2015 17:05:15 -0800 (PST) Received: by 10.37.87.68 with HTTP; Tue, 17 Nov 2015 17:05:15 -0800 (PST) Date: Tue, 17 Nov 2015 20:05:15 -0500 Message-ID: Subject: FreeBSD forum certificates wrong somehow. From: Zaphod Beeblebrox To: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 01:05:16 -0000 I realize that I have no idea who is in the wrong --- the error is rather opaque, but please follow: One of google or https everywhere (or both) directs my google searches to https when forums.freebsd.org comes up. For some reason, I can't seem to add an exception, but https is generally good... ... but firefox doesn't want to talk to https://forums.freebsd.org. So much so, in fact, it doesn't even provide the usual "add exception for https self-signed" ... it's just a dialog to report this nasty violation. ... now I realize that chrome seems to read the site just fine...but I maintain that I'd rather not use chrome ... and really someone needs to look at the problem... ... and since I don't know how to effectively complain to mozilla, I'm starting by posting here. From owner-freebsd-hackers@freebsd.org Wed Nov 18 01:28:58 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E46CCA2E2B7 for ; Wed, 18 Nov 2015 01:28:58 +0000 (UTC) (envelope-from royce.williams@gmail.com) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id ACF601985 for ; Wed, 18 Nov 2015 01:28:58 +0000 (UTC) (envelope-from royce.williams@gmail.com) Received: by obbbj7 with SMTP id bj7so21949219obb.1 for ; Tue, 17 Nov 2015 17:28:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=GpKYmYduaIesJW5AqAWrakRuTphWfwlvC5WM+mJdC/w=; b=0zOW2/8vVeXeBGf2/LTMiUizJSdVesfctP52kKWLhkK8ONct8ZEd0pKQvO0S9njgot T3F7xw/3K1vcU1d8Oil5r44zq1VR9UQN6vuma6vy/nNX30Arq19PVbKPxxs6dsdwMbHa zUFNem/hmV5rZExP+N5Go5CuHfZJ7yBH0r+MwpGEJCqpdhJIKkDQEYNSuD6dB1RNsGZl jZVb3sDHnSqfQ2QlVEj/9vQhMhgQrmImkwS1L3N9qJs1o5bN3fyeTHKzANXSV6cM3Am/ Ztta8O3tUY2H3tVdVrHZfpP/UHwuxXBIjC8JWi+0mZ6GvX5KQLX8h/HFTL4Wik4fCJB2 H48g== X-Received: by 10.60.155.33 with SMTP id vt1mr29420734oeb.27.1447810137876; Tue, 17 Nov 2015 17:28:57 -0800 (PST) MIME-Version: 1.0 Sender: royce.williams@gmail.com Received: by 10.202.81.85 with HTTP; Tue, 17 Nov 2015 17:28:28 -0800 (PST) In-Reply-To: References: From: Royce Williams Date: Tue, 17 Nov 2015 16:28:28 -0900 X-Google-Sender-Auth: vorlqRM0cSAuNliELpj4EYNwpao Message-ID: Subject: Re: FreeBSD forum certificates wrong somehow. To: Zaphod Beeblebrox Cc: FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 01:28:59 -0000 On Tue, Nov 17, 2015 at 4:05 PM, Zaphod Beeblebrox wrote: > I realize that I have no idea who is in the wrong --- the error is rather > opaque, but please follow: > > One of google or https everywhere (or both) directs my google searches to > https when forums.freebsd.org comes up. For some reason, I can't seem to > add an exception, but https is generally good... > > ... but firefox doesn't want to talk to https://forums.freebsd.org. So > much so, in fact, it doesn't even provide the usual "add exception for > https self-signed" ... it's just a dialog to report this nasty violation. > > ... now I realize that chrome seems to read the site just fine...but I > maintain that I'd rather not use chrome ... and really someone needs to > look at the problem... > > ... and since I don't know how to effectively complain to mozilla, I'm > starting by posting here. Firefox on what platform? I'm unable to replicate here, on Windows 7 or Linux (all I can reach at the moment). Qualys SSL Labs comes up clean for both IPv4 and IPv6: https://www.ssllabs.com/ssltest/analyze.html?d=forums.freebsd.org&s=149.20.54.209&latest https://www.ssllabs.com/ssltest/analyze.html?d=forums.freebsd.org&s=2001%3A4f8%3A3%3A36%3A0%3A0%3A0%3A209 Only unusual (not bad) thing that stands out from the results is that TLS 1.0 is not supported, which most sites haven't had the guts to do yet that I have seen. Do the forums have any load-balancing or DNS anycast stuff going on, or is forums.freebsd.org always 149.20.54.209 regardless of network standpoint? Firefox usually supplies an error code (of the form "err_ssl_version_or_cipher_mismatch" or similar). Anything like that showing up on your end? Royce From owner-freebsd-hackers@freebsd.org Wed Nov 18 02:07:08 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 68000A2EAB8 for ; Wed, 18 Nov 2015 02:07:08 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mx1.eichornenterprises.com (mx1.eichornenterprises.com [104.236.13.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.eichornenterprises.com", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 03E791996 for ; Wed, 18 Nov 2015 02:07:07 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mail.eichornenterprises.com (cpe-184-59-147-149.neo.res.rr.com [184.59.147.149]) by mx1.eichornenterprises.com (OpenSMTPD) with ESMTP id a31910e5; Tue, 17 Nov 2015 21:07:03 -0500 (EST) Received: by mail.eichornenterprises.com (OpenSMTPD) with ESMTPSA id f5bbd548 TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Tue, 17 Nov 2015 21:07:02 -0500 (EST) Message-ID: <1447812422.23778.17.camel@michaeleichorn.com> Subject: Re: FreeBSD forum certificates wrong somehow. From: "Michael B. Eichorn" To: Royce Williams , Zaphod Beeblebrox Cc: FreeBSD Hackers Date: Tue, 17 Nov 2015 21:07:02 -0500 In-Reply-To: References: Content-Type: multipart/signed; micalg="sha-256"; protocol="application/x-pkcs7-signature"; boundary="=-FsQD6iTox6JeT6r9RAou" X-Mailer: Evolution 3.18.1 Mime-Version: 1.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 02:07:08 -0000 --=-FsQD6iTox6JeT6r9RAou Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2015-11-17 at 16:28 -0900, Royce Williams wrote: > On Tue, Nov 17, 2015 at 4:05 PM, Zaphod Beeblebrox > wrote: > > I realize that I have no idea who is in the wrong --- the error is > > rather > > opaque, but please follow: > >=20 > > One of google or https everywhere (or both) directs my google > > searches to > > https when forums.freebsd.org comes up.=C2=A0=C2=A0For some reason, I c= an't > > seem to > > add an exception, but https is generally good... The forum does not serve http, there is a 301 redirect to https. > >=20 > > ... but firefox doesn't want to talk to https://forums.freebsd.org. > > =C2=A0=C2=A0So > > much so, in fact, it doesn't even provide the usual "add exception > > for > > https self-signed" ... it's just a dialog to report this nasty > > violation. > >=20 > > ... now I realize that chrome seems to read the site just > > fine...but I > > maintain that I'd rather not use chrome ... and really someone > > needs to > > look at the problem... > >=20 > > ... and since I don't know how to effectively complain to mozilla, > > I'm > > starting by posting here. >=20 > Firefox on what platform?=C2=A0=C2=A0I'm unable to replicate here, on Win= dows 7 > or Linux (all I can reach at the moment). More importantly which version. TLSv1.1 and 1.2 were disabled by default until version 27 (Released 20140204)[1]. And a noted below the forum requires at least 1.1 >=20 > Qualys SSL Labs comes up clean for both IPv4 and IPv6: >=20 > https://www.ssllabs.com/ssltest/analyze.html?d=3Dforums.freebsd.org&s=3D1 > 49.20.54.209&latest >=20 > https://www.ssllabs.com/ssltest/analyze.html?d=3Dforums.freebsd.org&s=3D2 > 001%3A4f8%3A3%3A36%3A0%3A0%3A0%3A209 >=20 > Only unusual (not bad) thing that stands out from the results is that > TLS 1.0 is not supported, which most sites haven't had the guts to do > yet that I have seen. >=20 > Do the forums have any load-balancing or DNS anycast stuff going on, > or is forums.freebsd.org always 149.20.54.209 regardless of network > standpoint? >=20 > Firefox usually supplies an error code (of the form > "err_ssl_version_or_cipher_mismatch" or similar).=C2=A0=C2=A0Anything lik= e that > showing up on your end? >=20 > Royce [1]=C2=A0http://website-archive.mozilla.org/www.mozilla.org/firefox_release= n otes/en-US/firefox/27.0/releasenotes/ --=-FsQD6iTox6JeT6r9RAou Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCEqAw ggYwMIIFGKADAgECAgMOXcYwDQYJKoZIhvcNAQELBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu dCBDQTAeFw0xNTA2MTMyMDI0NDZaFw0xNjA2MTQwMDM1NTBaMEgxHzAdBgNVBAMMFmlrZUBtaWNo YWVsZWljaG9ybi5jb20xJTAjBgkqhkiG9w0BCQEWFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDJVdWALPz5h2s5zUQGIJYl6Vp8FPtZNko8q/3s crCsxXJLprMaDdpnqTsmkbmEfKvsqPQE6HVOpGxVRTl/tCm+VvouW9eY9ITMigb1OnHdU13CKO0j drgeU1nHst0qxwsIofRD7nC4dakT6exnrVndlBmLrf/bLPh2qOM8YK5qKK6m33fE7AyYrwiYAWFT 3fERI7LakjaabrIoS/Y1rCdL5FaCTMOlRbZyduc8HkrgjT2JW+i4fVcKyGL5gExBJWfS3q1uGFaB ie6pYtl8lZPtvN0JSfibP003RBoLgzqHJKW91RL0qNeDjKZi/5nrlU398l9UoVvLLO3KxoPBXKCx AgMBAAGjggLcMIIC2DAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcD AgYIKwYBBQUHAwQwHQYDVR0OBBYEFJZqarc6CcrOs6eAwOgrMznk5ZWWMB8GA1UdIwQYMBaAFFNy 7ZKc4NrLAVx8fpY1TvLUuFGCMCEGA1UdEQQaMBiBFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggFM BgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDovL3d3 dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2Vy dGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBh Y2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0 YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2Ug aW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8w LTAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUH AQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIu Y2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20v MA0GCSqGSIb3DQEBCwUAA4IBAQB4K8iQw+0FRn3xEnB3vIIu2Vi4C3ZGnOMWP90FFXLrZ6uAu9AK xVCjXUVP6nAEsOopTMu769vVecdBvg0KO2i5aTDTdTLX4g9d020g4OLWW1NiynAkX8oKqJLqZ53q vHK4zP4KWPS3bSqDWVCosTMfI+H6tkg+6G3gS0HHoHTLKZhIT3z6PQZAfeofM7ed6NOdAcj0J2lP ODHzzz7Y9x4wMwYJdidorzUDVYkNIkim8ak7hK9F60NadA5w/BirFATSlzRyV0h1tl6oNisEaQcq tGvy6UoCTDhzaJ7pQValfDXJ/A47P0hNj/CX/PmkY1wQHsEJz2pbh5lqteP/fO0rMIIGMDCCBRig AwIBAgIDDl3GMA0GCSqGSIb3DQEBCwUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN MTUwNjEzMjAyNDQ2WhcNMTYwNjE0MDAzNTUwWjBIMR8wHQYDVQQDDBZpa2VAbWljaGFlbGVpY2hv cm4uY29tMSUwIwYJKoZIhvcNAQkBFhZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBIjANBgkqhkiG 9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyVXVgCz8+YdrOc1EBiCWJelafBT7WTZKPKv97HKwrMVyS6az Gg3aZ6k7JpG5hHyr7Kj0BOh1TqRsVUU5f7Qpvlb6LlvXmPSEzIoG9Tpx3VNdwijtI3a4HlNZx7Ld KscLCKH0Q+5wuHWpE+nsZ61Z3ZQZi63/2yz4dqjjPGCuaiiupt93xOwMmK8ImAFhU93xESOy2pI2 mm6yKEv2NawnS+RWgkzDpUW2cnbnPB5K4I09iVvouH1XCshi+YBMQSVn0t6tbhhWgYnuqWLZfJWT 7bzdCUn4mz9NN0QaC4M6hySlvdUS9KjXg4ymYv+Z65VN/fJfVKFbyyztysaDwVygsQIDAQABo4IC 3DCCAtgwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUF BwMEMB0GA1UdDgQWBBSWamq3OgnKzrOngMDoKzM55OWVljAfBgNVHSMEGDAWgBRTcu2SnODaywFc fH6WNU7y1LhRgjAhBgNVHREEGjAYgRZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBTAYDVR0gBIIB QzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRp b24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5n IHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBD QSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBs aWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQvMC0wK6ApoCeG JWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8w OQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9j YTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5j bGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG 9w0BAQsFAAOCAQEAeCvIkMPtBUZ98RJwd7yCLtlYuAt2RpzjFj/dBRVy62ergLvQCsVQo11FT+pw BLDqKUzLu+vb1XnHQb4NCjtouWkw03Uy1+IPXdNtIODi1ltTYspwJF/KCqiS6med6rxyuMz+Clj0 t20qg1lQqLEzHyPh+rZIPuht4EtBx6B0yymYSE98+j0GQH3qHzO3nejTnQHI9CdpTzgx888+2Pce MDMGCXYnaK81A1WJDSJIpvGpO4SvRetDWnQOcPwYqxQE0pc0cldIdbZeqDYrBGkHKrRr8ulKAkw4 c2ie6UFWpXw1yfwOOz9ITY/wl/z5pGNcEB7BCc9qW4eZarXj/3ztKzCCBjQwggQcoAMCAQICAR4w DQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0 Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1 NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1 cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7 zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8 VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+ jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQO Jebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB /wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAf BgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3dy5z dGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3Js MIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3Rh cnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29t L2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywGXLhjjF6uHLkjd02h cdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXltUfO4n4bGGdKo3awP Wp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8C h507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893 gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0 PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBm unwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2L L9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwF i2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhE puP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMYIDfzCCA3sCAQEwgZQwgYwxCzAJ BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRh bCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkg SW50ZXJtZWRpYXRlIENsaWVudCBDQQIDDl3GMA0GCWCGSAFlAwQCAQUAoIIBuzAYBgkqhkiG9w0B CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTExMTgwMjA3MDJaMC8GCSqGSIb3DQEJ BDEiBCDAG0mKLXSs7Dhte8/W4pSBesuJYneKB9sCJUjsm2AYKjCBpQYJKwYBBAGCNxAEMYGXMIGU MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJl IERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQ cmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAw5dxjCBpwYLKoZIhvcNAQkQAgsxgZeggZQw gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFBy aW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDDl3GMA0GCSqGSIb3DQEBAQUABIIBABsZg3Vj RI24qaVAZrpBJp/HK8zuCmVtP4dK3mLDpxQ673s7KsCJVpBAVeHIG6FNgx7+B+j9o2Y8bdfOCLSx qp4oL6h7cRl6uoMIuAlHk1qwVEn2V1mxfBBvGjjQOXN9xttmw/mNiG7efwsI2uCdSMJyjb/S+4ze rFfb0teqwsE5Q5QGwWA/r+lw2Uz/lYgALdx4qyaEh+hKjSwE1NQBAh95zR2UwRhpcIlRaGoPzQnS uxsGbzvkNE2ndJjFeOwgKKaLnuvf4I0AGJdAj6KxJ5UD6lwYkq/Uy5IUfdC0gRGf+hWy7oIp8U6o dvXrJEcduJNZWy+uHwXU3JNEBzAaBL4AAAAAAAA= --=-FsQD6iTox6JeT6r9RAou-- From owner-freebsd-hackers@freebsd.org Wed Nov 18 03:27:46 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83B58A2F0FB for ; Wed, 18 Nov 2015 03:27:46 +0000 (UTC) (envelope-from mark@heily.com) Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4A61D14DE for ; Wed, 18 Nov 2015 03:27:46 +0000 (UTC) (envelope-from mark@heily.com) Received: by igcto18 with SMTP id to18so29138425igc.0 for ; Tue, 17 Nov 2015 19:27:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heily-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Kmn2bcMXgVZVJBNbkEoIquGc6pp7La33ggIjX1T08Z0=; b=oybOBAIGZNpXL5F0hOP9omX8fb1LwSDSYEaAhhtnuK4YjBGCH18oNGcQPsaFLxsfDw RcRmLObGYM/xe/QgU/H8PKiQn3fw0y84FsCz+M0xeXN9mnavG8RSqPCGYNhHbIJJC4nW vIK9T07xCWhI/o6oVKfqKVTizIsfhMpOlBrj2o0lVSCJ+Msj0ASntakTJig0KfJKAsMk Yx0nNiRiDcHzW8MX5A8KJfV3oTantDfacJEmGDx129oeapHJzoWuj2e4d7YmjHOddoG1 GNjUx9MrhLvoyPK2Zy7gGSKaD/LGptb8vt6op2I89kdbWp2HG5Sk8Tv17td/c/5/x2mZ +RyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=Kmn2bcMXgVZVJBNbkEoIquGc6pp7La33ggIjX1T08Z0=; b=YH70TCps/Yuk2lm8hW8ads0GQj/v+nKHLdyITmu5TeFhJd7sAF2rlYkZvqlcQqVIoc 97KqW7oEtQweorkHD7FEo2NnzIiaY7HbeMh9clytY6u6AYkABDStoRFZv+3zECVjWTJt kES8FGAglrqQWJskEXwRIn2hFPpHG3l/EFtqUPDbwlDO7dHAchZN8EzSoj1cLX9UzfMZ 8zqmN2c33kVRp9H7Cnm26D2hMYUt7WNvRWno3cF5e2BILqQOr/bNSfRh8SxZBqWpAn5V UfsU41KvYGB0vBzAypzhKYzUm23UOSoyQa+wobEiHlUr2gyGFcbBFclwClA0fnptxifH 3aYw== X-Gm-Message-State: ALoCoQnJ3a7zofxyOUEcNjkiapp7cRMFT7dtzJca57oGw09XWlg5pYobwwfaMG3z+2SOZZhGOB4P MIME-Version: 1.0 X-Received: by 10.50.66.69 with SMTP id d5mr5153273igt.30.1447817265475; Tue, 17 Nov 2015 19:27:45 -0800 (PST) Received: by 10.79.84.199 with HTTP; Tue, 17 Nov 2015 19:27:45 -0800 (PST) X-Originating-IP: [71.70.169.30] In-Reply-To: References: Date: Tue, 17 Nov 2015 22:27:45 -0500 Message-ID: Subject: Re: relaunchd: a portable clone of launchd From: Mark Heily To: Benno Rice Cc: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 03:27:46 -0000 On Mon, Nov 16, 2015 at 10:32 PM, Benno Rice wrote: > Hi Mark! > > Are you also looking at constructing equivalents to things like notifyd, configd and asld? I've written something which blends some of the concepts behind notifyd and configd. It's called "stated" (state dee) and it's available here: https://github.com/mheily/stated I also submitted it to the ports tree here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204172 In a nutshell, it is a generic publish/subscribe mechanism for programs running on a single host to share information about their internal state and receive notifications about interesting events. I was inspired to write it by listening to Jordan Hubbard's talk about the problems that notifyd was trying to solve, such as programs that constantly call stat(2) on /etc/localtime to see if someone changed the timezone out from under them. I haven't written any of this yet, but I'm hoping that stated will present a unified view of all the important OS configuration settings, so that programs can subscribe to the ones they care about and get notified when they change. For example, similar to how people can run "sysctl -a" to see all kernel tunables, I'd like to be able to run "statectl -a" and get back some JSON like this: { hostname: "myhost", hostid: "e38a248b-8da1-11e5-b5da-382c4abedb0b", sshd.enable: "true", network.defaultrouter: "192.168.0.1", time.zone: "America/New_York", dns.fqdn: "myhost.example.com", dns.domain: "example.com", dns.nameservers: ["8.8.8.8", "8.8.4.4"], } Then, if a program cares deeply about using the most up-to-date timezone setting, it can subscribe to notifications about changes in the time.zone key, instead of constantly polling for changes to /etc/localtime. Notice that the above JSON isn't specific to FreeBSD, so programs don't need to care about operating-system details like what file in /etc is used to define the hostname. On Linux, it can be /etc/hostname; on BSD it can be /etc/rc.conf; instead, all they need to know is that the current value of the hostname is stored in a key called "hostname" > > What are you using as your comms/RPC framework, if anything? > Nothing yet, but I'm thinking of using D-Bus as the RPC mechanism for relaunchd, since a lot of open source programs are already using D-Bus. > >> On Nov 15, 2015, at 18:55, Mark Heily wrote: >> >> I've written a clone of the launchd framework found in Mac OS X [1]. >> It's called "relaunchd" and I would like to some help improving it and >> getting it added to the FreeBSD ports tree [2]. >> >> Here's the source code: >> >> https://github.com/mheily/relaunchd >> >> One of the coolest things I've been able to do with it is to use >> socket activation to launch an unmodified version of Apache inside of >> a jail, pass it a socket descriptor bound to port 80 from the primary >> network interface outside of the jail, and have it "just work" and >> start serving web content using the pre-existing socket descriptor. >> This eliminates the need to setup a cumbersome NAT and port forwarding >> mechanism for each jail [3]. >> >> This is a completely separate line of development from the work that >> the NextBSD folks are doing to port the published Apple source code >> for launchd and all of it's dependencies. >> >> I'd be happy to answer questions about relaunchd, and welcome >> contributions from anyone who wants to help make launchd on FreeBSD a >> reality. >> >> Regards, >> >> - Mark >> >> [1] https://en.wikipedia.org/wiki/Launchd >> [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204240 >> [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > From owner-freebsd-hackers@freebsd.org Wed Nov 18 07:32:28 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B2D6EA321E8 for ; Wed, 18 Nov 2015 07:32:28 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 49B40130C for ; Wed, 18 Nov 2015 07:32:28 +0000 (UTC) (envelope-from fernando.apesteguia@gmail.com) Received: by wmvv187 with SMTP id v187so263842342wmv.1 for ; Tue, 17 Nov 2015 23:32:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CYlGzTjW8yDKOAY3TQdzjAs2IVjsqw+mYMvzKsn+qrw=; b=okLH4AnbYMzCWoRczV96e9UeCDpX/HT/H7AiIyUclzYCA8t9Z8yQ3qZjqBX4cyGnlG NYZKF2jwYib2N9STPFwfjQXeNK3bi9z8h3mxs0gZhpcxlqR9yHm2RPuoaUT4DImrhkES ZQ2G6KKcNv0iXGcDw8nK9ewYahdCtVq+IbmDS8nEHrRQS5ULBs4ahavqvBNMD7zQ5dTS QrbAEVqSBlnH3ef7ZJf55mJCecUpY45w8is6Fc3mRy+ePUp0k+QwYKoZFeAbusFlGsLU 6M5fnlz8/s0cdlbSkqc5d7cK/cM1ccj7iFIYfnWtzj6RZHGv+UveZfbiHzHaNWr/AjJO rEvw== MIME-Version: 1.0 X-Received: by 10.194.202.163 with SMTP id kj3mr39749wjc.93.1447831946841; Tue, 17 Nov 2015 23:32:26 -0800 (PST) Received: by 10.27.186.138 with HTTP; Tue, 17 Nov 2015 23:32:26 -0800 (PST) In-Reply-To: References: Date: Wed, 18 Nov 2015 08:32:26 +0100 Message-ID: Subject: Re: relaunchd: a portable clone of launchd From: =?UTF-8?Q?Fernando_Apestegu=C3=ADa?= To: Mark Heily Cc: Benno Rice , FreeBSD Hackers Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 07:32:28 -0000 On Wed, Nov 18, 2015 at 4:27 AM, Mark Heily wrote: > On Mon, Nov 16, 2015 at 10:32 PM, Benno Rice wrote: >> Hi Mark! >> >> Are you also looking at constructing equivalents to things like notifyd, configd and asld? > > I've written something which blends some of the concepts behind > notifyd and configd. It's called "stated" (state dee) and it's > available here: > > https://github.com/mheily/stated > > I also submitted it to the ports tree here: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204172 > > In a nutshell, it is a generic publish/subscribe mechanism for > programs running on a single host to share information about their > internal state and receive notifications about interesting events. I > was inspired to write it by listening to Jordan Hubbard's talk about > the problems that notifyd was trying to solve, such as programs that > constantly call stat(2) on /etc/localtime to see if someone changed > the timezone out from under them. > > I haven't written any of this yet, but I'm hoping that stated will > present a unified view of all the important OS configuration > settings, so that programs can subscribe to the ones they care about > and get notified when they change. For example, similar to how people > can run "sysctl -a" to see all kernel tunables, I'd like to be able to > run "statectl -a" and get back some JSON like this: > > { > hostname: "myhost", > hostid: "e38a248b-8da1-11e5-b5da-382c4abedb0b", > sshd.enable: "true", > network.defaultrouter: "192.168.0.1", > time.zone: "America/New_York", > dns.fqdn: "myhost.example.com", > dns.domain: "example.com", > dns.nameservers: ["8.8.8.8", "8.8.4.4"], > } > > Then, if a program cares deeply about using the most up-to-date > timezone setting, it can subscribe to notifications about changes in > the time.zone key, instead of constantly polling for changes to > /etc/localtime. > > Notice that the above JSON isn't specific to FreeBSD, so programs > don't need to care about operating-system details like what file in > /etc is used to define the hostname. On Linux, it can be > /etc/hostname; on BSD it can be /etc/rc.conf; instead, all they need > to know is that the current value of the hostname is stored in a key > called "hostname" > >> >> What are you using as your comms/RPC framework, if anything? >> > > Nothing yet, but I'm thinking of using D-Bus as the RPC mechanism for > relaunchd, since a lot of open source programs are already using > D-Bus. Including systemd ;) which exposes several interfaces to DBus. If this is intended to be in base at some point of the future, it shouldn't rely on third party software from ports. Anyway, I agree that if we are going to replace a key component of the system we may want to discuss which approach is best (launchd, relaunchd, OpenRC, svc, etc...). Cheers. > >> >>> On Nov 15, 2015, at 18:55, Mark Heily wrote: >>> >>> I've written a clone of the launchd framework found in Mac OS X [1]. >>> It's called "relaunchd" and I would like to some help improving it and >>> getting it added to the FreeBSD ports tree [2]. >>> >>> Here's the source code: >>> >>> https://github.com/mheily/relaunchd >>> >>> One of the coolest things I've been able to do with it is to use >>> socket activation to launch an unmodified version of Apache inside of >>> a jail, pass it a socket descriptor bound to port 80 from the primary >>> network interface outside of the jail, and have it "just work" and >>> start serving web content using the pre-existing socket descriptor. >>> This eliminates the need to setup a cumbersome NAT and port forwarding >>> mechanism for each jail [3]. >>> >>> This is a completely separate line of development from the work that >>> the NextBSD folks are doing to port the published Apple source code >>> for launchd and all of it's dependencies. >>> >>> I'd be happy to answer questions about relaunchd, and welcome >>> contributions from anyone who wants to help make launchd on FreeBSD a >>> reality. >>> >>> Regards, >>> >>> - Mark >>> >>> [1] https://en.wikipedia.org/wiki/Launchd >>> [2] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204240 >>> [3] Example: http://kbeezie.com/freebsd-jail-single-ip/ >>> _______________________________________________ >>> freebsd-hackers@freebsd.org mailing list >>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers >>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" >> > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Wed Nov 18 07:55:59 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4450DA327A9 for ; Wed, 18 Nov 2015 07:55:59 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10]) by mx1.freebsd.org (Postfix) with ESMTP id 0D6831CA9 for ; Wed, 18 Nov 2015 07:55:58 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from [192.168.1.166] (unknown [86.125.33.32]) by mail.rdsor.ro (Postfix) with ESMTP id EAC371178D for ; Wed, 18 Nov 2015 09:55:56 +0200 (EET) From: Dan Partelly Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: libUCL / UCL as FreeBSD config question Message-Id: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> Date: Wed, 18 Nov 2015 09:55:56 +0200 To: freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 07:55:59 -0000 Hi all, is LibUCL able to read in memory a UCL key-value database , modify it in = various ways : 1. Add a new key-value pair 2. Modify the value of a value and serialise the modified database back to disk ? Or it is designed only a one way / read-only configuration mechanism ?=20= The reason Im asking is this:=20 if UCL becomes the new config mechanism of FreeBSD, does it brings any = other advantage=20 than an easy to read and humanly write format ? Would this = library/language be usable in=20 any other way in system configuration =E2=80=94 apart from autoexec.bat = way =E2=80=94> use command line tool to read key-vaule , filter it with some tool back to plain **text** and = feed it to a command line utility from FreeBSD base ?=20 Let=E2=80=99s say one writes a network config daemon to handle network = configuration, and expose network=20 configuration (like interface management, route management, DHCP = bindings and so on), which=20 exposes all this functionality to the rest of the system through IPC. = Now, let=E2=80=99s say , a simple client modifies the IP address of a certain interface, or host name or = whatever, and in process modifying the corresponding key-value in memory, in addition to sending the IOCTL to = change ip address for the interface=20 to the kernel. Is lib UCL able to serialise this change back to the file which backups = up the database ? If it is , all is dandy,=20 If it is not, is is this feature easy to implement in libUCL , without = being a hack, or libUCL design was read only=20 from start, thing which would make serialisation hard to implement = cleanly ? From owner-freebsd-hackers@freebsd.org Wed Nov 18 08:20:07 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 43E07A32F97 for ; Wed, 18 Nov 2015 08:20:07 +0000 (UTC) (envelope-from jim@netgate.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 090891953 for ; Wed, 18 Nov 2015 08:20:06 +0000 (UTC) (envelope-from jim@netgate.com) Received: by oies6 with SMTP id s6so20794879oie.1 for ; Wed, 18 Nov 2015 00:20:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netgate.com; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=DWqNvuSGVyClAYO7CjFO4MbPIDNTy5F3z5d5ZFy3lKI=; b=EcCgHiQ4RknaOOYfMbbD7M0BJBYAUOEQ1enho9lekSIQCKOFZz164oJKqDMVm57XHo oFAjrI/Akmn3mwR80A40PmabL1KgYmJqkIU6978lbGWAJoeqhemPvnJ2qR42jNzqCTZe gpd0SCQ1eNLCfO/1NsUq39+OLrttILqWraSzM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=DWqNvuSGVyClAYO7CjFO4MbPIDNTy5F3z5d5ZFy3lKI=; b=F/L10t52ibVcQNYeCxz6GgK/+EaeaqGTiNYMf3Nc4A7OLZ7ENRIK3+jnmaPzBf7/GC /N1PmfNxWFMLQM0etelX31sb4Ij1ih6QwUd3jh6/JuX2MVlO7MFMCWXD1m450BJYiKQF frF3aAua1HuES8AHEO9lyo8SDPR7bYleAvYpbP4t6zXnVbrVLqxzW7fWTZkoENQrQP80 POS56znI/55P3thn8o6KeNV50KWH7zJmoOb5lGwyOPw3ceQFYOvl/UWRQJ/CHXQQeY8f lAB4cuS9klnUm2DQ95WAlnfXeFzEZ40s+Xt5BAeyIV0+T9ISaPWmo0OhGdoSNY7+ZTuP H0pA== X-Gm-Message-State: ALoCoQnjY9zuFzkk9rRuaFJZvYTViNtrqHtt7/YyNhA24vG42U8O+E3OQsMOx0EOv8kX8VCq0nMU X-Received: by 10.202.58.198 with SMTP id h189mr103595oia.65.1447834806102; Wed, 18 Nov 2015 00:20:06 -0800 (PST) Received: from ?IPv6:2001:470:1f0f:281:5501:7d50:4b29:695c? ([2001:470:1f0f:281:5501:7d50:4b29:695c]) by smtp.gmail.com with ESMTPSA id t7sm726904obd.14.2015.11.18.00.20.05 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 Nov 2015 00:20:05 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: relaunchd: a portable clone of launchd From: Jim Thompson X-Mailer: iPhone Mail (13B143) In-Reply-To: Date: Wed, 18 Nov 2015 02:20:04 -0600 Cc: Mark Heily , FreeBSD Hackers Content-Transfer-Encoding: quoted-printable Message-Id: <8FF83C2F-D8CD-4366-A890-7EF605050456@netgate.com> References: To: =?utf-8?Q?Fernando_Apestegu=C3=ADa?= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 08:20:07 -0000 > On Nov 18, 2015, at 1:32 AM, Fernando Apestegu=C3=ADa wrote: >=20 > Anyway, I agree that if we are going to replace a key component of the > system we may want to discuss which approach is best (launchd, > relaunchd, OpenRC, svc, etc...). And thus the bike shed begins before it's built.=20= From owner-freebsd-hackers@freebsd.org Wed Nov 18 09:49:14 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id E597AA31AD9 for ; Wed, 18 Nov 2015 09:49:14 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id CBFCB175B for ; Wed, 18 Nov 2015 09:49:14 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id CACBBA31AD8; Wed, 18 Nov 2015 09:49:14 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B073DA31AD6 for ; Wed, 18 Nov 2015 09:49:14 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) by mx1.freebsd.org (Postfix) with ESMTP id 2CBB1175A; Wed, 18 Nov 2015 09:49:14 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from chamsa.cs.huji.ac.il ([132.65.80.19]) by kabab.cs.huji.ac.il with esmtp id 1ZyzMM-000PCp-1p; Wed, 18 Nov 2015 11:49:02 +0200 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: kqueue of a nfs mounted file not working From: Daniel Braniss In-Reply-To: <564A8B6F.3080009@freebsd.org> Date: Wed, 18 Nov 2015 11:49:01 +0200 Cc: Rick Macklem , Konstantin Belousov , hackers@freebsd.org Message-Id: References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> <564A8B6F.3080009@freebsd.org> To: Alfred Perlstein X-Mailer: Apple Mail (2.2104) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 09:49:15 -0000 > On 17 Nov 2015, at 04:05, Alfred Perlstein wrote: >=20 >=20 >=20 > On 11/16/15 6:00 AM, Rick Macklem wrote: >> Daniel Braniss wrote: >>>> On 15 Nov 2015, at 17:26, Konstantin Belousov = wrote: >>>>=20 >>>> On Sun, Nov 15, 2015 at 11:22:55AM +0200, Daniel Braniss wrote: >>>>> HI, >>>>> I???m writing a program to monitor a file using kqueue(2), if the = file is >>>>> local >>>>> all is OK, but if the file is via a nfs mounted fs, it only works = once. >>>>> stat shows the file growing, but kevent is not triggered. >>>> Does file grow due to local changes on the nfs client, or some = other >>>> client changes the file, while your client tries to get kevent >>>> notifications ? >>> it gets updated by a host which has the file as local, so yes, it = gets >>> updated >>> by another client/host. >>>=20 >> Hmm, I am not surprised that this doesn't work. The only indication = to the >> client that the file has changed on the server is a change in the = file's >> attributes when they're acquired (via a Getattr RPC or similar) from = the server. >>=20 >> There is a vfs operation called VFS_SYSCTL(). This isn't implemented = on >> the current NFS client. It was implemented on the old one, but only = for >> NFS locking events and I didn't understand what needed to be done, so = I >> didn't do it. >> Kostik, do you know if there is a VFS_SYSCTL() call done when the = kevent >> stuff is probing for a file size change? (Or does it not probe and = events >> get triggered via the write syscall or ???) I took a quick look at = the kevent >> stuff, but admit I got lost and couldn't figure out what triggered = events >> being logged? >>=20 >> Also, is the event for "file growing" or "file changed"? >> If it is the latter, all the NFS client can do is look for a change = in >> the file's modify time and this is often at a resolution of 1sec., = which >> implies that a change within the same second as the previous one may = not >> be noticed. (NFSv4 has a Change attribute that is always guaranteed = to >> change, but that is only NFSv4.) Also, you see metadata changes as = well >> as data changes, at least for the NFSv4 attribute. >>=20 >> rick >>=20 > Hello Rick, >=20 > I implemented the VFS_SYSCTL work in NFS. The goal was to allow a = path to query filesystems via sysctl. >=20 > This was used in OS X to provide a way to query the filesystem for = "events". >=20 > = https://github.com/opensource-apple/xnu/blob/10.10/bsd/nfs/nfs_vfsops.c#L5= 188 = >=20 > For NFS you want to inform the user that an nfs filesystem is down, or = the locking daemon is down. That was inside a GUI you can pop up a = dialog box to allow the user to force-unmount or turn off locking. >=20 > Image you're connected to multiple NFS shares inside of X11 or = whatever windowing system you have. Then there is a network outage. = You'll want to know which filesystems are not responding and why. >=20 > -Alfred >=20 > -Alfred I found a workaround, not elegant, but works, I added a timeout to the kevent instead of Null. so now it=92s working in busy wait mode instead of event driven. I you plant add themishing links, I can heliport with the testing. thanks, danny From owner-freebsd-hackers@freebsd.org Wed Nov 18 09:59:14 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 54C9CA31E65 for ; Wed, 18 Nov 2015 09:59:14 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 3962A1C60 for ; Wed, 18 Nov 2015 09:59:14 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: by mailman.ysv.freebsd.org (Postfix) id 38354A31E64; Wed, 18 Nov 2015 09:59:14 +0000 (UTC) Delivered-To: hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1F79DA31E61 for ; Wed, 18 Nov 2015 09:59:14 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from kabab.cs.huji.ac.il (kabab.cs.huji.ac.il [132.65.116.210]) by mx1.freebsd.org (Postfix) with ESMTP id 4B5501C5F; Wed, 18 Nov 2015 09:59:13 +0000 (UTC) (envelope-from danny@cs.huji.ac.il) Received: from chamsa.cs.huji.ac.il ([132.65.80.19]) by kabab.cs.huji.ac.il with esmtp id 1ZyzW9-000PKO-IN; Wed, 18 Nov 2015 11:59:09 +0200 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: kqueue of a nfs mounted file not working From: Daniel Braniss In-Reply-To: Date: Wed, 18 Nov 2015 11:59:09 +0200 Cc: Konstantin Belousov , Rick Macklem , hackers@freebsd.org Message-Id: References: <9BC3EFA2-945F-4C86-89F6-778873B58469@cs.huji.ac.il> <20151115152635.GB5854@kib.kiev.ua> <3AEC67FD-2E67-4EF9-9D46-818ABF3D8118@cs.huji.ac.il> <661673285.88370232.1447682409478.JavaMail.zimbra@uoguelph.ca> <564A8B6F.3080009@freebsd.org> To: Alfred Perlstein X-Mailer: Apple Mail (2.2104) Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 09:59:14 -0000 > On 18 Nov 2015, at 11:49, Daniel Braniss wrote: >=20 >>=20 >> On 17 Nov 2015, at 04:05, Alfred Perlstein > wrote: >>=20 >>=20 >>=20 >> On 11/16/15 6:00 AM, Rick Macklem wrote: >>> Daniel Braniss wrote: >>>>> On 15 Nov 2015, at 17:26, Konstantin Belousov = wrote: >>>>>=20 >>>>> On Sun, Nov 15, 2015 at 11:22:55AM +0200, Daniel Braniss wrote: >>>>>> HI, >>>>>> I???m writing a program to monitor a file using kqueue(2), if the = file is >>>>>> local >>>>>> all is OK, but if the file is via a nfs mounted fs, it only works = once. >>>>>> stat shows the file growing, but kevent is not triggered. >>>>> Does file grow due to local changes on the nfs client, or some = other >>>>> client changes the file, while your client tries to get kevent >>>>> notifications ? >>>> it gets updated by a host which has the file as local, so yes, it = gets >>>> updated >>>> by another client/host. >>>>=20 >>> Hmm, I am not surprised that this doesn't work. The only indication = to the >>> client that the file has changed on the server is a change in the = file's >>> attributes when they're acquired (via a Getattr RPC or similar) from = the server. >>>=20 >>> There is a vfs operation called VFS_SYSCTL(). This isn't implemented = on >>> the current NFS client. It was implemented on the old one, but only = for >>> NFS locking events and I didn't understand what needed to be done, = so I >>> didn't do it. >>> Kostik, do you know if there is a VFS_SYSCTL() call done when the = kevent >>> stuff is probing for a file size change? (Or does it not probe and = events >>> get triggered via the write syscall or ???) I took a quick look at = the kevent >>> stuff, but admit I got lost and couldn't figure out what triggered = events >>> being logged? >>>=20 >>> Also, is the event for "file growing" or "file changed"? >>> If it is the latter, all the NFS client can do is look for a change = in >>> the file's modify time and this is often at a resolution of 1sec., = which >>> implies that a change within the same second as the previous one may = not >>> be noticed. (NFSv4 has a Change attribute that is always guaranteed = to >>> change, but that is only NFSv4.) Also, you see metadata changes as = well >>> as data changes, at least for the NFSv4 attribute. >>>=20 >>> rick >>>=20 >> Hello Rick, >>=20 >> I implemented the VFS_SYSCTL work in NFS. The goal was to allow a = path to query filesystems via sysctl. >>=20 >> This was used in OS X to provide a way to query the filesystem for = "events". >>=20 >> = https://github.com/opensource-apple/xnu/blob/10.10/bsd/nfs/nfs_vfsops.c#L5= 188 = = > >>=20 >> For NFS you want to inform the user that an nfs filesystem is down, = or the locking daemon is down. That was inside a GUI you can pop up a = dialog box to allow the user to force-unmount or turn off locking. >>=20 >> Image you're connected to multiple NFS shares inside of X11 or = whatever windowing system you have. Then there is a network outage. = You'll want to know which filesystems are not responding and why. >>=20 >> -Alfred >>=20 >> -Alfred >=20 > I found a workaround, not elegant, but works, > I added a timeout to the kevent instead of Null. > so now it=92s working in busy wait mode instead of event driven. > I you plant add themishing links, I can heliport with the testing. >=20 I hate spell checkers s/themishing/the missing links/ s/heliport/help out/ > thanks, > danny >=20 >=20 > _______________________________________________ > freebsd-hackers@freebsd.org = mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers = > To unsubscribe, send any mail to = "freebsd-hackers-unsubscribe@freebsd.org = " From owner-freebsd-hackers@freebsd.org Wed Nov 18 16:10:38 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B5B65A2BE74 for ; Wed, 18 Nov 2015 16:10:38 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-qg0-x22f.google.com (mail-qg0-x22f.google.com [IPv6:2607:f8b0:400d:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C1591DC6 for ; Wed, 18 Nov 2015 16:10:38 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: by qgad10 with SMTP id d10so31207077qga.3 for ; Wed, 18 Nov 2015 08:10:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsd.com.br; s=capeta; h=date:from:to:subject:message-id:organization:mime-version :content-type:content-transfer-encoding; bh=KF6MmPEPK7RKS9BWKVNih9oMXrIBIGQQMYQZESiz+RY=; b=DJs676Hs1w1rhkx2etdM3lmS9SELmJxCMaPbpB87vOCOHxhdUuE1Ko3VyQtYvo+zsN gS7M079iTD1mSB15HNXXUrakX3TOOfJTWpS5ARQfsZmILF+EcU2rl80lda+sNLfXpzAX 3LCE7pnAuyD9e4liY7vizUkx2DT9ZnFNC1E6g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:organization :mime-version:content-type:content-transfer-encoding; bh=KF6MmPEPK7RKS9BWKVNih9oMXrIBIGQQMYQZESiz+RY=; b=m8MwDTOxEDROBXdV2kpfseml2HAAXtOxl5uKmIOdobOBHE1i0hrlxUwqOM0pNslFo5 yQ8zHU0Qn9JYb0EPr7cojuVwob6CEn7QyEXIBOd+c8Wt+ZQ2OhhawWeWlQHGBtzObXgu kREggIg8oawTLGkwXHbIRVym5sgKiuXl6TAXzXhkGHfaSXUdtCaKo0z+0GouZxzmel3E AIQBT5EN8iCs1WpKNDZBu6S+2M76N30F1VFasvewefYh8IvKBdIiM+hinwjPHF1ReEOQ deCW6Z548qSGxvbprAljVrzaSv95adfnAh23qVfnHaKOGHuyRFX34nK0pjfZaTxpRmW1 Sk3w== X-Gm-Message-State: ALoCoQlw7H4cCXjQ9jjWHbgdjQ4nwlQXfoyQ3ecOOua0j8TdqWNTLjUni1qHdKjqHqGvxIBo1ek8 X-Received: by 10.140.153.213 with SMTP id 204mr2477420qhz.30.1447863037262; Wed, 18 Nov 2015 08:10:37 -0800 (PST) Received: from Papi ([186.212.159.77]) by smtp.gmail.com with ESMTPSA id 5sm1063851qgk.10.2015.11.18.08.10.36 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 18 Nov 2015 08:10:37 -0800 (PST) Date: Wed, 18 Nov 2015 13:15:34 -0300 From: Mario Lobo To: freebsd-hackers@freebsd.org Subject: Re: FreeBSD smbfs horribly slow (update) Message-ID: <20151118131534.4a317f33@Papi> Organization: BSD X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.25; amd64-portbld-freebsd10.2) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Nov 2015 16:10:38 -0000 This an update to my previous post. Here are the test scenarios: Daemon = custom app that is accessed via tcp, and works on DBF/NTX files, either locally or on a smb share. The test involves several writing/deleting or updating DBF/NTX records operations. OBS - completion times may vary, but very little. Case 1) FBSD 10.2 running Daemon <---> Local Files Test executed on the same machine were the daemon is running. Completion: 3 seconds case 2) Daemon client <---> FBSD 10.2 running Daemon <---> Local Files (whatever OS) Test executed on the daemon client. Completion: 3-4 seconds case 3) Daemon client <---> FBSD 10.2 running Daemon <---> FBSD (Samba 4.2) (whatever OS) Test executed on the daemon client. The daemon server mounts the share via mount_smbfs Completion: 3 minutes and 50 seconds (aprox.) case 4) Daemon client <---> FBSD 10.2 running Daemon <---> LINUX (Samba 3.6) (whatever OS) Test executed on the daemon client. The daemon server mounts the share via mount_smbfs Completion: 3 minutes and 47 seconds (aprox.) case 5) Daemon client <---> CENTOS 7 running Daemon <---> LINUX (Samba 3.6) (whatever OS) Test executed on the daemon client. The daemon server mounts the share via cifs Completion: 5-6 seconds case 5) Daemon client <---> CENTOS 7 running Daemon <---> FBSD (Samba 4.2) (whatever OS) Test executed on the daemon client. The daemon server mounts the share via cifs Completion: 5-6 seconds CONCLUSION: When copying several files to the share via mount_smbfs (i.e. overwriting the DBF/NTX to rerun the test), I can get 20/40 mbps, with a few 300/400k hiccups in between, but for doing "little record" operations like those involved in DBF/NTX, the cifs client outperforms mount_smbfs client by an enormous factor. -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] "UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things." From owner-freebsd-hackers@freebsd.org Thu Nov 19 11:16:30 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 72ADEA33F32 for ; Thu, 19 Nov 2015 11:16:30 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id DC07F1D4D for ; Thu, 19 Nov 2015 11:16:29 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 12f9212a for ; Thu, 19 Nov 2015 12:09:46 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; s=mail; bh=hbahL0jO9Ysqf63YDJQj0LtGD /8=; b=UYAC9TNgJSRPyQPjKZQdK7EPgxfGs5qCO9hO+OwzNl8x3QRYwgJO9eyoa ALAuGTUAa7jN3aGNdAI8T77xV/IYRciqwt55xHUGmFg6oDqKUwBj1hWWncQuNK0f x3eiLJuO8zjdvFmtMj5dwKWNev3dkhVceyyfQ8FPB+HDpooIrs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:subject:message-id:mime-version:content-type :content-transfer-encoding; q=dns; s=mail; b=tuA8H5TUs0kaf7I+BQt J/yY2YaMlsTVxeKerow3et2JvI+J3yICPLUqAPf70DRNUPY4o1QWSz5P2VfISjfb dfVprFOLDUg08pBJ6qUyZBh/jFV86YEo83Isz4BHJOfZB6iNHtn3vFFnI0XY4yA0 3kx0V06vnRuC2tbD2wHNfYfw= Received: from atlantis.staff.bocal.org (163.5.250.153 [163.5.250.153]) by mail.blih.net (OpenSMTPD) with ESMTPSA id 41396805 TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO for ; Thu, 19 Nov 2015 12:09:46 +0100 (CET) Date: Thu, 19 Nov 2015 12:09:45 +0100 From: Emmanuel Vadot To: freebsd-hackers@freebsd.org Subject: boot1.efi and ConsoleControl on HP 840G1/G2 Message-Id: <20151119120945.71d0cb068006398d3a556559@bidouilliste.com> X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.28; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2015 11:16:30 -0000 Hello Hackers, After hours I've found why I couldn't use properly FreeBSD on my HP 840G1/G2 laptop. What is happening right now with -current is that the kernel framebuffer is garbage (https://www.bidouilliste.com/images/efi/IMG_2650.JPG). The problem is that boot1.efi calls ConsoleControl which, from my findings, is not in the UEFI specs but was only in the EDK implementation. This should not be a problem as LocateProtocol should return != EFI_SUCCESS but on my laptops (and probably others) this is not the case. After removing the ConsoleControl related lines and recompiling boot1.efi I can now boot FreeBSD. I'm pretty sure that this would not be a problem on other machine (with the patch I can still boot correctly FreeBSD on my Samsung 870Z laptop) but I would prefer that other people test it. I've opened a bug on bugzilla (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204674) if some people want to try the patch. Cheers, -- Emmanuel Vadot From owner-freebsd-hackers@freebsd.org Thu Nov 19 10:38:54 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6DF04A33A16 for ; Thu, 19 Nov 2015 10:38:54 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mx0.gentlemail.de (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 06E5A1014 for ; Thu, 19 Nov 2015 10:38:53 +0000 (UTC) (envelope-from freebsd@omnilan.de) Received: from mh0.gentlemail.de (ezra.dcm1.omnilan.net [IPv6:2a00:e10:2800::a135]) by mx0.gentlemail.de (8.14.5/8.14.5) with ESMTP id tAJAcmC7052848; Thu, 19 Nov 2015 11:38:48 +0100 (CET) (envelope-from freebsd@omnilan.de) Received: from titan.inop.mo1.omnilan.net (titan.inop.mo1.omnilan.net [IPv6:2001:a60:f0bb:1::3:1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mh0.gentlemail.de (Postfix) with ESMTPSA id BE9F99A9; Thu, 19 Nov 2015 11:38:47 +0100 (CET) Message-ID: <564DA6B7.3060705@omnilan.de> Date: Thu, 19 Nov 2015 11:38:47 +0100 From: Harry Schmalzbauer Organization: OmniLAN User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; de-DE; rv:1.9.2.8) Gecko/20100906 Lightning/1.0b2 Thunderbird/3.1.2 MIME-Version: 1.0 To: Doug Ambrisko CC: freebsd-hackers@freebsd.org Subject: Re: Fix MNAMELEN or reimplement struct statfs References: <20140415233133.GA14686@ambrisko.com> <5452600C.5030003@omnilan.de> <20141101154004.GA40398@ambrisko.com> <559FD426.3000108@omnilan.de> <20150710154654.GA71708@ambrisko.com> In-Reply-To: <20150710154654.GA71708@ambrisko.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (mx0.gentlemail.de [IPv6:2a00:e10:2800::a130]); Thu, 19 Nov 2015 11:38:48 +0100 (CET) X-Milter: Spamilter (Reciever: mx0.gentlemail.de; Sender-ip: ; Sender-helo: mh0.gentlemail.de; ) X-Mailman-Approved-At: Thu, 19 Nov 2015 12:30:36 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2015 10:38:54 -0000 Bezüglich Doug Ambrisko's Nachricht vom 10.07.2015 17:46 (localtime): > On Fri, Jul 10, 2015 at 04:18:14PM +0200, Harald Schmalzbauer wrote: > | > | > | Hello, > | > | > | > | first sorry for the missing thread references in the header, I'm not > | > | subscribed to hackers@. > | > | > | > | bdrewery@ pointed me to this discussion in response to my question to > | > | stable@ > | > | (http://lists.freebsd.org/pipermail/freebsd-fs/2014-August/019949.html) > | > | > | > | Last promising post I found: > | > | > | > | > |/ > I have a new patch at: > | > | > /|/ > http://people.freebsd.org/~ambrisko/mount_bigger_2.patch > | > | > /|/ > that I tested against head. This should be pretty close to commiting > | > | > /|/ > unless people find some issues with it. > | > | > /|/ > | > | > /|/ In sys/kern/vfs_mount.c: > | > | > /|/ + mp->mnt_path = malloc(strlen(fspath), M_MOUNT, M_WAITOK); > | > | > /|/ + strlcpy((char *)mp->mnt_path, fspath, strlen(fspath)); > | > | > /|/ > | > | > /|/ This always strips the last byte off the fspath. > | > | > /|/ > | > | > /|/ I like that this only touches the kernel, so it does not break anything > | > | > /|/ regarding mount/umount of filesystems with short paths, including > | > | > /|/ (NFS) filesystems that do not respond. > | > | > /|/ > | > | > /|/ The patch does not enlarge f_mntfromname which may be a problem for > | > | > /|/ nullfs. It is certainly a step forwards for poudriere but [ENAMETOOLONG] > | > | > /|/ errors could still occur in more extreme situations. > | > | > / > | > | > Good point on nullfs. I'll look at fixing that. To do that I'm > | > | > changing mnt_path to mnt_topath so then I can have a mnt_frompath. > | > | > I'll add nullfs to my test cases. I'll need to run through the uses > | > | > of f_mntfromname. It was pretty easy with f_mntonname since it was > | > | > only allocated in one place just used a bunch of other place. I assume > | > | > that mount root would be short. > | > | > | > | Thanks a lot so far for working hard on that problem! > | > | Is there anything newer than "mount_bigger_2.patch", which considers > | > | potential nullfs problems? > | > | I'm heavily using nullfs (without poudriere), but I'd give it a try on > | > | my rather lightly loaded local 10.1 storage box ??? almost all snapshots > | > | are useless, can't access them in case of the case; which happens > | > | frequently :-( > | > | Would I have to expect any nullfs regressions with the april > | > | (mount_bigger_2) patch?? > | > | Bez?glich Doug Ambrisko's Nachricht vom 01.11.2014 16:40 (localtime): > | > I should be able to resume working on this since things are starting to > | > slow down. It shouldn't be much more work to get it finished off to > | > put up for review. > | > | Hello Doug, > | > | I've been using your mount_bigger_2.path for some months without > | problems, but haven't done any kind of stress test. > | It just saves my soul in case I have to recover files from > | (zfs-)snapshots from time to time :-) Hello Doug, unfortunately, mount_bigger doesn't cover the length restriction for make_dev_p(), which leads to inaccessable zvols (g_dev_taste: make_dev_p() failed (gp->name=zvol/babasP0.1xSATA7k2-0/liveBACKSTOR/zfsREPL/esm-vega/P1/iscsi.redtsdatahdd500@epochp2, error=63)) … > ZFS. Kirk asked me not to continue with this since it would make > the 64 bit inode work harder and that they were going to bump up > the max of the mount point. He also mentioned that it couldn't be > merged back since it changes the kernel API. So I'm not sure > where that leaves us for now except that this works for us. I use … Do you have any news regarding this issue? I haven't followed the whole development in that area for quiet some time, but just tried 10/stable (r290995) and found this beeing still unresolved. Thanks, -Harry From owner-freebsd-hackers@freebsd.org Thu Nov 19 13:10:32 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 66A4EA31401 for ; Thu, 19 Nov 2015 13:10:32 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.blih.net", Issuer "mail.blih.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CA5221927 for ; Thu, 19 Nov 2015 13:10:31 +0000 (UTC) (envelope-from manu@bidouilliste.com) Received: from mail.blih.net (mail.blih.net [212.83.177.182]) by mail.blih.net (OpenSMTPD) with ESMTP id 29e63f36 for ; Thu, 19 Nov 2015 14:10:26 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=bidouilliste.com; h=date :from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; s=mail; bh=y3vWHYzJ1aZJ RV+WPdM+qMQz4OA=; b=rRfPpJwF9tsB8h1vSVwgmL9T75+uV/pPBUI1yPicDphC MLO43oNjSWWqvmXwNPfl0YVKo9alkxVME1wwFENz1Fhjg/+4SfhRsFfL8FKpdfAe owHgtj6EhDop9lnB1nGpZWHpEHEF2eLsJMGNY/0VCBIEuCzbLtafJfMh2CLqIZc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=bidouilliste.com; h=date :from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; q=dns; s=mail; b=L4dajW xrlbOTiZUVtWeCofmKHxBKHfDMwY8UQ7dq8dEYqGvuK2trDO0j+FZ+/tERNsGNJR w1EpdNeVcqpOp6kPY7hHDxkUC7nmY4Woe/H48Su252xtG7Y8VDndMrIhEdN/6GxN Gpt3H2MOOSbWjt8/70jGQYfmzmwZyHlbEpYFI= Received: from atlantis.staff.bocal.org (163.5.250.153 [163.5.250.153]) by mail.blih.net (OpenSMTPD) with ESMTPSA id e58091b7 TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO for ; Thu, 19 Nov 2015 14:10:26 +0100 (CET) Date: Thu, 19 Nov 2015 14:10:26 +0100 From: Emmanuel Vadot To: freebsd-hackers@freebsd.org Subject: Re: boot1.efi and ConsoleControl on HP 840G1/G2 Message-Id: <20151119141026.c1c859703fc5fcc09d18d9b5@bidouilliste.com> In-Reply-To: <20151119120945.71d0cb068006398d3a556559@bidouilliste.com> References: <20151119120945.71d0cb068006398d3a556559@bidouilliste.com> X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.28; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2015 13:10:32 -0000 On Thu, 19 Nov 2015 12:09:45 +0100 Emmanuel Vadot wrote: > > Hello Hackers, > > After hours I've found why I couldn't use properly FreeBSD on my HP 840G1/G2 laptop. > > What is happening right now with -current is that the kernel framebuffer is garbage (https://www.bidouilliste.com/images/efi/IMG_2650.JPG). > The problem is that boot1.efi calls ConsoleControl which, from my findings, is not in the UEFI specs but was only in the EDK implementation. > This should not be a problem as LocateProtocol should return != EFI_SUCCESS but on my laptops (and probably others) this is not the case. > > After removing the ConsoleControl related lines and recompiling boot1.efi I can now boot FreeBSD. > > I'm pretty sure that this would not be a problem on other machine (with the patch I can still boot correctly FreeBSD on my Samsung 870Z laptop) but I would prefer that other people test it. > > I've opened a bug on bugzilla (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204674) if some people want to try the patch. > > Cheers, > > -- > Emmanuel Vadot Replying to myself cause I've found other stuff. I looked at GRUB sources and it do what boot1.efi do (use ConsoleControl to set the Console to text mode, grub_efi_set_text_mode in grub-core/kern/efi/efi.c). The only difference that I can see between how GRUB handle the EFI console and boot1 is that grub never Reset the Console nor change the current text mode (grub-core/term/efi/console.c). So I patched again boot1.efi leaving the ConsoleControl stuff on but commented the Reset and the SetMode stuff, and this worked. This is the screen when the console is Reset : https://www.bidouilliste.com/images/efi/IMG_2649.JPG This is the screen when the console is not reseted : https://www.bidouilliste.com/images/efi/IMG_2651.JPG From loader(8) with the current boot1.efi, if I type gop list I got 4 modes but all of them are 1920x1280. If I gop set X and gop set 0 (1920x1280) (Or via loader.rc), when the kernel start the framebuffer data is correct. From loader(8) with the patched boot1.efi, if I type gop list I got the 4 correct modes. Cheers, -- Emmanuel Vadot From owner-freebsd-hackers@freebsd.org Thu Nov 19 21:58:13 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 90A88A3351C for ; Thu, 19 Nov 2015 21:58:13 +0000 (UTC) (envelope-from i.pratikdhanave@gmail.com) Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4EEFF1AAE for ; Thu, 19 Nov 2015 21:58:13 +0000 (UTC) (envelope-from i.pratikdhanave@gmail.com) Received: by ioc74 with SMTP id 74so104248856ioc.2 for ; Thu, 19 Nov 2015 13:58:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=FsYAFPSXuMJ79T8jT5Wh6PwB4D2wpmpHNs7DFXawpiA=; b=dLEzP3rEkdf6HhEJN4EtcAao+39c12cstCySNzyaV3CG2txqk7iLiKAvg0r3YGAatQ EIsDRWSHv5Vi8hx0KPo42KgRuhU7UUrufVhF1gV8K8bD9hYIx4PprmSEvy5yG3ZvajTd e6wgRfN6WobZkloRYoZkZr6gnDEh+iXEXOLykvNu3QxBWfVIkSQkkVcjrKwlf8+B0RUN Un0kuLlIdC7ZX7tP9n+IefkeJg8xfu2B23CA2Bs1bxuSaImLxTEXpiemLLHHC986b7Wm tqnJSmVMCTuy9Ikv/+NGSAEC2jO6RXdssfhCmfgcR8HQqDrw8gwhd22kloVOQof830JG XdQA== X-Received: by 10.107.32.199 with SMTP id g190mr12514153iog.55.1447970292597; Thu, 19 Nov 2015 13:58:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.7.85 with HTTP; Thu, 19 Nov 2015 13:57:53 -0800 (PST) From: pratik dhanave Date: Fri, 20 Nov 2015 03:27:53 +0530 Message-ID: Subject: Enrollment Conversation on "Memory compression and deduplication" To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2015 21:58:13 -0000 Hello Theraven, My name is Pratik Dhanave. I want to contribute to Project "Memory compression and deduplication [0] . I see this Project on FreeBSD Google Summer of Code Ideas page. How I can contribute to this Project. Where Should I get Started ? Regards, Pratik Dhanave [0] - Memory compression and deduplication From owner-freebsd-hackers@freebsd.org Thu Nov 19 22:34:25 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 5A48FA33EC5 for ; Thu, 19 Nov 2015 22:34:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 208661381 for ; Thu, 19 Nov 2015 22:34:25 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by iofh3 with SMTP id h3so105567006iof.3 for ; Thu, 19 Nov 2015 14:34:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=/7ytiey3OePzsa7bQXguGLukHl8RzjrdvpCGCogHo1w=; b=ZtPf+giLLmd+JIXyJQIhGCAMUZ2Q1kBktsZSOauXlf+Oi7tdoWsBGGdW33ds97d7e6 zyMy9mXkwYa5qHDVY0dfUs4j5x7hybsQzGrx21akjzyDhSXItItAWc9R1yQVdTh8oxAh U+Cb51aQofA0z2RsHBcr4bu9CNjt0/iiKd3DzDyAWKRml4vjczqit82mVCJ88jFgu6vi VUXDkhjq/0GXRD1Nhb1MdW2OCVKuMICWs1WlANn4DZVLQnmdJ6Kj4ZwXB1KQGfDhSz6B 6kqKDFmSeI1mlhfiw/udnhQ/KEYrJQ98wSgUCGCBvQg2KnBrIKr3tKnnmWXFlbcdsdyX k0mw== MIME-Version: 1.0 X-Received: by 10.107.162.21 with SMTP id l21mr10247734ioe.123.1447972464306; Thu, 19 Nov 2015 14:34:24 -0800 (PST) Received: by 10.36.217.196 with HTTP; Thu, 19 Nov 2015 14:34:24 -0800 (PST) In-Reply-To: References: Date: Thu, 19 Nov 2015 14:34:24 -0800 Message-ID: Subject: Re: Enrollment Conversation on "Memory compression and deduplication" From: Adrian Chadd To: pratik dhanave Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Mailman-Approved-At: Thu, 19 Nov 2015 22:55:02 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Nov 2015 22:34:25 -0000 Hi! You can start asking questions and writing code. :) What do you need? -a On 19 November 2015 at 13:57, pratik dhanave wrote: > Hello Theraven, > My name is Pratik Dhanave. I want to contribute to Project > "Memory compression and deduplication [0] > . > I see this Project on FreeBSD Google Summer of Code Ideas page. > How I can contribute to this Project. Where Should I get Started > ? > > Regards, > Pratik Dhanave > > [0] > > - Memory compression and deduplication > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Fri Nov 20 15:19:12 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7582EA348AE for ; Fri, 20 Nov 2015 15:19:12 +0000 (UTC) (envelope-from vsevolod@highsecure.ru) Received: from mail.highsecure.ru (mail6.highsecure.ru [IPv6:2a01:4f8:190:43b5::99]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 36C491B27 for ; Fri, 20 Nov 2015 15:19:11 +0000 (UTC) (envelope-from vsevolod@highsecure.ru) Received: from secret-bunker.localdomain (global-5-141.nat-2.net.cam.ac.uk [131.111.5.141]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: vsevolod@highsecure.ru) by mail.highsecure.ru (Postfix) with ESMTPSA id B035A300457; Fri, 20 Nov 2015 16:19:10 +0100 (CET) Received: from [127.0.0.1] (localhost [127.0.0.1]) by secret-bunker.localdomain (Postfix) with ESMTP id 2FD8110385C5; Fri, 20 Nov 2015 15:19:06 +0000 (GMT) Subject: Re: libUCL / UCL as FreeBSD config question To: Dan Partelly , freebsd-hackers@freebsd.org References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> From: Vsevolod Stakhov X-Enigmail-Draft-Status: N1110 Message-ID: <564F39E9.3030303@highsecure.ru> Date: Fri, 20 Nov 2015 15:19:05 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=highsecure.ru; s=dkim; t=1448032750; bh=cmVvzXyt/1bBMJ0VOXLtne0RWh3OW9jpmJBZCh5H9PU=; h=Subject:To:References:From:Message-ID:Date:MIME-Version:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=ER1xTXxAWhSn4RAf++vaALrcIz2a6WjBLf+7igTVWdq/uLA1mPxias0OuOUiqj8i8jcGOTEgyehSsFEJJ+6fZIByPBsGO29raejfccdz3SNjyH6rulPr8giXsEEdOGS9phH4CVmhN7JuZMpanM5EzH/kWz/m+qcu9W7PVQvJqfw= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 15:19:12 -0000 On 18/11/2015 07:55, Dan Partelly wrote: > Hi all, > > > is LibUCL able to read in memory a UCL key-value database , modify it in various ways : > > 1. Add a new key-value pair > 2. Modify the value of a value > > and serialise the modified database back to disk ? > > Or it is designed only a one way / read-only configuration mechanism ? > > The reason Im asking is this: > > if UCL becomes the new config mechanism of FreeBSD, does it brings any other advantage > than an easy to read and humanly write format ? Would this library/language be usable in > any other way in system configuration — apart from autoexec.bat way —> use command line tool > to read key-vaule , filter it with some tool back to plain **text** and feed it to a command line utility > from FreeBSD base ? > > Let’s say one writes a network config daemon to handle network configuration, and expose network > configuration (like interface management, route management, DHCP bindings and so on), which > exposes all this functionality to the rest of the system through IPC. Now, let’s say , a simple client > modifies the IP address of a certain interface, or host name or whatever, and in process modifying the > corresponding key-value in memory, in addition to sending the IOCTL to change ip address for the interface > to the kernel. > > Is lib UCL able to serialise this change back to the file which backups up the database ? If it is , all is dandy, > If it is not, is is this feature easy to implement in libUCL , without being a hack, or libUCL design was read only > from start, thing which would make serialisation hard to implement cleanly ? UCL supports serialization to native UCL ('config'), JSON, compacted JSON (with no lint) and YAML[1]. So far, there is also support of emitting msgpack binary format for UCL objects. >From the API perspective, libucl allows custom emitters[2], for example to output to some C string or dynamically growing string, or stdio file. There is also streamlined API that allows emitting of incomplete UCL objects (e.g. those that are too large to fit in memory). The only unimplemented feature is the format preserving emitting. We have discussed it during the recent BSDCan, but I had no time to implement any of the discussed approaches unfortunately. [1]: https://github.com/vstakhov/libucl/#emitter [2]: https://github.com/vstakhov/libucl/blob/master/doc/api.md#emitting-functions-1 -- Vsevolod Stakhov From owner-freebsd-hackers@freebsd.org Fri Nov 20 18:06:07 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3607DA34226 for ; Fri, 20 Nov 2015 18:06:07 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 130FD1B0A for ; Fri, 20 Nov 2015 18:06:06 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 73C55D0BA for ; Fri, 20 Nov 2015 18:06:00 +0000 (UTC) Subject: Re: libUCL / UCL as FreeBSD config question To: freebsd-hackers@freebsd.org References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> From: Allan Jude X-Enigmail-Draft-Status: N1110 Message-ID: <564F6118.5030702@freebsd.org> Date: Fri, 20 Nov 2015 13:06:16 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9I3qhLKErGJfVQgDCDFMlNUEprM7bsUTP" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 18:06:07 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --9I3qhLKErGJfVQgDCDFMlNUEprM7bsUTP Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2015-11-18 02:55, Dan Partelly wrote: > Hi all, >=20 >=20 > is LibUCL able to read in memory a UCL key-value database , modify it i= n various ways : >=20 > 1. Add a new key-value pair > 2. Modify the value of a value >=20 > and serialise the modified database back to disk ? >=20 > Or it is designed only a one way / read-only configuration mechanism ? = >=20 > The reason Im asking is this:=20 >=20 > if UCL becomes the new config mechanism of FreeBSD, does it brings any = other advantage=20 > than an easy to read and humanly write format ? Would this library/lang= uage be usable in=20 > any other way in system configuration =E2=80=94 apart from autoexec.bat= way =E2=80=94> use command line tool > to read key-vaule , filter it with some tool back to plain **text** an= d feed it to a command line utility > from FreeBSD base ?=20 >=20 > Let=E2=80=99s say one writes a network config daemon to handle network = configuration, and expose network=20 > configuration (like interface management, route management, DHCP bindin= gs and so on), which=20 > exposes all this functionality to the rest of the system through IPC. N= ow, let=E2=80=99s say , a simple client > modifies the IP address of a certain interface, or host name or whateve= r, and in process modifying the > corresponding key-value in memory, in addition to sending the IOCTL to= change ip address for the interface=20 > to the kernel. >=20 > Is lib UCL able to serialise this change back to the file which backups= up the database ? If it is , all is dandy,=20 > If it is not, is is this feature easy to implement in libUCL , without = being a hack, or libUCL design was read only=20 > from start, thing which would make serialisation hard to implement cl= eanly ? >=20 >=20 >=20 >=20 > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" >=20 Basically, libucl parses the configuration from the file, and creates the in-memory objects. You then have an API to manipulate the objects, like add new key-value pairs, push/pop/shift/append to arrays, merge two sets of key-value pairs with a priority system to decide who wins when there are duplicates, etc. Then, it has an emitter system to serialize those in-memory objects back out to a config file. The API is generic enough that the input and output formats could include some type of database. One flavour that I am looking to add is nvlists, as this appears to be the best way to pass data between modules.= As for the command line tool, this is the intention of uclcmd: If you have /etc/pkg/FreeBSD.conf: FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes } You can do: uclcmd get -f /etc/pkg/FreeBSD.conf FreeBSD.url and the result is: pkg+http://pkg.FreeBSD.org/${ABI}/latest And then you could do: uclcm set -f /etc/pkg/FreeBSD.conf FreeBSD.url http://pkg.mysite.com/${ABI}/custom And it would modify the configuration in place for you. Although some limitation in libucl mean that, if you have a config that has comments in it, the comments are lost, as they are not represented in the in-memory version of the object that then gets serialized for output. If you treat the config files as a database, then this is fine, but if the user expects to still hand edit them with an editor, this is a fairly big POLA violation. --=20 Allan Jude --9I3qhLKErGJfVQgDCDFMlNUEprM7bsUTP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJWT2EfAAoJEBmVNT4SmAt+KD8P/3cNpSAGVU2eCv+wdI1beLhx UFEEUw4DmRV+cyAVKJyXNKPmVCqI64PfJrd+q032noL5Nfekvcf42uwQL2kFqEIt 3+ffOhrKayb5Re3jgT7tOGIaeIA+g6POwzX/EkT5iyfGN/o+BMz+MMVGqIdGWimI SmbkLUGeCqpaQhyuclXen6X0lw9PyyTTpDFpj3vOpXJuaR3Y8lzogAoHdb1HJov0 BDCg3T1Nf1MYY4+juRY5z1B78GQfrsHkYgnF3nx5K9kwcYZqUuCk3sTGDUbICB0/ y4GIaP26tAwiMAFREKmhwMpee/ZaEer4wkKWYfnUz2yefmTH7aGvOsiIBE76WaIY Wr2Xx4QLCb5pk96vKGOurIy7xt0RXFMguO2Zqucw5MKmitQSH3uEH5enXKZvTQiJ BeNC9hv9HRVSkD6kEcmsk7mQ4LiCD0dGThUocJR5/qfWNUfeWlnoC1ZJ3ESH/b7V OiOmHqQ5pjQYgLHE4mGuH6eDmgPop2x3OuuUTD6psqcT/R53T6n/VuB3kaamFhSG DYEL1htlcdGc41gTrwDnbppaFHytSUHs8ETmaE9jlG/9knRTpApMbMPwoWZQ3sOi T/6/gQmI1KZFLUUbwdfO+7jiRyFMmzzJTfgKwN8mn1U2IqdWLOMPO7nQ1012sFgP T1fxqtOinZkUQMkzHy0I =zanl -----END PGP SIGNATURE----- --9I3qhLKErGJfVQgDCDFMlNUEprM7bsUTP-- From owner-freebsd-hackers@freebsd.org Fri Nov 20 18:17:04 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id C0935A3453C for ; Fri, 20 Nov 2015 18:17:04 +0000 (UTC) (envelope-from emorrasg@yahoo.es) Received: from nm29-vm7.bullet.mail.ir2.yahoo.com (nm29-vm7.bullet.mail.ir2.yahoo.com [212.82.97.76]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 15A83123E for ; Fri, 20 Nov 2015 18:17:03 +0000 (UTC) (envelope-from emorrasg@yahoo.es) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.es; s=s2048; t=1448043249; bh=8JABXAu/c9q72aXGS/eprCmmGErUd+6WPnRj2Mx0Yfc=; h=Date:From:To:Subject:In-Reply-To:References:From:Subject; b=aj25iMmCPHD7XJOp+ZWPw6Lz8CKprgRIwjREcf3aIYlnPuIMwV6o+8O8ynC8ZcJcpZn842zV/VtFyZr2ihrHY/Pz9dVI0q6n8q2zeUmeodrn4lpkA0YcHWKg4OThxDX7Nn9pO+eXiM8qAvea3lJdPSJoOlO93FHvSjySogBOCEhawxckcYEToWBf4/OcFhEm+YOSXdQVO+/kJWVUrFOA/DDs5YEUNDzvkU18qdW8mQ8pJlSJwyRc0euffJBgxNF3J6eNfSR94FnuEOae/ABbxecrcD0zei+at1ougixrcypeHsKW65X9YK3HfELlZXoXk2oskXN/NURa5TFOjrAXsw== Received: from [212.82.98.54] by nm29.bullet.mail.ir2.yahoo.com with NNFMP; 20 Nov 2015 18:14:09 -0000 Received: from [46.228.39.109] by tm7.bullet.mail.ir2.yahoo.com with NNFMP; 20 Nov 2015 18:14:09 -0000 Received: from [127.0.0.1] by smtp146.mail.ir2.yahoo.com with NNFMP; 20 Nov 2015 18:14:09 -0000 X-Yahoo-Newman-Id: 292418.67073.bm@smtp146.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: Sv9ByJoVM1kqKXv54HV0gpdqxPyBSy2CIWIEPQ2Ss0tEtjh SB.g44wVweXyB.yyAMeHTlWBGgxCCv_pXaOTlg18gCbODhqDAuT4lKYZHMOy QphEYV6tC7v3f8toHD7K5Dz0QTov1JyXZqj1ijLVVFwDA5_ND68XQwEbiHpT 6fzW3jdavBq1RlQns348pZH4_f4Uy94kgY4BFSoMwCPfBTQrWyLVA5si29P_ k1VfiD4it7UZ3aIpXV6gxeQ7MufUIRsCpGy4SBrf9daGLnoC21MI9hC1xsqW KLUYhTfbho4D3gC0CCmaOoYVaK7DXCfoZ2wldHD.3XWz7AmGVWerJW32wx1D F2WJQ4W31iWH.9JrseKcMn9BP_ks5tUfwhDGMmAD_DLAqbXk1IPNnwPt0of6 e3wk656zZ0PziezN9bGh.7uUfYuyKILmUgpmMFNU96pD5fq3535Qx0MG0srw mxQsT_GXesb.tAhNAtof4bZWPShF0k8Ln8kTTY68ffVD44jyxoqsXY4pX0C0 5QoFDitN6vHvzonLvVxisVphjOh2NmXKt71eyZIE- X-Yahoo-SMTP: mX392iiswBAeJNdO_s.EW62LZDJR Date: Fri, 20 Nov 2015 19:14:26 +0100 From: Eduardo Morras To: freebsd-hackers@freebsd.org Subject: Re: libUCL / UCL as FreeBSD config question Message-Id: <20151120191426.a720ca4f4e73bd867d535104@yahoo.es> In-Reply-To: <564F6118.5030702@freebsd.org> References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> <564F6118.5030702@freebsd.org> X-Mailer: Sylpheed 3.4.3 (GTK+ 2.24.28; amd64-portbld-freebsd10.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 18:17:04 -0000 On Fri, 20 Nov 2015 13:06:16 -0500 Allan Jude wrote: > Although some limitation in libucl mean that, if you have a config > that has comments in it, the comments are lost, as they are not > represented in the in-memory version of the object that then gets > serialized for output. If you treat the config files as a database, > then this is fine, but if the user expects to still hand edit them > with an editor, this is a fairly big POLA violation. POLA as in https://en.wikipedia.org/wiki/Principle_of_least_astonishment or https://en.wikipedia.org/wiki/Principle_of_least_privilege ? > > -- > Allan Jude > --- --- Eduardo Morras From owner-freebsd-hackers@freebsd.org Fri Nov 20 18:18:38 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D66E5A34604 for ; Fri, 20 Nov 2015 18:18:38 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id B30EB13DE for ; Fri, 20 Nov 2015 18:18:38 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id E02A1D1EC for ; Fri, 20 Nov 2015 18:18:37 +0000 (UTC) Subject: Re: libUCL / UCL as FreeBSD config question To: freebsd-hackers@freebsd.org References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> <564F6118.5030702@freebsd.org> <20151120191426.a720ca4f4e73bd867d535104@yahoo.es> From: Allan Jude Message-ID: <564F6411.6040208@freebsd.org> Date: Fri, 20 Nov 2015 13:18:57 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <20151120191426.a720ca4f4e73bd867d535104@yahoo.es> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="XkT97Bv6UheuM2MqNRv8p0AthIrg6AWlx" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 18:18:38 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XkT97Bv6UheuM2MqNRv8p0AthIrg6AWlx Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2015-11-20 13:14, Eduardo Morras wrote: > On Fri, 20 Nov 2015 13:06:16 -0500 > Allan Jude wrote: >=20 >> Although some limitation in libucl mean that, if you have a config >> that has comments in it, the comments are lost, as they are not >> represented in the in-memory version of the object that then gets >> serialized for output. If you treat the config files as a database, >> then this is fine, but if the user expects to still hand edit them >> with an editor, this is a fairly big POLA violation. >=20 > POLA as in https://en.wikipedia.org/wiki/Principle_of_least_astonishmen= t or https://en.wikipedia.org/wiki/Principle_of_least_privilege ? Astonishment. The user put meaningful comments in their config file, they used the utility to make a change to some value elsewhere in the config file, now their config file is written possibly in a different order, and with no comments. >=20 >> >> --=20 >> Allan Jude >> >=20 >=20 > --- --- > Eduardo Morras > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.o= rg" >=20 --=20 Allan Jude --XkT97Bv6UheuM2MqNRv8p0AthIrg6AWlx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJWT2QUAAoJEBmVNT4SmAt+oMQP/0P2XBO9IAWoym3tOsR3ONDQ ps89SMOh9dHtkc6uXUZG+abDxrvTpqHsdrQyd1maDqy5iPgxT2gdqU/6s+GcJnIT +IPmVXncPkJIInuI/4GRpC2gKw+tQzCy1Z7EBRCEbuzeObwnLwnxt58qesAy6qr1 e/qWrqIrFLvovQIO9aTqiUJSv+7aiuF4viXhHyNdS7NKfJaVbRhljijaIKM9X8XX PRvdMlF+gtcAH08y3cE9lu2aFFjiIs4Fd2Nq53kJhILW109F3cCswIXHgdcsc853 0gnP1BMprFV+rDnY17OSE41QTe1ovH7m1jZsVc/Oze3vop0cU1Znk3Fy8nNBH09H byHtD9wM04GZ93uxS9MscKixZYQx+LCOdRd0afNUvnHwJBsxJKZhHqSpFiGoMNy1 sndPwVW3yTXxkvktmwAvaEbZZvkAtWpgr7fJsP6O8A0ow5z9TA8Rprjo8YcHG0Qq g/k1H5MaNkG6j1QTIBgCZh7wPGj9GCekgvkxv2fJJaTkCdzkFKlFLZLSJ4QGMqti mS8BPQWjrUZDP0tDnYTArtOxZpHg1sJhfrrSG0gNSdRg/Fkw3zVOYQjyFiKfHf3m EQyJ9gn3L/D2ds47EIrc47gS40/mN8XdrBPdXItF37xcAVVcY2rievF9fZx+ObBE jP1t8CnPdiuVeVKJ6DP6 =IhH7 -----END PGP SIGNATURE----- --XkT97Bv6UheuM2MqNRv8p0AthIrg6AWlx-- From owner-freebsd-hackers@freebsd.org Fri Nov 20 19:36:49 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F3E04A3269F for ; Fri, 20 Nov 2015 19:36:48 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mx1.eichornenterprises.com (mx1.eichornenterprises.com [104.236.13.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.eichornenterprises.com", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8B6851D3E; Fri, 20 Nov 2015 19:36:48 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mail.eichornenterprises.com (cpe-184-59-147-149.neo.res.rr.com [184.59.147.149]) by mx1.eichornenterprises.com (OpenSMTPD) with ESMTP id 8463746f; Fri, 20 Nov 2015 14:36:38 -0500 (EST) Received: by mail.eichornenterprises.com (OpenSMTPD) with ESMTPSA id 4741874f TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Fri, 20 Nov 2015 14:36:37 -0500 (EST) Message-ID: <1448048197.2765.74.camel@michaeleichorn.com> Subject: Re: libUCL / UCL as FreeBSD config question From: "Michael B. Eichorn" To: Allan Jude , freebsd-hackers@freebsd.org Date: Fri, 20 Nov 2015 14:36:37 -0500 In-Reply-To: <564F6118.5030702@freebsd.org> References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> <564F6118.5030702@freebsd.org> Content-Type: multipart/signed; micalg="sha-256"; protocol="application/x-pkcs7-signature"; boundary="=-6uU46NjvdoseBKsrW8ur" X-Mailer: Evolution 3.18.1 Mime-Version: 1.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 19:36:49 -0000 --=-6uU46NjvdoseBKsrW8ur Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2015-11-20 at 13:06 -0500, Allan Jude wrote: >=C2=A0 > Although some limitation in libucl mean that, if you have a config > that > has comments in it, the comments are lost, as they are not > represented > in the in-memory version of the object that then gets serialized for > output. If you treat the config files as a database, then this is > fine, > but if the user expects to still hand edit them with an editor, this > is > a fairly big POLA violation. >=20 Even if someday we stop editing by hand, comments are far to useful IMHO to drop yet. Context is very important to what we do, and sometimes keys are just to cryptic. I think I see two ways to avoid the POLA violation (but I am still rather new at this so be gentle) 1) Add special keys for use in memory 'value' and 'comment' such that the file: FreeBSD: { =C2=A0 url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", =C2=A0 mirror_type: "srv", =C2=A0 signature_type: "fingerprints", =C2=A0 # A comment about fingerprints =C2=A0 # More comments =C2=A0 fingerprints: "/usr/share/keys/pkg", # an inline comment =C2=A0 enabled: yes } becomes in memory: FreeBSD: { =C2=A0 url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", =C2=A0 mirror_type: "srv", =C2=A0 signature_type: "fingerprints", =C2=A0 fingerprints: { =C2=A0 =C2=A0 value: "/usr/share/keys/pkg" =C2=A0 =C2=A0 comment: { =C2=A0 =C2=A0 =C2=A0 above: "A comment about fingerprints\nMore comments" =C2=A0 =C2=A0 =C2=A0 inline: "an inline comment" =C2=A0 =C2=A0 } =C2=A0 } =C2=A0 enabled: yes } uclcmd should just return value like: # uclcmd get -f /etc/pkg/FreeBSD.conf FreeBSD.fingerprints returns /usr/share/keys/pkg unless the comment (C?) flag is used: # uclcmd get -f -C /etc/pkg/FreeBSD.conf FreeBSD.fingerprints returns # A comment about fingerprints # More comments /usr/share/keys/pkg # an inline comment Finally if uclcmd set is used, if the session is interactive, ask the user = what to do about the existing comment. If not append a note of the change t= o the comment so that the file becomes: FreeBSD: { =C2=A0 url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", =C2=A0 mirror_type: "srv", =C2=A0 signature_type: "fingerprints", =C2=A0 # A comment about fingerprints =C2=A0 # More comments =C2=A0 ## Comments may be outdated, non-interactive edit 20151120T1400 =C2=A0 ## /usr/share/keys/pkg -> /root/keys/pkg =C2=A0 fingerprints: "/root/keys/pkg", # an inline comment =C2=A0 enabled: yes } 2) Assume everything can be commented, everything gets an extra pointer for= a potential comment string. Output all comments as the 'above' style (bonu= s: comments become predictible in style). Same uclcmd behavior as described= above. The above are just ideas (and I know next to nothing about the guts of libu= cl), but I think comments are important, if this or something else works I = am willing to help with the implementation. Regards, Ike --=-6uU46NjvdoseBKsrW8ur Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCEqAw ggYwMIIFGKADAgECAgMOXcYwDQYJKoZIhvcNAQELBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu dCBDQTAeFw0xNTA2MTMyMDI0NDZaFw0xNjA2MTQwMDM1NTBaMEgxHzAdBgNVBAMMFmlrZUBtaWNo YWVsZWljaG9ybi5jb20xJTAjBgkqhkiG9w0BCQEWFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDJVdWALPz5h2s5zUQGIJYl6Vp8FPtZNko8q/3s crCsxXJLprMaDdpnqTsmkbmEfKvsqPQE6HVOpGxVRTl/tCm+VvouW9eY9ITMigb1OnHdU13CKO0j drgeU1nHst0qxwsIofRD7nC4dakT6exnrVndlBmLrf/bLPh2qOM8YK5qKK6m33fE7AyYrwiYAWFT 3fERI7LakjaabrIoS/Y1rCdL5FaCTMOlRbZyduc8HkrgjT2JW+i4fVcKyGL5gExBJWfS3q1uGFaB ie6pYtl8lZPtvN0JSfibP003RBoLgzqHJKW91RL0qNeDjKZi/5nrlU398l9UoVvLLO3KxoPBXKCx AgMBAAGjggLcMIIC2DAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcD AgYIKwYBBQUHAwQwHQYDVR0OBBYEFJZqarc6CcrOs6eAwOgrMznk5ZWWMB8GA1UdIwQYMBaAFFNy 7ZKc4NrLAVx8fpY1TvLUuFGCMCEGA1UdEQQaMBiBFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggFM BgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDovL3d3 dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2Vy dGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBh Y2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0 YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2Ug aW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8w LTAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUH AQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIu Y2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20v MA0GCSqGSIb3DQEBCwUAA4IBAQB4K8iQw+0FRn3xEnB3vIIu2Vi4C3ZGnOMWP90FFXLrZ6uAu9AK xVCjXUVP6nAEsOopTMu769vVecdBvg0KO2i5aTDTdTLX4g9d020g4OLWW1NiynAkX8oKqJLqZ53q vHK4zP4KWPS3bSqDWVCosTMfI+H6tkg+6G3gS0HHoHTLKZhIT3z6PQZAfeofM7ed6NOdAcj0J2lP ODHzzz7Y9x4wMwYJdidorzUDVYkNIkim8ak7hK9F60NadA5w/BirFATSlzRyV0h1tl6oNisEaQcq tGvy6UoCTDhzaJ7pQValfDXJ/A47P0hNj/CX/PmkY1wQHsEJz2pbh5lqteP/fO0rMIIGMDCCBRig AwIBAgIDDl3GMA0GCSqGSIb3DQEBCwUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN MTUwNjEzMjAyNDQ2WhcNMTYwNjE0MDAzNTUwWjBIMR8wHQYDVQQDDBZpa2VAbWljaGFlbGVpY2hv cm4uY29tMSUwIwYJKoZIhvcNAQkBFhZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBIjANBgkqhkiG 9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyVXVgCz8+YdrOc1EBiCWJelafBT7WTZKPKv97HKwrMVyS6az Gg3aZ6k7JpG5hHyr7Kj0BOh1TqRsVUU5f7Qpvlb6LlvXmPSEzIoG9Tpx3VNdwijtI3a4HlNZx7Ld KscLCKH0Q+5wuHWpE+nsZ61Z3ZQZi63/2yz4dqjjPGCuaiiupt93xOwMmK8ImAFhU93xESOy2pI2 mm6yKEv2NawnS+RWgkzDpUW2cnbnPB5K4I09iVvouH1XCshi+YBMQSVn0t6tbhhWgYnuqWLZfJWT 7bzdCUn4mz9NN0QaC4M6hySlvdUS9KjXg4ymYv+Z65VN/fJfVKFbyyztysaDwVygsQIDAQABo4IC 3DCCAtgwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUF BwMEMB0GA1UdDgQWBBSWamq3OgnKzrOngMDoKzM55OWVljAfBgNVHSMEGDAWgBRTcu2SnODaywFc fH6WNU7y1LhRgjAhBgNVHREEGjAYgRZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBTAYDVR0gBIIB QzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRp b24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5n IHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBD QSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBs aWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQvMC0wK6ApoCeG JWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8w OQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9j YTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5j bGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG 9w0BAQsFAAOCAQEAeCvIkMPtBUZ98RJwd7yCLtlYuAt2RpzjFj/dBRVy62ergLvQCsVQo11FT+pw BLDqKUzLu+vb1XnHQb4NCjtouWkw03Uy1+IPXdNtIODi1ltTYspwJF/KCqiS6med6rxyuMz+Clj0 t20qg1lQqLEzHyPh+rZIPuht4EtBx6B0yymYSE98+j0GQH3qHzO3nejTnQHI9CdpTzgx888+2Pce MDMGCXYnaK81A1WJDSJIpvGpO4SvRetDWnQOcPwYqxQE0pc0cldIdbZeqDYrBGkHKrRr8ulKAkw4 c2ie6UFWpXw1yfwOOz9ITY/wl/z5pGNcEB7BCc9qW4eZarXj/3ztKzCCBjQwggQcoAMCAQICAR4w DQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0 Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1 NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1 cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7 zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8 VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+ jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQO Jebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB /wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAf BgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3dy5z dGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3Js MIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3Rh cnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29t L2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywGXLhjjF6uHLkjd02h cdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXltUfO4n4bGGdKo3awP Wp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8C h507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893 gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0 PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBm unwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2L L9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwF i2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhE puP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMYIDfzCCA3sCAQEwgZQwgYwxCzAJ BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRh bCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkg SW50ZXJtZWRpYXRlIENsaWVudCBDQQIDDl3GMA0GCWCGSAFlAwQCAQUAoIIBuzAYBgkqhkiG9w0B CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTExMjAxOTM2MzdaMC8GCSqGSIb3DQEJ BDEiBCDEg2U2Z6JHX6yQ+mQGp2YSvSYYc2fXmqxpjpwLJLoeTzCBpQYJKwYBBAGCNxAEMYGXMIGU MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJl IERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQ cmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAw5dxjCBpwYLKoZIhvcNAQkQAgsxgZeggZQw gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFBy aW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDDl3GMA0GCSqGSIb3DQEBAQUABIIBAENuG0v1 Qc1KBIgaJkinOnGV/Sel0LofUJWPO+QOwKaCdl9Pp1qpzIS/ajh44FsXf89H6VswY+gfEGhP8pXv r3ajJ1ZNvfp2LalidQdDiXXzpvPsYGevWTMOBTGFTtiRHKevqHTRxLZ2vNzodSIF7wOeTgBlchSw VEnc0jiXNSfK9XvZpkVYbnke4wV8XurGwJFcBe0+Ys9bBSTi0s8TRw/mhJqTf2AgiLDfyhvmVlqj 87ntqH3G+KTb4bFroGnVTGgzm/TlQ52NcXb7edZ8bWMz/HJ41UxHKwdccgp6MNGUUkpYArp+ijF3 3WyIvexlcPf1BdIp2/1AntG0Nn7Ke7kAAAAAAAA= --=-6uU46NjvdoseBKsrW8ur-- From owner-freebsd-hackers@freebsd.org Fri Nov 20 19:39:57 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 39073A3270F for ; Fri, 20 Nov 2015 19:39:57 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 12BBB1E6E for ; Fri, 20 Nov 2015 19:39:56 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id F2311D3B7 for ; Fri, 20 Nov 2015 19:39:55 +0000 (UTC) Subject: Re: libUCL / UCL as FreeBSD config question To: freebsd-hackers@freebsd.org References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> <564F6118.5030702@freebsd.org> <1448048197.2765.74.camel@michaeleichorn.com> From: Allan Jude X-Enigmail-Draft-Status: N1110 Message-ID: <564F771F.4060408@freebsd.org> Date: Fri, 20 Nov 2015 14:40:15 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <1448048197.2765.74.camel@michaeleichorn.com> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="mCnnVqGiXtb36sxo7S1sdISFmMWKrhVGT" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 19:39:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --mCnnVqGiXtb36sxo7S1sdISFmMWKrhVGT Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2015-11-20 14:36, Michael B. Eichorn wrote: > On Fri, 2015-11-20 at 13:06 -0500, Allan Jude wrote: >> =20 >> Although some limitation in libucl mean that, if you have a config >> that >> has comments in it, the comments are lost, as they are not >> represented >> in the in-memory version of the object that then gets serialized for >> output. If you treat the config files as a database, then this is >> fine, >> but if the user expects to still hand edit them with an editor, this >> is >> a fairly big POLA violation. >> >=20 > Even if someday we stop editing by hand, comments are far to useful > IMHO to drop yet. Context is very important to what we do, and > sometimes keys are just to cryptic. >=20 > I think I see two ways to avoid the POLA violation (but I am still > rather new at this so be gentle) >=20 > 1) Add special keys for use in memory 'value' and 'comment' such that > the file: >=20 > FreeBSD: { > url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", > mirror_type: "srv", > signature_type: "fingerprints", > # A comment about fingerprints > # More comments > fingerprints: "/usr/share/keys/pkg", # an inline comment > enabled: yes > } >=20 > becomes in memory: >=20 > FreeBSD: { > url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", > =20 > mirror_type: "srv", > signature_type: "fingerprints", > fingerprints: { > =20 > value: "/usr/share/keys/pkg" > comment: { > above: "A comment > about fingerprints\nMore comments" > inline: "an inline comment" > =20 > } > } > enabled: yes > } >=20 > uclcmd should just return value like: >=20 > # uclcmd get -f /etc/pkg/FreeBSD.conf FreeBSD.fingerprints >=20 > returns > /usr/share/keys/pkg >=20 > unless the comment (C?) flag is used: > # uclcmd get -f -C /etc/pkg/FreeBSD.conf FreeBSD.fingerprints >=20 > returns > # A comment about fingerprints > # More comments > /usr/share/keys/pkg # an inline comment >=20 > Finally if uclcmd set is used, if the session is interactive, ask the u= ser what to do about the existing comment. If not append a note of the ch= ange to the comment so that the file becomes: >=20 > FreeBSD: { > url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", > mirror_type: "srv", > signature_type: "fingerprints", > # A comment about fingerprints > # More comments > ## Comments may be outdated, non-interactive edit 20151120T1400 > ## /usr/share/keys/pkg -> /root/keys/pkg > fingerprints: "/root/keys/pkg", # an inline comment > enabled: yes > } >=20 > 2) Assume everything can be commented, everything gets an extra pointer= for a potential comment string. Output all comments as the 'above' style= (bonus: comments become predictible in style). Same uclcmd behavior as d= escribed above. >=20 > The above are just ideas (and I know next to nothing about the guts of = libucl), but I think comments are important, if this or something else wo= rks I am willing to help with the implementation. >=20 > Regards, > Ike >=20 This was discussed at the developer summit at BSDCan, sadly the video is not online yet. The issue is that UCL allows comments anywhere, for example: #above FreeBSD: { /* before */ url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", mirror_type: /* middle */ "srv", signature_type: "fingerprints", /* after */ # under fingerprints: "/root/keys/pkg", # inline-after enabled: yes } Etc. So the solution that was discussed was changing libucl to use an Abstract Syntax Tree, but that is a lot of work. So for now, I am not sure what the best approach is. --=20 Allan Jude --mCnnVqGiXtb36sxo7S1sdISFmMWKrhVGT Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJWT3ciAAoJEBmVNT4SmAt+sxcP/j0IxRYFmj1BJXU41h9dHOuo TuXE9txKMfB9V3+azjwRI5cBb/vEByHAjWMH4zVHE8ihk1G07h8uuXtJd/GeLFof 64uPl6gf9Tvc6i09GoHBjQaXtk2FNnalf8VHvdXB1HXHhqljBoCm15oPLDZQH3mH tWxixM1jiQLL5zMz/kT82dcIV63EBhFKehHnd7hNyJYMfo0ywWAPVVOhrJzndw6w avpK0DSiwMv/4/47UAE2n9xYOhD/AM1JJrepJml7cvSo/6wTtaL0trrGm3sKy9HK oHppvmo7BOGKWKf1XhQahFCmj+MAOkUwTyvGotZxaTWYpC4XlkxvZpp+MDYFVWAz CWQtFC8kI77ttflT3hK09IBcl0eaNI8FPMQf3qFeBrhQTDwjJeo2RAwrsnoLqTAr dCl1gM3DEaONdLCYHWsox1q4e4kZ+dgvGR+ivssFIbQt7gjlxfhPBZkOmcf9Hsa9 nVB7jUoaqzdU7/Y4lnLaifLoTxpP2Z3b7Rjjy0PmyvzPm4iTsJt7gg++ReqI19Cf bMhjna3UzaJRqSZjXPsfCQS0vR14c+yMXhlpB1x+gV0s36llnrVJ0/gppnpbiWDE ixYpxj8KIWIA2ZqBQuGz9moyiLP9s0J3wfASeEszTqHd5MB/ZXF+xKQKuqEHSldp y8CbOhdNT+mCDw7AtRlX =zQ24 -----END PGP SIGNATURE----- --mCnnVqGiXtb36sxo7S1sdISFmMWKrhVGT-- From owner-freebsd-hackers@freebsd.org Fri Nov 20 20:14:39 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D89ADA32EF1 for ; Fri, 20 Nov 2015 20:14:39 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mx1.eichornenterprises.com (mx1.eichornenterprises.com [104.236.13.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.eichornenterprises.com", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 68BFC1ED5; Fri, 20 Nov 2015 20:14:38 +0000 (UTC) (envelope-from ike@michaeleichorn.com) Received: from mail.eichornenterprises.com (cpe-184-59-147-149.neo.res.rr.com [184.59.147.149]) by mx1.eichornenterprises.com (OpenSMTPD) with ESMTP id 24d19b06; Fri, 20 Nov 2015 15:14:35 -0500 (EST) Received: by mail.eichornenterprises.com (OpenSMTPD) with ESMTPSA id ef4a6d0a TLS version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Fri, 20 Nov 2015 15:14:34 -0500 (EST) Message-ID: <1448050474.2765.77.camel@michaeleichorn.com> Subject: Re: libUCL / UCL as FreeBSD config question From: "Michael B. Eichorn" To: Allan Jude , freebsd-hackers@freebsd.org Date: Fri, 20 Nov 2015 15:14:34 -0500 In-Reply-To: <564F771F.4060408@freebsd.org> References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> <564F6118.5030702@freebsd.org> <1448048197.2765.74.camel@michaeleichorn.com> <564F771F.4060408@freebsd.org> Content-Type: multipart/signed; micalg="sha-256"; protocol="application/x-pkcs7-signature"; boundary="=-63sReblvOQ2UInbuDG9a" X-Mailer: Evolution 3.18.1 Mime-Version: 1.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 20:14:39 -0000 --=-63sReblvOQ2UInbuDG9a Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2015-11-20 at 14:40 -0500, Allan Jude wrote: > On 2015-11-20 14:36, Michael B. Eichorn wrote: > > On Fri, 2015-11-20 at 13:06 -0500, Allan Jude wrote: > > > =C2=A0 > > > Although some limitation in libucl mean that, if you have a > > > config > > > that > > > has comments in it, the comments are lost, as they are not > > > represented > > > in the in-memory version of the object that then gets serialized > > > for > > > output. If you treat the config files as a database, then this is > > > fine, > > > but if the user expects to still hand edit them with an editor, > > > this > > > is > > > a fairly big POLA violation. > > >=20 > >=20 > > Even if someday we stop editing by hand, comments are far to useful > > IMHO to drop yet. Context is very important to what we do, and > > sometimes keys are just to cryptic. > >=20 > > I think I see two ways to avoid the POLA violation (but I am still > > rather new at this so be gentle) > >=20 > > 1) Add special keys for use in memory 'value' and 'comment' such > > that > > the file: > >=20 > > FreeBSD: { > > =C2=A0 url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", > > =C2=A0 mirror_type: "srv", > > =C2=A0 signature_type: "fingerprints", > > =C2=A0 # A comment about fingerprints > > =C2=A0 # More comments > > =C2=A0 fingerprints: "/usr/share/keys/pkg", # an inline comment > > =C2=A0 enabled: yes > > } > >=20 > > becomes in memory: > >=20 > > FreeBSD: { > > =C2=A0 url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", > > =C2=A0 > > mirror_type: "srv", > > =C2=A0 signature_type: "fingerprints", > > =C2=A0 fingerprints: { > > =C2=A0 > > =C2=A0 value: "/usr/share/keys/pkg" > > =C2=A0=C2=A0=C2=A0=C2=A0comment: { > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0above: "A comment > > about fingerprints\nMore comments" > > =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0inline: "an inline comment" > > =C2=A0=C2=A0=C2=A0 > > } > > =C2=A0 } > > =C2=A0 enabled: yes > > } > >=20 > > uclcmd should just return value like: > >=20 > > # uclcmd get -f /etc/pkg/FreeBSD.conf FreeBSD.fingerprints > >=20 > > returns > > /usr/share/keys/pkg > >=20 > > unless the comment (C?) flag is used: > > # uclcmd get -f -C /etc/pkg/FreeBSD.conf FreeBSD.fingerprints > >=20 > > returns > > # A comment about fingerprints > > # More comments > > /usr/share/keys/pkg # an inline comment > >=20 > > Finally if uclcmd set is used, if the session is interactive, ask > > the user what to do about the existing comment. If not append a > > note of the change to the comment so that the file becomes: > >=20 > > FreeBSD: { > > =C2=A0 url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", > > =C2=A0 mirror_type: "srv", > > =C2=A0 signature_type: "fingerprints", > > =C2=A0 # A comment about fingerprints > > =C2=A0 # More comments > > =C2=A0 ## Comments may be outdated, non-interactive edit 20151120T1400 > > =C2=A0 ## /usr/share/keys/pkg -> /root/keys/pkg > > =C2=A0 fingerprints: "/root/keys/pkg", # an inline comment > > =C2=A0 enabled: yes > > } > >=20 > > 2) Assume everything can be commented, everything gets an extra > > pointer for a potential comment string. Output all comments as the > > 'above' style (bonus: comments become predictible in style). Same > > uclcmd behavior as described above. > >=20 > > The above are just ideas (and I know next to nothing about the guts > > of libucl), but I think comments are important, if this or > > something else works I am willing to help with the implementation. > >=20 > > Regards, > > Ike > >=20 >=20 > This was discussed at the developer summit at BSDCan, sadly the video > is > not online yet. >=20 > The issue is that UCL allows comments anywhere, for example: >=20 > #above > FreeBSD: { > =C2=A0=C2=A0=C2=A0/* before */ url: "pkg+http://pkg.FreeBSD.org/${ABI}/la= test", > =C2=A0=C2=A0=C2=A0mirror_type: /* middle */ "srv", > =C2=A0=C2=A0=C2=A0signature_type: "fingerprints", /* after */ > =C2=A0=C2=A0=C2=A0# under > =C2=A0=C2=A0=C2=A0fingerprints: "/root/keys/pkg", # inline-after > =C2=A0=C2=A0=C2=A0enabled: yes > } >=20 > Etc. So the solution that was discussed was changing libucl to use an > Abstract Syntax Tree, but that is a lot of work. So for now, I am not > sure what the best approach is. >=20 >=20 >=20 Ok, I am satified that comments are a topic of discussion and that improvement may be forthcoming. I will wait on the video before making more chatter. Ike --=-63sReblvOQ2UInbuDG9a Content-Type: application/x-pkcs7-signature; name="smime.p7s" Content-Disposition: attachment; filename="smime.p7s" Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCEqAw ggYwMIIFGKADAgECAgMOXcYwDQYJKoZIhvcNAQELBQAwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQK Ew1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu dCBDQTAeFw0xNTA2MTMyMDI0NDZaFw0xNjA2MTQwMDM1NTBaMEgxHzAdBgNVBAMMFmlrZUBtaWNo YWVsZWljaG9ybi5jb20xJTAjBgkqhkiG9w0BCQEWFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggEi MA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDJVdWALPz5h2s5zUQGIJYl6Vp8FPtZNko8q/3s crCsxXJLprMaDdpnqTsmkbmEfKvsqPQE6HVOpGxVRTl/tCm+VvouW9eY9ITMigb1OnHdU13CKO0j drgeU1nHst0qxwsIofRD7nC4dakT6exnrVndlBmLrf/bLPh2qOM8YK5qKK6m33fE7AyYrwiYAWFT 3fERI7LakjaabrIoS/Y1rCdL5FaCTMOlRbZyduc8HkrgjT2JW+i4fVcKyGL5gExBJWfS3q1uGFaB ie6pYtl8lZPtvN0JSfibP003RBoLgzqHJKW91RL0qNeDjKZi/5nrlU398l9UoVvLLO3KxoPBXKCx AgMBAAGjggLcMIIC2DAJBgNVHRMEAjAAMAsGA1UdDwQEAwIEsDAdBgNVHSUEFjAUBggrBgEFBQcD AgYIKwYBBQUHAwQwHQYDVR0OBBYEFJZqarc6CcrOs6eAwOgrMznk5ZWWMB8GA1UdIwQYMBaAFFNy 7ZKc4NrLAVx8fpY1TvLUuFGCMCEGA1UdEQQaMBiBFmlrZUBtaWNoYWVsZWljaG9ybi5jb20wggFM BgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDovL3d3 dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2Vy dGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBh Y2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0 YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2Ug aW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8w LTAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUH AQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEv Y2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIu Y2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20v MA0GCSqGSIb3DQEBCwUAA4IBAQB4K8iQw+0FRn3xEnB3vIIu2Vi4C3ZGnOMWP90FFXLrZ6uAu9AK xVCjXUVP6nAEsOopTMu769vVecdBvg0KO2i5aTDTdTLX4g9d020g4OLWW1NiynAkX8oKqJLqZ53q vHK4zP4KWPS3bSqDWVCosTMfI+H6tkg+6G3gS0HHoHTLKZhIT3z6PQZAfeofM7ed6NOdAcj0J2lP ODHzzz7Y9x4wMwYJdidorzUDVYkNIkim8ak7hK9F60NadA5w/BirFATSlzRyV0h1tl6oNisEaQcq tGvy6UoCTDhzaJ7pQValfDXJ/A47P0hNj/CX/PmkY1wQHsEJz2pbh5lqteP/fO0rMIIGMDCCBRig AwIBAgIDDl3GMA0GCSqGSIb3DQEBCwUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRD b20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYG A1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcN MTUwNjEzMjAyNDQ2WhcNMTYwNjE0MDAzNTUwWjBIMR8wHQYDVQQDDBZpa2VAbWljaGFlbGVpY2hv cm4uY29tMSUwIwYJKoZIhvcNAQkBFhZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBIjANBgkqhkiG 9w0BAQEFAAOCAQ8AMIIBCgKCAQEAyVXVgCz8+YdrOc1EBiCWJelafBT7WTZKPKv97HKwrMVyS6az Gg3aZ6k7JpG5hHyr7Kj0BOh1TqRsVUU5f7Qpvlb6LlvXmPSEzIoG9Tpx3VNdwijtI3a4HlNZx7Ld KscLCKH0Q+5wuHWpE+nsZ61Z3ZQZi63/2yz4dqjjPGCuaiiupt93xOwMmK8ImAFhU93xESOy2pI2 mm6yKEv2NawnS+RWgkzDpUW2cnbnPB5K4I09iVvouH1XCshi+YBMQSVn0t6tbhhWgYnuqWLZfJWT 7bzdCUn4mz9NN0QaC4M6hySlvdUS9KjXg4ymYv+Z65VN/fJfVKFbyyztysaDwVygsQIDAQABo4IC 3DCCAtgwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUF BwMEMB0GA1UdDgQWBBSWamq3OgnKzrOngMDoKzM55OWVljAfBgNVHSMEGDAWgBRTcu2SnODaywFc fH6WNU7y1LhRgjAhBgNVHREEGjAYgRZpa2VAbWljaGFlbGVpY2hvcm4uY29tMIIBTAYDVR0gBIIB QzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRp b24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5n IHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBD QSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBs aWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQvMC0wK6ApoCeG JWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8w OQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9j YTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5j bGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG 9w0BAQsFAAOCAQEAeCvIkMPtBUZ98RJwd7yCLtlYuAt2RpzjFj/dBRVy62ergLvQCsVQo11FT+pw BLDqKUzLu+vb1XnHQb4NCjtouWkw03Uy1+IPXdNtIODi1ltTYspwJF/KCqiS6med6rxyuMz+Clj0 t20qg1lQqLEzHyPh+rZIPuht4EtBx6B0yymYSE98+j0GQH3qHzO3nejTnQHI9CdpTzgx888+2Pce MDMGCXYnaK81A1WJDSJIpvGpO4SvRetDWnQOcPwYqxQE0pc0cldIdbZeqDYrBGkHKrRr8ulKAkw4 c2ie6UFWpXw1yfwOOz9ITY/wl/z5pGNcEB7BCc9qW4eZarXj/3ztKzCCBjQwggQcoAMCAQICAR4w DQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0YXJ0 Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1 NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1 cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAx IFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7 zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8 VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+ jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQO Jebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB /wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAf BgNVHSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3dy5z dGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cuc3RhcnRz c2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3Js MIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3Rh cnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29t L2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywGXLhjjF6uHLkjd02h cdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXltUfO4n4bGGdKo3awP Wp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8C h507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893 gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0 PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBm unwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2L L9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwF i2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhE puP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMYIDfzCCA3sCAQEwgZQwgYwxCzAJ BgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRh bCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkg SW50ZXJtZWRpYXRlIENsaWVudCBDQQIDDl3GMA0GCWCGSAFlAwQCAQUAoIIBuzAYBgkqhkiG9w0B CQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNTExMjAyMDE0MzRaMC8GCSqGSIb3DQEJ BDEiBCAQFIJ4nUGaUEqcFFMy3Bsw4hPM4GmeihjG35gujmn8KjCBpQYJKwYBBAGCNxAEMYGXMIGU MIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJl IERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQ cmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAw5dxjCBpwYLKoZIhvcNAQkQAgsxgZeggZQw gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUg RGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFBy aW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDDl3GMA0GCSqGSIb3DQEBAQUABIIBAHOCP7m3 8z7GmcILzm14ghklpYh0NfOY37+d6FFa8xgyMc58D+5486MakvePn0z2+p34d0OGhiGySagXAkUd 9LeAzlXtVf081p1IWjxPCKRiNZbKxulOxKw9sh+X8aBMzm+Ehx96oJBDxbrvPez6kHBDWp3I+fix lEAm/MVRps967HhwhRC+iM9/q83BmTw4lrZV8+a0bjcSRmrt869rKEkgUdT5n1v/oRfd51k5Guq8 dalXt7NIUYXEKTYFY4W0f0Q6X3RA0WChBerl76njjArxDeIBgtsGK31zyayWOyUFgDKPrpvViFta xD4vfl4djnqcN1eJ5L5qfjI6HtqAU9sAAAAAAAA= --=-63sReblvOQ2UInbuDG9a-- From owner-freebsd-hackers@freebsd.org Fri Nov 20 20:46:50 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4F587A335C0 for ; Fri, 20 Nov 2015 20:46:50 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10]) by mx1.freebsd.org (Postfix) with ESMTP id BF4621FB3; Fri, 20 Nov 2015 20:46:48 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from [192.168.1.101] (unknown [79.119.24.18]) by mail.rdsor.ro (Postfix) with ESMTP id 7843C1F178; Fri, 20 Nov 2015 22:46:47 +0200 (EET) Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: libUCL / UCL as FreeBSD config question From: Dan Partelly In-Reply-To: <564F6118.5030702@freebsd.org> Date: Fri, 20 Nov 2015 22:46:47 +0200 Cc: freebsd-hackers@freebsd.org Message-Id: <5576AC9A-791F-4B52-9433-32D2806D35C9@rdsor.ro> References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> <564F6118.5030702@freebsd.org> To: Allan Jude X-Mailer: Apple Mail (2.3096.5) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 20:46:50 -0000 Allan, Thanks for clearing my confusion, and furthering my understanding on = whats cooking on this front. The tool is dandy. I have another issue I want to ask about: concurrency. Is there any support in either uclib and the tools like = uclcmd to ensure=20 atomic access to the ucl files ? And not on advisory level, (although if = utilities would respect=20 adviasory looking =E2=80=A6 it would be better than nothing). I mean = something on the lines of mandatory locking.=20 Was the question of concurrency discussed ? Dan > On 20 Nov 2015, at 20:06, Allan Jude wrote: >=20 > You can do: >=20 >=20 > uclcmd get -f /etc/pkg/FreeBSD.conf FreeBSD.url >=20 > and the result is: > pkg+http://pkg.FreeBSD.org/${ABI}/latest = >=20 > And then you could do: >=20 > uclcm set -f /etc/pkg/FreeBSD.conf FreeBSD.url > http://pkg.mysite.com/${ABI}/custom = >=20 > And it would modify the configuration in place for you. From owner-freebsd-hackers@freebsd.org Fri Nov 20 21:18:04 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 98EAEA33C42 for ; Fri, 20 Nov 2015 21:18:04 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from mx1.scaleengine.net (mx1.scaleengine.net [209.51.186.6]) by mx1.freebsd.org (Postfix) with ESMTP id 72FF21E23 for ; Fri, 20 Nov 2015 21:18:04 +0000 (UTC) (envelope-from allanjude@freebsd.org) Received: from [10.1.1.2] (unknown [10.1.1.2]) (Authenticated sender: allanjude.freebsd@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 08B01DEE0 for ; Fri, 20 Nov 2015 21:18:03 +0000 (UTC) Subject: Re: libUCL / UCL as FreeBSD config question To: freebsd-hackers@freebsd.org References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> <564F6118.5030702@freebsd.org> <5576AC9A-791F-4B52-9433-32D2806D35C9@rdsor.ro> From: Allan Jude X-Enigmail-Draft-Status: N1110 Message-ID: <564F8E1F.8060600@freebsd.org> Date: Fri, 20 Nov 2015 16:18:23 -0500 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <5576AC9A-791F-4B52-9433-32D2806D35C9@rdsor.ro> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MWvHNptkpS1nt4kgBwmx0RwXTr7leHRGK" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 21:18:04 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MWvHNptkpS1nt4kgBwmx0RwXTr7leHRGK Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 2015-11-20 15:46, Dan Partelly wrote: > Allan, >=20 > Thanks for clearing my confusion, and furthering my understanding on wh= ats cooking on this front. >=20 > The tool is dandy. I have another issue I want to ask about: >=20 > concurrency. Is there any support in either uclib and the tools like uc= lcmd to ensure=20 > atomic access to the ucl files ? And not on advisory level, (although i= f utilities would respect=20 > adviasory looking =E2=80=A6 it would be better than nothing). I mean so= mething on the lines > of mandatory locking.=20 >=20 > Was the question of concurrency discussed ? >=20 > Dan >=20 >=20 Most of the discussion centered around the design of the config files, and the library. My tool is in the early stages and was only briefly discussed with the goal of showing the power of UCL from an automation standpoint. Obviously uclcmd can use locking to ensure that two instances do not overlap. Updates to the file would also be atomic (save to tmpfile then rename into place), and it could check that the modification date of the file has not changed since it was read, to avoid overlapping any other access to the file. In the end, I picture it being somewhat like 'vipw' --=20 Allan Jude --MWvHNptkpS1nt4kgBwmx0RwXTr7leHRGK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQIcBAEBAgAGBQJWT44iAAoJEBmVNT4SmAt+E44P/18Z3HdKQp/gS8J0e6q7NhM0 wIPyNXX86ff88L0sCK1oljlydx+dZAcd8CwKDot7TUDixiPVrz/V20JLvY/o281w TtkHf1zVnJkYc1mVC8p/lJzAlgwCLcHqAX24PGG6NdQJIwUNtGn3xjlwSSKIIxMY tXUi8jKGaTO5A80YiyRJxkdOfZkP2wRqtaXpvv/EiI8e2O6dsEPt2aHW3k4CKB/3 6UdG8XDScvvyeKVoDhAuhkdAX9rYlZ3qWcjAYox2DFSIQeK04jV8mBGtgAXIYTYD w/9qhs1dPHGl4SLud5cJIZcUyv0PW4D/Fv85dZ1UrJulR6UaZUldtCqXeS9p7xyE 1QSeODmlDiPiPdBS9dbBWFNmTUzC3dF04klWjKabbiOzAxdtb1Znz/wJEGkafaAU u0SIA2zHe1vLhLzdQusydXuXKomZN+uDD8yOHZ+acchlxPOVq1M/7VX+HQOr2Kuj VYUgT1iYvXYrsG8+yy9ts9Tki4tuUdOWYvb9Grvhz1/VraOXIpZEwU0IQmDbGHGJ fHh/LO8CHCmlriOj9yrIwzLqN1Q0WdtS/7SU1tXD03+fFcl3MIiZp/x+XJf84PY8 b3rELsq0vpLAW2l+fY9j25ecp1xw+JQDIRf9mi9sK6DThWSSL2Owqdiwf8WxfvnP aFj4e8jKEq97YiS/UxV2 =ktsO -----END PGP SIGNATURE----- --MWvHNptkpS1nt4kgBwmx0RwXTr7leHRGK-- From owner-freebsd-hackers@freebsd.org Fri Nov 20 20:58:51 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1ABF0A337F5 for ; Fri, 20 Nov 2015 20:58:51 +0000 (UTC) (envelope-from cemeyer@uw.edu) Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DB7DD150A for ; Fri, 20 Nov 2015 20:58:50 +0000 (UTC) (envelope-from cemeyer@uw.edu) Received: by pacej9 with SMTP id ej9so126885816pac.2 for ; Fri, 20 Nov 2015 12:58:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uw-edu.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:in-reply-to:references:mime-version :content-type:content-transfer-encoding; bh=UwRLgshkyBPdEU0c80yn13CIBw4BqpoLR485nLhqukU=; b=dJ2b8XnkwCQQI+1oUHHdee2O8h6dvdtuhE87mhKlAjJlg+ionlxYqfsHFhJNkq8XNz 3KOgwmgPvMKqY9hAitVnqtmTATWjsSIqvPVxqCrT2TT1lai6ZWOUCArUjx3e5aI8m9l9 WZzbmxWyaW0dpcs9wk7XgGxe4TJ3oiVkO7gjgnQt3ZXQduBzQhX9QEkotxcEdtTrlLkg AxqhDjvuVStUvhBd26EFg4LfnLt2R642wgX2Hoo5C9AjbKJHrZZrwNE+wutkjzOZ3rXQ fNyddcaR/xHOFrp+lKbb3A0IH4sZcbUCMARDB+otk83wfCsiXau/cwtPZOI78uI9GT70 ywlg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=UwRLgshkyBPdEU0c80yn13CIBw4BqpoLR485nLhqukU=; b=QxyUIWHLjUMGw4zNKETNM+/nyZ3ZSvXu8P+mWAjkYQt2sUn+290uFadEEFojlmhaL3 EbLbGCKI9ycv4T/ICjQ44FCch8qJdg/ImSZK1BZQMIptjscG5wEuLTBwWhnIy+w3dHkn SFWvb6mJHX4pgNQ77QaWufdzmG3jfAiaosQ2g4C8tYAAwbJM1goWawS+OwLO7puYrT8I PT3J6cokxkSVz0REBABwGpfRg5PdKycopjNU2bDEhJLR95WgndxlRmAvB3MIwzreezr7 u1HkPaWIduuGHj3dEAXo8pR8PWeTHj+CrKSxTYwM1dpii30FDHrjE+WbhkiMKF4EflAt UBAw== X-Gm-Message-State: ALoCoQmf7aBijGyn8OOSlGx83/Z8wv+galQupcBQ400UxQSADKheVRBkDMStL2blcFqcIAa+YTla X-Received: by 10.66.63.37 with SMTP id d5mr22024399pas.103.1448053130290; Fri, 20 Nov 2015 12:58:50 -0800 (PST) Received: from m (c-50-181-252-241.hsd1.wa.comcast.net. [50.181.252.241]) by smtp.gmail.com with ESMTPSA id sz9sm861485pab.13.2015.11.20.12.58.49 for (version=TLSv1/SSLv3 cipher=OTHER); Fri, 20 Nov 2015 12:58:49 -0800 (PST) Date: Fri, 20 Nov 2015 12:58:46 -0800 From: Conrad Meyer To: freebsd-hackers@freebsd.org Subject: Re: libUCL / UCL as FreeBSD config question Message-ID: <20151120125846.31d4f4cc@m> In-Reply-To: <564F771F.4060408@freebsd.org> References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> <564F6118.5030702@freebsd.org> <1448048197.2765.74.camel@michaeleichorn.com> <564F771F.4060408@freebsd.org> X-Mailer: Claws Mail 3.12.0 (GTK+ 2.24.28; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Fri, 20 Nov 2015 21:50:19 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Nov 2015 20:58:51 -0000 On Fri, 20 Nov 2015 14:40:15 -0500 Allan Jude wrote: > The issue is that UCL allows comments anywhere, for example: > > #above > FreeBSD: { > /* before */ url: > "pkg+http://pkg.FreeBSD.org/${ABI}/latest", mirror_type: /* > middle */ "srv", signature_type: "fingerprints", /* after */ > # under > fingerprints: "/root/keys/pkg", # inline-after > enabled: yes > } > > Etc. So the solution that was discussed was changing libucl > to use an Abstract Syntax Tree, but that is a lot of work. > So for now, I am not sure what the best approach is. I think an AST that keeps comments is a good approach going forwards. We don't need a short-term fix that is anything less than that. Best, Conrad From owner-freebsd-hackers@freebsd.org Sat Nov 21 07:36:13 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8394AA2A54F for ; Sat, 21 Nov 2015 07:36:13 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10]) by mx1.freebsd.org (Postfix) with ESMTP id 41CFE1D26 for ; Sat, 21 Nov 2015 07:36:12 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from [192.168.1.100] (unknown [79.119.24.18]) by mail.rdsor.ro (Postfix) with ESMTP id 3D67015B48; Sat, 21 Nov 2015 09:36:11 +0200 (EET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: libUCL / UCL as FreeBSD config question From: Dan Partelly In-Reply-To: <20151120125846.31d4f4cc@m> Date: Sat, 21 Nov 2015 09:36:11 +0200 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: 7bit Message-Id: References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> <564F6118.5030702@freebsd.org> <1448048197.2765.74.camel@michaeleichorn.com> <564F771F.4060408@freebsd.org> <20151120125846.31d4f4cc@m> To: Conrad Meyer X-Mailer: Apple Mail (2.3096.5) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2015 07:36:13 -0000 I fully support this point of view. A short term fix is uncalled for. > On 20 Nov 2015, at 22:58, Conrad Meyer wrote: > > On Fri, 20 Nov 2015 14:40:15 -0500 > Allan Jude wrote: >> The issue is that UCL allows comments anywhere, for example: >> >> #above >> FreeBSD: { >> /* before */ url: >> "pkg+http://pkg.FreeBSD.org/${ABI}/latest", mirror_type: /* >> middle */ "srv", signature_type: "fingerprints", /* after */ >> # under >> fingerprints: "/root/keys/pkg", # inline-after >> enabled: yes >> } >> >> Etc. So the solution that was discussed was changing libucl >> to use an Abstract Syntax Tree, but that is a lot of work. >> So for now, I am not sure what the best approach is. > > I think an AST that keeps comments is a good approach going > forwards. We don't need a short-term fix that is anything > less than that. > > Best, > Conrad > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" From owner-freebsd-hackers@freebsd.org Sat Nov 21 08:06:53 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 265F1A2AD97 for ; Sat, 21 Nov 2015 08:06:53 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from mail.rdsor.ro (mail.rdsor.ro [193.231.238.10]) by mx1.freebsd.org (Postfix) with ESMTP id 6978F1826; Sat, 21 Nov 2015 08:06:52 +0000 (UTC) (envelope-from dan_partelly@rdsor.ro) Received: from [192.168.1.100] (unknown [79.119.24.18]) by mail.rdsor.ro (Postfix) with ESMTP id 3DCA11F150; Sat, 21 Nov 2015 10:06:51 +0200 (EET) Mime-Version: 1.0 (Mac OS X Mail 9.1 \(3096.5\)) Subject: Re: libUCL / UCL as FreeBSD config question From: Dan Partelly In-Reply-To: <564F8E1F.8060600@freebsd.org> Date: Sat, 21 Nov 2015 10:06:51 +0200 Cc: freebsd-hackers@freebsd.org Message-Id: References: <5B598F72-C5DD-48FD-866D-F90E117D646E@rdsor.ro> <564F6118.5030702@freebsd.org> <5576AC9A-791F-4B52-9433-32D2806D35C9@rdsor.ro> <564F8E1F.8060600@freebsd.org> To: Allan Jude X-Mailer: Apple Mail (2.3096.5) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2015 08:06:53 -0000 I gather then that concurrency was deemed s not important , probably not = even mentioned in those talks.=20 I think you guys should think more at concurrency issues, and give them = first class citizen status. Please do not rush a solution. =20 It;s not about making sure that 2 instances of uclcomand don't overlap, = it is to make sure=20 that **nothing** overlaps when accessing that file. No arbitrary n tools = / daeomns whatever.=20 It is a , after all, an OS config file, not the config file of a game. Absent the will to adopt a proper, fully transactional and atomic = mechanism of storing OS configuration,=20 I would go back to the drawing board for a while. It may even be a long = while. Please do not employ an=20 half breed solution to this problem/ Leave things as they are today = until you figure it all out from all angles. > On 20 Nov 2015, at 23:18, Allan Jude wrote: >=20 > On 2015-11-20 15:46, Dan Partelly wrote: >> Allan, >>=20 >> Thanks for clearing my confusion, and furthering my understanding on = whats cooking on this front. >>=20 >> The tool is dandy. I have another issue I want to ask about: >>=20 >> concurrency. Is there any support in either uclib and the tools like = uclcmd to ensure=20 >> atomic access to the ucl files ? And not on advisory level, (although = if utilities would respect=20 >> adviasory looking =E2=80=A6 it would be better than nothing). I mean = something on the lines >> of mandatory locking.=20 >>=20 >> Was the question of concurrency discussed ? >>=20 >> Dan >>=20 >>=20 >=20 > Most of the discussion centered around the design of the config files, > and the library. My tool is in the early stages and was only briefly > discussed with the goal of showing the power of UCL from an automation > standpoint. Obviously uclcmd can use locking to ensure that two > instances do not overlap. Updates to the file would also be atomic = (save > to tmpfile then rename into place), and it could check that the > modification date of the file has not changed since it was read, to > avoid overlapping any other access to the file. >=20 > In the end, I picture it being somewhat like 'vipw' >=20 > --=20 > Allan Jude From owner-freebsd-hackers@freebsd.org Sat Nov 21 23:15:51 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1E87DA34C60 for ; Sat, 21 Nov 2015 23:15:51 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id DF4DA1FCB for ; Sat, 21 Nov 2015 23:15:50 +0000 (UTC) (envelope-from yuri@rawbw.com) Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128]) (authenticated bits=0) by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id tALNFn5e004139 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for ; Sat, 21 Nov 2015 15:15:49 -0800 (PST) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be yuri.doctorlan.com To: Freebsd hackers list From: Yuri Subject: Here documents: do they work in FreeBSD make? Message-ID: <5650FB25.2060408@rawbw.com> Date: Sat, 21 Nov 2015 15:15:49 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Nov 2015 23:15:51 -0000 This syntax doesn't work for me: @cat <${MY_DIR}/my-file \ #!/bin/sh \ \ echo 'Hello World!' \ EOF \ ${MY_DIR}/my-file is created empty. Could anybody give me a hint what am I doing wrong? Thanks, Yuri