Re: sysutils/diskcheckd needs fixing and a maintainer
On 18 August 2011 09:03, per...@pluto.rain.com wrote: Chris Rees utis...@gmail.com wrote: We don't want to provide broken software. Mark Linimon lini...@lonesome.com wrote: ... it's obsolete, broken, junk ... Unless there is more to this than is reported in those two PRs, I'd call it a considerable exaggeration to describe diskcheckd as broken. * http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/115853 is shown as closed, so presumably is no longer a problem. Wow, would it have been too difficult to actually READ the closing message from Jeremy? I suggest you look again -- I've pasted it here so you can see it. The problem here is that the code does not do what the manpage says (or vice-versa). The 3rd column does not specify frequency of checking, but rather, over what duration of time to spread a single disk scan over. Thus, 7 days would mean spread the entire disk check at X rate over the course of 7 days. There is still a bug in the code where large disks will cause problems resulting in updateproctitle() never getting called, and so on, but that's unrelated to this PR. I'm closing the PR because trying to fix all of this should really be ben@'s responsibility. (Sorry for sounding harsh.) How does that indicate it's fixed? It's an 'abandoned' PR. * http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/143566 says ... diskcheckd runs fine when gmirror is not involved ... and then goes on to describe a problem _when diskcheckd is run on a component of a gmirror_. How anyone got from in some way incompatible with gmirror to broken escapes me. One could as well claim that gmirror is broken because it is incompatible with diskcheckd :- No. It's broken because there's no logical reason -- it will probably break with other things. I'm currently running diskcheckd on an 8.1 gmirrored system with config file /dev/ad0 * * 8192 -- which should be using about 1/6 of that disk's bandwidth -- and will see what happens when it reaches the end of the disk (sometime tomorrow). So far I have not seen any issues. Thank you for testing and investigating, this is what the port has needed, and two days of being deprecated has achieved more than 18 months of a PR being open. Chris -- Chris Rees | FreeBSD Developer cr...@freebsd.org | http://people.freebsd.org/~crees ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: sysutils/diskcheckd needs fixing and a maintainer
Am 18.08.2011 08:20, schrieb Chris Rees: On 18 August 2011 09:03, per...@pluto.rain.com wrote: Chris Rees utis...@gmail.com wrote: We don't want to provide broken software. Mark Linimon lini...@lonesome.com wrote: ... it's obsolete, broken, junk ... Unless there is more to this than is reported in those two PRs, I'd call it a considerable exaggeration to describe diskcheckd as broken. * http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/115853 is shown as closed, so presumably is no longer a problem. Wow, would it have been too difficult to actually READ the closing message from Jeremy? I suggest you look again -- I've pasted it here so you can see it. The problem here is that the code does not do what the manpage says (or vice-versa). The 3rd column does not specify frequency of checking, but rather, over what duration of time to spread a single disk scan over. Thus, 7 days would mean spread the entire disk check at X rate over the course of 7 days. There is still a bug in the code where large disks will cause problems resulting in updateproctitle() never getting called, and so on, but that's unrelated to this PR. I'm closing the PR because trying to fix all of this should really be ben@'s responsibility. (Sorry for sounding harsh.) How does that indicate it's fixed? It's an 'abandoned' PR. This would be a case for marking it suspended (or possibly analyzed, depending on which of these two fits best), rather than closing it. The status is also a statement... Thank you for testing and investigating, this is what the port has needed, and two days of being deprecated has achieved more than 18 months of a PR being open. So the bottom line for this case is, we sometimes only get sufficient attention through deprecating ports. Unfortunately that approach might wear off some day. Too bad. :-( Do we need a think twice before adding a port habit? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
apps in ports by license
Dear All, Maybe stupid question but is there any possibility to search, sort apps by license? Thanks much!! Jindra ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: apps in ports by license
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/18/11 01:33, Jindřich Káňa wrote: Dear All, Maybe stupid question but is there any possibility to search, sort apps by license? Not currently. This would need a change to INDEX format I think... Cheers, - -- Xin LI delp...@delphij.nethttps://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (FreeBSD) iQEcBAEBCAAGBQJOTNWaAAoJEATO+BI/yjfBgUQH/3t33gZKSD9G3TWfsAYQBscY HfGxsW82K9Gsn9WTpdtQh7G0fwxE0ZuH01r4IHmwneBjGCcv+n9VGep6FSag1h3+ JkFcG3xe+XxqhTc/qjRk5tdqR8miShQ6XN1cLSaWnQKH2yM4OCenrXcM9s6ieGmu iipHHeKVAyg705EbRAQXhzZUM9B8Zq2lDELJmwYIQVdNsiiG9WO6blWRpA2yNNPx JoaCS3BimjO/Zmxj6oZZ/lzD+cyRetYKJq0SuQOcMQ6F2sbfoSh/DP+vRpSS7ozy AwBLiFhDH+DfP9o22DnwKWZK4t+yZ3pgf0iRZNVpfJg+3Tw1UrFHgbSEyr58eTc= =fg/A -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: apps in ports by license
On 18 August 2011 09:33, Jindřich Káňa jindr...@kana.at wrote: Dear All, Maybe stupid question but is there any possibility to search, sort apps by license? Not a stupid question -- currently there isn't an easy way, but why would you want to do that anyway? Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Big patches
Hi, I've been told that dynamic pkg-plists are bad or at least should be avoided´at most costs. Now, all my patches for Typo3 seem blocked by a SPAM Filter or at least take 2 days until I get reply. See PR159878-81, I submitted the patches on tuesday. So, what should I do? Still create full pkg-plists and hope that the patch passes the FreeBSD PR system or fall back to dynamic pkg-plists? Thanks, Helmut ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Big patches
On 18 August 2011 20:11, Helmut Schneider jumpe...@gmx.de wrote: Hi, I've been told that dynamic pkg-plists are bad or at least should be avoided´at most costs. Now, all my patches for Typo3 seem blocked by a SPAM Filter or at least take 2 days until I get reply. See PR159878-81, I submitted the patches on tuesday. So, what should I do? Still create full pkg-plists and hope that the patch passes the FreeBSD PR system or fall back to dynamic pkg-plists? Thanks, Helmut Do you have any webspace you could upload them to? If not, email them to me and I'll host them for you. Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
[HEADS UP] apache22 will be become the default apache version during the next days!
Just a short reminder. We will switch the default apache version during the next days to from apache13 to apache22. apache13 will stay in the portstree for the next months, but will be removed before end of this year! Users who will stay for this time with apache13 should create the following entry in /etc/make.conf. APACHE_PORT= www/apache13 Please take the time and migrate to apache22 now! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Postfix - Dovecot SASL problem
Hi,
I'm using mail/postfix with WITH_DOVECOT2=yes and mail/dovecot2 with MySQL
backend for users from FreeBSD ports:
dovecot-2.0.12
postfix-2.8.4,1
I'm unable to get SMTP authentication working using Dovecot SASL with
postfix/main.cf:
...
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous, noplaintext
smtpd_sasl_tls_security_options = noanonymous
...
dovecot/dovecot.conf
...
userdb {
args = /usr/local/etc/dovecot/dovecot-mysql.conf
driver = sql
}
passdb {
args = /usr/local/etc/dovecot/dovecot-mysql.conf
driver = sql
}
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
}
...
Postfix works fine if the SASL Auth is turned off. Dovecot works
fine per se for accessing mailboxes via POP3 and IMAP.
When attempting to use Dovecot for SMTP SASL auth, what I get is
2011-08-18 23:31:57auth: Debug: Loading modules from directory:
/usr/local/lib/dovecot/auth
Aug 18 23:31:57 mail postfix/smtpd[57411]: fatal: no SASL authentication
mechanisms
2011-08-18 23:31:57auth: Debug: auth client connected (pid=57411)
Aug 18 23:31:58 mail postfix/master[57398]: warning: process
/usr/local/libexec/postfix/smtpd pid
57411 exit status 1
Aug 18 23:31:58 mail postfix/master[57398]: warning:
/usr/local/libexec/postfix/smtpd: bad command
startup -- throttling
even though postfix starts to talk to dovecot accroding to ktrace:
57671 smtpdCALL connect(0xe,0x7fffd870,0x6a)
57671 smtpdSTRU struct sockaddr { AF_LOCAL, private/auth }
57671 smtpdNAMI private/auth
57671 smtpdRET connect 0
57671 smtpdCALL fcntl(0xe,F_GETFL,0)
57671 smtpdRET fcntl 6
57671 smtpdCALL fcntl(0xe,F_SETFL,O_RDWR)
57671 smtpdRET fcntl 0
57671 smtpdCALL gettimeofday(0x801434770,0)
57671 smtpdRET gettimeofday 0
57671 smtpdCALL getpid
57671 smtpdRET getpid 57671/0xe147
57671 smtpdCALL poll(0x7fffd860,0x1,0x2710)
57671 smtpdRET poll 1
57671 smtpdCALL write(0xe,0x80144f010,0x17)
57671 smtpdGIO fd 14 wrote 23 bytes
VERSION 1 0
CPID57671
57671 smtpdRET write 23/0x17
57671 smtpdCALL gettimeofday(0x801434770,0)
57671 smtpdRET gettimeofday 0
57671 smtpdCALL poll(0x7fffd850,0x1,0x2710)
57671 smtpdRET poll 1
57671 smtpdCALL read(0xe,0x80144f010,0x1000)
57671 smtpdGIO fd 14 read 117 bytes
VERSION 1 1
MECHPLAIN plaintext
MECHLOGIN plaintext
SPID57672
CUID1
COOKIE acc0b5dcc32aed19ae3e6823ad91bc42
DONE
57671 smtpdRET read 117/0x75
57671 smtpdCALL gettimeofday(0x801434770,0)
57671 smtpdRET gettimeofday 0
57671 smtpdCALL gettimeofday(0x7fffca80,0)
57671 smtpdRET gettimeofday 0
57671 smtpdCALL getpid
57671 smtpdRET getpid 57671/0xe147
57671 smtpdCALL sendto(0x7,0x7fffcac0,0x52,0,0,0)
57671 smtpdGIO fd 7 wrote 82 bytes
18Aug 18 23:33:35 postfix/smtpd[57671]: fatal: no SASL authentication
mechanisms
57671 smtpdRET sendto 82/0x52
Any ideas where could be the problem?
TIA,
Petr
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Postfix - Dovecot SASL problem
On Thu, 18 Aug 2011 23:38:58 +0200 Petr Holub articulated: Any ideas where could be the problem? This question really belongs on either the Postfix or Dovecot forums. I would suggest starting with the Postfix one and proceeding from there. Start with the documentation located here: http://www.postfix.com/DEBUG_README.html Read the Reporting problems to postfix-us...@postfix.org at the end of that documentation. Be sure to include the output from the saslfinger tool. This can be found at http://postfix.state-of-mind.de/patrick.koetter/saslfinger/. -- Jerry ✌ jerry+po...@seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ Whenever anyone says, theoretically, they really mean not really. Dave Parnas ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Postfix - Dovecot SASL problem
[ I agree with Jerry that this question belongs on postfix-users, but I hope my response is helpful ] On Thu, 2011-08-18 at 23:38:58 +0200, Petr Holub wrote: I'm using mail/postfix with WITH_DOVECOT2=yes and mail/dovecot2 with MySQL backend for users from FreeBSD ports: dovecot-2.0.12 postfix-2.8.4,1 I'm unable to get SMTP authentication working using Dovecot SASL with postfix/main.cf: Generally, when asking for help with Postfix, it is better to provide the output of 'postconf -n' rather than snippets of your main.cf. ... smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous So you prohibit plaintext SASL authentication unless the session is TLS encrypted. When attempting to use Dovecot for SMTP SASL auth, what I get is 2011-08-18 23:31:57auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Aug 18 23:31:57 mail postfix/smtpd[57411]: fatal: no SASL authentication mechanisms There are no TLS connection lines in your log excerpt; if we assume that no encrypted session was established, then this error makes sense if ... MECHPLAIN plaintext MECHLOGIN plaintext dovecot only offers plaintext authentication mechanisms, which you have configured Postfix to explicitly disallow for non-TLS sessions. -- Sahil Tandon sa...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Postfix - Dovecot SASL problem
Hi-- On Aug 18, 2011, at 2:38 PM, Petr Holub wrote: smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous From what I've seen in your ktrace, you're only offering MECH LOGIN plaintext, which isn't going be allowable per the Postfix setting. You need to setup CRAM-MD5 or maybe GSSAPI, or else permit plaintext auth mechanisms if the connection is coming via TLS/SSL: http://wiki2.dovecot.org/HowTo/CRAM-MD5 Also see: http://www.postfix.org/postconf.5.html Warning: it appears that clients try authentication methods in the order as advertised by the server (e.g., PLAIN ANONYMOUS CRAM-MD5) which means that if you disable plaintext passwords, clients will log in anonymously, even when they should be able to use CRAM-MD5. So, if you disable plaintext logins, disable anonymous logins too. Postfix treats anonymous login as no authentication. Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Big patches
Sorry, I did not see your message and emailed you separately. GNATS has a spamcatcher for 500k messages (mostly this catches viruses). Normally I handle such PRs manually before the cleanup process runs, but I forgot to do it this time. (I only took a glance.) Does the plist change dramatically every time the ports are updated? Is there any way around this if so? Such large changes put stress not only on GNATS (it is, after all, a database), but also on the CVS repository when the updates are committed. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Postfix - Dovecot SASL problem
On Thu, 2011-08-18 at 15:18:41 -0700, Chuck Swiger wrote: From what I've seen in your ktrace, you're only offering MECH LOGIN plaintext, which isn't going be allowable per the Postfix setting. His dovecot configuration also appears to be offering the PLAIN plaintext auth mechanism; not just LOGIN. -- Sahil Tandon sa...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Postfix - Dovecot SASL problem
On Aug 18, 2011, at 4:25 PM, Sahil Tandon wrote: From what I've seen in your ktrace, you're only offering MECH LOGIN plaintext, which isn't going be allowable per the Postfix setting. His dovecot configuration also appears to be offering the PLAIN plaintext auth mechanism; not just LOGIN. Yes, that's right-- but they're both plaintext, which Postfix was configured not to allow... Regards, -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Postfix - Dovecot SASL problem
On Thu, 2011-08-18 at 16:35:58 -0700, Chuck Swiger wrote: On Aug 18, 2011, at 4:25 PM, Sahil Tandon wrote: From what I've seen in your ktrace, you're only offering MECH LOGIN plaintext, which isn't going be allowable per the Postfix setting. His dovecot configuration also appears to be offering the PLAIN plaintext auth mechanism; not just LOGIN. Yes, that's right-- but they're both plaintext, which Postfix was configured not to allow... Indeed, as I noted[1] earlier in this thread; I replied to your message for the sake of completeness and posterity. :) [1] http://lists.freebsd.org/pipermail/freebsd-ports/2011-August/069300.html -- Sahil Tandon sa...@freebsd.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD Port: chromium-13.0.782.112
Hey, I would like to use the chromedriver target from the chromium port. However, I do not know how to add that target to my local ports chromium configuration. How do I make the chromedriver target? -- -Patrick Ranspach- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Postfix - Dovecot SASL problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/18/2011 05:42 PM, Sahil Tandon wrote: On Thu, 2011-08-18 at 16:35:58 -0700, Chuck Swiger wrote: On Aug 18, 2011, at 4:25 PM, Sahil Tandon wrote: From what I've seen in your ktrace, you're only offering MECH LOGIN plaintext, which isn't going be allowable per the Postfix setting. His dovecot configuration also appears to be offering the PLAIN plaintext auth mechanism; not just LOGIN. Yes, that's right-- but they're both plaintext, which Postfix was configured not to allow... Indeed, as I noted[1] earlier in this thread; I replied to your message for the sake of completeness and posterity. :) [1] http://lists.freebsd.org/pipermail/freebsd-ports/2011-August/069300.html From what I see, this is exactly correct and the information provided (while not a Postfix or Dovecot mailing list) should definitely be of help. In fact, it is the solution to the problem. Well done! :) Regards, Janky Jay, III -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5NtiEACgkQGK3MsUbJZn4qJQCffNCPfQrzLSw423PZwgLNRG5p 7RoAn2+ubGLvzz2wk/bjn976HIqgAYs7 =JUBJ -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
