Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-15:08.sendmail
For the purity of the experiment I installed fresh FreeBSD 10.1-RELEASE amd64. Then I updated it to p13. Tried to send email via localhost - no luck as before. Then I applied Gregory's new.patch patch, rebuilt, installed and rebooted. It works now! I successfully sent and received my email. Here is how it looks now: % echo ttt | mail -s 'ss' ptimof...@xxx.ru Jun 23 10:31:35 test10-64 sendmail[825]: t5N7VZcc000825: from=timp, size=38, class=0, nrcpts=1, msgid=<201506230731.t5n7vzcc000...@xxx.ru>, relay=timp@localhost Jun 23 10:31:35 test10-64 sendmail[825]: STARTTLS=client, relay=[127.0.0.1], version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-AES256-GCM-SHA384, bits=256/256 Jun 23 10:31:35 test10-64 sm-mta[826]: STARTTLS=server, relay=localhost [127.0.0.1], version=TLSv1/SSLv3, verify=NO, cipher=DHE-RSA-AES256-GCM-SHA384, bits=256/256 Jun 23 10:31:35 test10-64 sm-mta[826]: t5N7VZLw000826: from=, size=333, class=0, nrcpts=1, msgid=<201506230731.t5n7vzcc000...@xxx.ru>, proto=ESMTP, daemon=Daemon0, relay=localhost [127.0.0.1] Jun 23 10:31:35 test10-64 sendmail[825]: t5N7VZcc000825: to=ptimof...@xxx.ru, ctladdr=timp (1001/1001), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30038, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (t5N7VZLw000826 Message accepted for delivery) Jun 23 10:31:36 test10-64 sm-mta[828]: t5N7VZLw000826: to=, delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=30333, relay=kalmar.xxx.ru. [192.168.31.190], dsn=2.0.0, stat=Sent (t5N7VZaL008894 Message accepted for delivery) I hope this patch will be in p14, as addition to p13! -- View this message in context: http://freebsd.1045724.n5.nabble.com/Re-FreeBSD-Announce-FreeBSD-Errata-Notice-FreeBSD-EN-15-08-sendmail-tp6019450p6020423.html Sent from the freebsd-stable mailing list archive at Nabble.com. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
FreeBSD_stable_10 - Build #1518 - Fixed
FreeBSD_stable_10 - Build #1518 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_stable_10/1518/ to view the results. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ?
-Original Message- From: Willem Jan Withagen Sent: Monday, June 22, 2015 11:48 PM To: Daniel Genis ; freebsd-stable@freebsd.org Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? We are kind of new to FreeBSD, so we're wondering what are the plans to merge these fixes into the 10.1-RELEASE branch ? We'd love to get these fixes without having to rebuild the kernel. Is there any chance for the merge to happen in the near future, or should we compile the kernel to get the fixes? The RELEASE branch is exactly what it says, RELEASE. And is only done once per version when the actual official RELEASE is. So the next one will be the upcoming 10.2-RELEASE. Which is schedules for August 2015 according to: There are actually 2 branches tracking release: RELEASE which is the original release itself and RELENG which is the release+security and some errata fixes. In practice one should always track and compile RELENG sources with production servers, unless there's a bugfix or added driver that's only available in STABLE. The other way to get to the front of the like is starting and tracking 10-STABLE which is the running front of the kernel/software development. STABLE means stable ABI, not necessarily that the branch is running stable. It should be considered more as a beta, than something to track if one does want. (Yes, there can be even major breakages in STABLE. It's not usual but it can happen.) The running front of development is HEAD, which is 11.0 at this time - once latest major release gets first "dot" release, the major version number of HEAD gets advanced. HEAD is more or less recommended for those who can deal with debugging breakages and whatnot and can be severely broken from time to time. It looks like at the moment the fix for you would be temporarily track/compile 10.1 STABLE and then once 10.2 is released start tracking 10.2 RELENG -Reko ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
