Re: comsat-biff issue
Is your mail being delivered to /var/mail/yourname or do you have a .forward file? The comsat daemon is notified by mail.local which delivers mail to the local mail spool. If you have a .forward file, mail.local is not used and you won't get a biff notification. - todd
Re: NFS encoding?
- Original Message - | Looks like there is no resolution but replacement. Thanks. | | http://superuser.com/questions/302407/what-to-do-with-nfs-server-utf-8-and-wi | ndows-7 | | Best regards, | Zhi-Qiang Lei | | On Jul 6, 2015, at 1:56 PM, Johan Petersson vhdlni...@gmail.com wrote: | | i really wish i could help you out - my girlfriend lives in hong kong so i | understand the need to display chinese chars, i do. | i have ran NFS for years, but only in a pure UNIX environment - | bsd-versions, | linux and osx. but i'm not any kind of NFS expert - i'd have to suggest | that | you try to read as many man-pages as you can. or check out the NFS source | code. once you know the encoding, put the question to Microsoft. | or simply stop using windows haha | | good luck! | /Johan | | On Mon, Jul 6, 2015 at 7:36 AM, Zhi-Qiang Lei zhiqiang@gmail.com | mailto:zhiqiang@gmail.com wrote: | Is there such encoding option in NFS setting? And what encoding does | OpenBSD | used as default for filenames? Thanks for your suggestion though. | | Best regards, | Zhi-Qiang Lei | | On Jul 6, 2015, at 1:02 PM, Johan Petersson vhdlni...@gmail.com | mailto:vhdlni...@gmail.com wrote: | | that is not a question for the OpenBSD people if you ask me. win7 is junk, | go | ask microsoft this kind of questions | | On Mon, Jul 6, 2015 at 6:58 AM, Zhi-Qiang Lei zhiqiang@gmail.com | mailto:zhiqiang@gmail.com wrote: | I have an OpenBSD 5.6 server with NFS enabled. When I mount it on my Mac | and | Raspberry Pi, everything is fine. However, when I map it on Windows 7, all | the | filenames with Chinese in them cannot be displayed correctly. How can I | fix | this? Thanks. | | Best regards, | Zhi-Qiang Lei | | What about re-exporting the NFS share out via Samba and just ditching the NFS client in Windows 7 altogether? -- James A. Peltier IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 604-365-6432 Fax : 778-782-3045 E-Mail : jpelt...@sfu.ca Website : http://www.sfu.ca/itservices Twitter : @sfu_rcg Powering Engagement Through Technology
Re: comsat-biff issue
On Mon, 06 Jul 2015 16:53:27 +0200, Walter Alejandro Iglesias wrote: Till you mentioned about it I've ignored the existence of /usr/libexec/mail.local. :-) I'm a new to OpenBSD. Is it some kind of procmail's alike functionality? It's what delivers messages to /var/mail/username when invoked by the MTA. I tried modifying the comsat line in inetd.conf, using just udp4, removing the ip limit prefix, etc. I've tried installing procmail (telling smtpd to use it). I did some tests stopping /etc/rc.d/inetd and running inetd -d form the command line. It turns out mail.local only supported udp4 anyway (though I've just committed a fix for that). With the default inetd.conf, after sending a mail to myself: # inetd -d ADD: 127.0.0.1:comsat proto=udp, wait.max=1.256 user:group=root:wheel builtin =0 server=/usr/libexec/comsat ADD: ::1:comsat proto=udp6, wait.max=1.256 user:group=root:wheel builtin=0 se rver=/usr/libexec/comsat ADD: daytime proto=tcp, wait.max=0.256 user:group=root:wheel builtin=1959e0e0 8630 server=internal ADD: daytime proto=tcp6, wait.max=0.256 user:group=root:wheel builtin=1959e0e 08630 server=internal someone wants comsat 14937 execv /usr/libexec/comsat The last two lines appeared right after sending the email. I understand (in my ignorance) that means inetd *receives* the notification (from mail.local?). And the following is what netstat shows: Correct, mail.local sends a message to the comsat port which inetd listens on. Then inetd will exec comsat with the socket hooked up to standard input and output. I know biff isn't a big concern but I insisted because I thought it could be a symptom of some other more important issue. The root cause was that mail.local sends a newline character after the spool file offset which comsat was not expecting. This used to work but got broken by the conversion to strtonum(). I've committed a fix for comsat similar to the diff I send earlier. - todd
Re: NFS encoding?
Looks like there is no resolution but replacement. Thanks. Yes, some overly generalised statements follow. A worthy endeavour is to educate your users or use tools that prevent the problem. Unless the entire software stack from the lowest level is encoding aware and understands and carries correctly the complete information in your preferred encoding end to end, you're inevitably going to have problems at some stage or abstraction layer. The reliable solution is to use the common denominator in carrying names (any information) between software implementation. As majority of the software is alpha-numeric English symbols aware (only) including the language used for programming, logically either convert it all to your encoding (properly end to end, portable) or use a naming scheme that is a subset of your encoding to match the common denominator. In simple words: use 7-bit old school ASCII. There are packages to help you convert, or simply start over. Another attempt at this is UTF-8, which may not solve it for you or create a new set of problems. No matter nfs, cifs or whatever (future (proof (really))) protocol you use, this problem will always be present and simply resolved by not creating the use cases outside generic symbol usage.
Re: X error: Maximum number of clients reached
On 07/06/15 22:43, luke...@onemodel.org wrote: I'm on OpenBSD 5.7 amd64, w/ all the latest stable patches. When I simply launch xfce (from ports), an xterm, and ~34 xedit windows, I get: Maximum number of clients reachedError: Can't open display: :0.0. I think I also had the same problem earlier when running fvwm instead of xfce. I've searched thru code (not yet exhaustively), searched the mailing lists, the web with DuckDuckGo(DDG), and tried various things. Most DDG search results talk about buggy apps, or closing windows, but I don't think that's my problem as I don't have that many windows open. Three of the search results say this (though the info could be old, by several years or more): By default, the X server has a limit of just 128. In order to increase this limit, you need to run at least Solaris 8 or an earlier release with the Xserver patch applies that fixes bug: 4185418 the X server should support more connections .Then change the Xservers configuration file and add the -clients 1024 option to the X commandline. However, I've passed -clients 1024 to the startx command with no effect, and I don't see that as a parameter in 'man X' or 'man Xservers'. Maybe that parameter needs to go in a config file somewhere, but I'm floundering at this point in the X config stuff. When I searched through the xenocara code, I found that the error comes from xserver/os/connection.c, where a constant NOROOM contains the error message, and interesting functions being called include AllocNewConnection, ErrorConnMax, and InitConnectionLimits which is where the variable MaxClients is being set. When I opened enough xedit windows to reproduce the error, just now, then closed one of them and ran xwininfo -root -children|wc I got a result of 213. Then I killed those 17 xedit windows (I have other things open now also) and xwininfo -root -children|wc said 94. That's about as far as I've got, since I'm new enough with this to be unsure whether I'm going in a good direction, diagnostically; my ignorance might be causing this to take longer than needed, and I'm hoping not to have to run X in gdb I don't see anything interesting in /var/log/messages or in Xorg.0.log: I think it's all just repeated output telling me it un- and re-found my external USB mouse and keyboard. Should I use sendbug for this? Any ideas appreciated. Thanks!! Luke This might be login.conf / ulimit (man ksh) issue... Fred
X error: Maximum number of clients reached
I'm on OpenBSD 5.7 amd64, w/ all the latest stable patches. When I simply launch xfce (from ports), an xterm, and ~34 xedit windows, I get: Maximum number of clients reachedError: Can't open display: :0.0. I think I also had the same problem earlier when running fvwm instead of xfce. I've searched thru code (not yet exhaustively), searched the mailing lists, the web with DuckDuckGo(DDG), and tried various things. Most DDG search results talk about buggy apps, or closing windows, but I don't think that's my problem as I don't have that many windows open. Three of the search results say this (though the info could be old, by several years or more): By default, the X server has a limit of just 128. In order to increase this limit, you need to run at least Solaris 8 or an earlier release with the Xserver patch applies that fixes bug: 4185418 the X server should support more connections .Then change the Xservers configuration file and add the -clients 1024 option to the X commandline. However, I've passed -clients 1024 to the startx command with no effect, and I don't see that as a parameter in 'man X' or 'man Xservers'. Maybe that parameter needs to go in a config file somewhere, but I'm floundering at this point in the X config stuff. When I searched through the xenocara code, I found that the error comes from xserver/os/connection.c, where a constant NOROOM contains the error message, and interesting functions being called include AllocNewConnection, ErrorConnMax, and InitConnectionLimits which is where the variable MaxClients is being set. When I opened enough xedit windows to reproduce the error, just now, then closed one of them and ran xwininfo -root -children|wc I got a result of 213. Then I killed those 17 xedit windows (I have other things open now also) and xwininfo -root -children|wc said 94. That's about as far as I've got, since I'm new enough with this to be unsure whether I'm going in a good direction, diagnostically; my ignorance might be causing this to take longer than needed, and I'm hoping not to have to run X in gdb Any ideas appreciated. Thanks!! Luke
Re: X error: Maximum number of clients reached
On 7/6/15, luke...@onemodel.org luke...@onemodel.org wrote: I'm on OpenBSD 5.7 amd64, w/ all the latest stable patches. When I simply launch xfce (from ports), an xterm, and ~34 xedit windows, I get: Maximum number of clients reachedError: Can't open display: :0.0. I think I also had the same problem earlier when running fvwm instead of xfce. these threads might interest you: freedesktop-xorg-devel: [PATCH RFC] configurable maximum number of clients http://marc.info/?t=14328287932r=1w=2 [PATCH RFC xserver v2] configurable maximum number of clients http://marc.info/?l=freedesktop-xorg-develm=143291631231526w=2 [PATCH v3] configurable maximum number of clients http://marc.info/?t=14333428952r=1w=2 --patrick I've searched thru code (not yet exhaustively), searched the mailing lists, the web with DuckDuckGo(DDG), and tried various things. Most DDG search results talk about buggy apps, or closing windows, but I don't think that's my problem as I don't have that many windows open. Three of the search results say this (though the info could be old, by several years or more): By default, the X server has a limit of just 128. In order to increase this limit, you need to run at least Solaris 8 or an earlier release with the Xserver patch applies that fixes bug: 4185418 the X server should support more connections .Then change the Xservers configuration file and add the -clients 1024 option to the X commandline. However, I've passed -clients 1024 to the startx command with no effect, and I don't see that as a parameter in 'man X' or 'man Xservers'. Maybe that parameter needs to go in a config file somewhere, but I'm floundering at this point in the X config stuff. When I searched through the xenocara code, I found that the error comes from xserver/os/connection.c, where a constant NOROOM contains the error message, and interesting functions being called include AllocNewConnection, ErrorConnMax, and InitConnectionLimits which is where the variable MaxClients is being set. When I opened enough xedit windows to reproduce the error, just now, then closed one of them and ran xwininfo -root -children|wc I got a result of 213. Then I killed those 17 xedit windows (I have other things open now also) and xwininfo -root -children|wc said 94. That's about as far as I've got, since I'm new enough with this to be unsure whether I'm going in a good direction, diagnostically; my ignorance might be causing this to take longer than needed, and I'm hoping not to have to run X in gdb I don't see anything interesting in /var/log/messages or in Xorg.0.log: I think it's all just repeated output telling me it un- and re-found my external USB mouse and keyboard. Should I use sendbug for this? Any ideas appreciated. Thanks!! Luke
X error: Maximum number of clients reached
I'm on OpenBSD 5.7 amd64, w/ all the latest stable patches. When I simply launch xfce (from ports), an xterm, and ~34 xedit windows, I get: Maximum number of clients reachedError: Can't open display: :0.0. I think I also had the same problem earlier when running fvwm instead of xfce. I've searched thru code (not yet exhaustively), searched the mailing lists, the web with DuckDuckGo(DDG), and tried various things. Most DDG search results talk about buggy apps, or closing windows, but I don't think that's my problem as I don't have that many windows open. Three of the search results say this (though the info could be old, by several years or more): By default, the X server has a limit of just 128. In order to increase this limit, you need to run at least Solaris 8 or an earlier release with the Xserver patch applies that fixes bug: 4185418 the X server should support more connections .Then change the Xservers configuration file and add the -clients 1024 option to the X commandline. However, I've passed -clients 1024 to the startx command with no effect, and I don't see that as a parameter in 'man X' or 'man Xservers'. Maybe that parameter needs to go in a config file somewhere, but I'm floundering at this point in the X config stuff. When I searched through the xenocara code, I found that the error comes from xserver/os/connection.c, where a constant NOROOM contains the error message, and interesting functions being called include AllocNewConnection, ErrorConnMax, and InitConnectionLimits which is where the variable MaxClients is being set. When I opened enough xedit windows to reproduce the error, just now, then closed one of them and ran xwininfo -root -children|wc I got a result of 213. Then I killed those 17 xedit windows (I have other things open now also) and xwininfo -root -children|wc said 94. That's about as far as I've got, since I'm new enough with this to be unsure whether I'm going in a good direction, diagnostically; my ignorance might be causing this to take longer than needed, and I'm hoping not to have to run X in gdb I don't see anything interesting in /var/log/messages or in Xorg.0.log: I think it's all just repeated output telling me it un- and re-found my external USB mouse and keyboard. Should I use sendbug for this? Any ideas appreciated. Thanks!! Luke
Re: SOHO IPv6 router problems
On Mon, Jul 06, 2015 at 03:51:04PM +, Christian Weisgerber wrote: FWIW, this scheme is specified here: TR-187: IPv6 for PPP Broadband Access https://www.broadband-forum.org/technical/download/TR-187.pdf Thanks for the information! There is no PPP involved in our situation but otherwise it seems to match what we are working with. -- Patrik Lundin
Re: NFS encoding?
Looks like there is no resolution but replacement. Thanks. http://superuser.com/questions/302407/what-to-do-with-nfs-server-utf-8-and-wi ndows-7 Best regards, Zhi-Qiang Lei On Jul 6, 2015, at 1:56 PM, Johan Petersson vhdlni...@gmail.com wrote: i really wish i could help you out - my girlfriend lives in hong kong so i understand the need to display chinese chars, i do. i have ran NFS for years, but only in a pure UNIX environment - bsd-versions, linux and osx. but i'm not any kind of NFS expert - i'd have to suggest that you try to read as many man-pages as you can. or check out the NFS source code. once you know the encoding, put the question to Microsoft. or simply stop using windows haha good luck! /Johan On Mon, Jul 6, 2015 at 7:36 AM, Zhi-Qiang Lei zhiqiang@gmail.com mailto:zhiqiang@gmail.com wrote: Is there such encoding option in NFS setting? And what encoding does OpenBSD used as default for filenames? Thanks for your suggestion though. Best regards, Zhi-Qiang Lei On Jul 6, 2015, at 1:02 PM, Johan Petersson vhdlni...@gmail.com mailto:vhdlni...@gmail.com wrote: that is not a question for the OpenBSD people if you ask me. win7 is junk, go ask microsoft this kind of questions On Mon, Jul 6, 2015 at 6:58 AM, Zhi-Qiang Lei zhiqiang@gmail.com mailto:zhiqiang@gmail.com wrote: I have an OpenBSD 5.6 server with NFS enabled. When I mount it on my Mac and Raspberry Pi, everything is fine. However, when I map it on Windows 7, all the filenames with Chinese in them cannot be displayed correctly. How can I fix this? Thanks. Best regards, Zhi-Qiang Lei
Re: SOHO IPv6 router problems
On 2015-06-30, Patrik Lundin pat...@sigterm.se wrote: The setup looks like this: We are supposed to get a default route on the outside interface (em0), using autoconf, and then recieve an IPv6 prefix on the inside (em1) using DHCP6-PD (prefix delegation). FWIW, this scheme is specified here: TR-187: IPv6 for PPP Broadband Access https://www.broadband-forum.org/technical/download/TR-187.pdf -- Christian naddy Weisgerber na...@mips.inka.de
Re: comsat-biff issue
Hello Todd, On Mon, Jul 06, 2015 at 06:37:24AM -0600, Todd C. Miller wrote: Is your mail being delivered to /var/mail/yourname or do you have a .forward file? The comsat daemon is notified by mail.local which delivers mail to the local mail spool. If you have a .forward file, mail.local is not used and you won't get a biff notification. Till you mentioned about it I've ignored the existence of /usr/libexec/mail.local. :-) I'm a new to OpenBSD. Is it some kind of procmail's alike functionality? My configuration is almost the after-install defaults. There's just a /root/.forward created at install time pointing to my user. I thought about it, I tried removing that .forward file and removing aliases I'd added later and logged in *only* root user I sent email from root to root to find out if some variable set in my ~/.kshrc or ~/.profile could be interfering. I tried modifying the comsat line in inetd.conf, using just udp4, removing the ip limit prefix, etc. I've tried installing procmail (telling smtpd to use it). I did some tests stopping /etc/rc.d/inetd and running inetd -d form the command line. With the default inetd.conf, after sending a mail to myself: # inetd -d ADD: 127.0.0.1:comsat proto=udp, wait.max=1.256 user:group=root:wheel builtin=0 server=/usr/libexec/comsat ADD: ::1:comsat proto=udp6, wait.max=1.256 user:group=root:wheel builtin=0 server=/usr/libexec/comsat ADD: daytime proto=tcp, wait.max=0.256 user:group=root:wheel builtin=1959e0e08630 server=internal ADD: daytime proto=tcp6, wait.max=0.256 user:group=root:wheel builtin=1959e0e08630 server=internal someone wants comsat 14937 execv /usr/libexec/comsat The last two lines appeared right after sending the email. I understand (in my ignorance) that means inetd *receives* the notification (from mail.local?). And the following is what netstat shows: # netstat -a -p udp Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) udp 0 0 localhost.biff *.* udp 0 0 *.syslog *.* Active Internet connections (including servers) Proto Recv-Q Send-Q Local Address Foreign Address(state) udp6 0 0 localhost.biff *.* udp6 0 0 *.syslog *.* And that's all that came to my mind (I've tried also opening and closing my living room's window several times :-)). I know biff isn't a big concern but I insisted because I thought it could be a symptom of some other more important issue. - todd Walter -- PLEASE, LET'S PRESERVE GOOD EMAIL PRACTICES - Use plain text (no HTML please). - Separate paragraphs with empty lines. - Use hard wrapped lines at no more than 72 columns. - Avoid top-posting. - You'll find the above easy to accomplish by using a decent email client (i.e. Thunderbird, Claws mail, Mutt).
Re: comsat-biff issue
It looks like this is fallout from the strtonum() conversion in
comsat. The issue is that mail.local writes a trailing newline
after the offset that we need to trim. This fixes it.
- todd
Index: libexec/comsat/comsat.c
===
RCS file: /cvs/src/libexec/comsat/comsat.c,v
retrieving revision 1.39
diff -u -p -u -r1.39 comsat.c
--- libexec/comsat/comsat.c 18 Apr 2015 18:28:37 - 1.39
+++ libexec/comsat/comsat.c 6 Jul 2015 14:56:23 -
@@ -191,6 +191,7 @@ doreadutmp(void)
}
(void)lseek(uf, 0, SEEK_SET);
nutmp = read(uf, utmp, statbf.st_size)/sizeof(struct utmp);
+ dsyslog(LOG_DEBUG, read %d utmp entries, nutmp);
}
(void)alarm(15);
}
@@ -204,15 +205,22 @@ mailfor(char *name)
char *cp;
off_t offset;
+ dsyslog(LOG_DEBUG, mail for '%s', name);
+ cp = name + strlen(name) - 1;
+ while (cp name isspace((unsigned char)*cp))
+ *cp-- = '\0';
if (!(cp = strchr(name, '@')))
return;
*cp = '\0';
offset = strtonum(cp + 1, 0, LLONG_MAX, errstr);
- if (errstr)
+ if (errstr) {
+ syslog(LOG_ERR, '%s' is %s, cp + 1, errstr);
return;
+ }
while (--utp = utmp) {
memcpy(utname, utp-ut_name, UT_NAMESIZE);
utname[UT_NAMESIZE] = '\0';
+ dsyslog(LOG_DEBUG, check %s against %s, name, utname);
if (!strncmp(utname, name, UT_NAMESIZE))
notify(utp, offset);
}
