Re: HAL must die!
On Fri, 18 Mar 2011 22:36:41 +0100, Michel Talon ta...@lpthe.jussieu.fr wrote: How many new features of FreeBSD are correctly documented presently? Features of the FreeBSD OS are typically well documented. This high quality affects all kind of documentation, be it the handbook FAQ, as well as the manpages that are available for system binaries, kernel interfaces, library calls, configuration files and system operations. Also see the high quality of the source code which is, due to its style and content (and its comment) also a source of documentation, mainly designed for programmers instead of end users. HAL, on the other hand, is obsolete as well as not part of the FreeBSD operating system. It's a separate port. Many ports do follow the quality approach for documentation, see man xmms, man mplayer or even man opera for examples. Many modern software does not provide documentation in the standard way, try man firefox or any KDE program. In some cases, documentation is left to the users and scattered across the Internet in web pages and Wikis. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: HAL must die!
On 03/19/11 17:18, Polytropon wrote: On Fri, 18 Mar 2011 22:36:41 +0100, Michel Talonta...@lpthe.jussieu.fr wrote: How many new features of FreeBSD are correctly documented presently? Features of the FreeBSD OS are typically well documented. This high quality affects all kind of documentation, be it the handbook FAQ, as well as the manpages that are available for system binaries, kernel interfaces, library calls, configuration files and system operations. Also see the high quality of the source code which is, due to its style and content (and its comment) also a source of documentation, mainly designed for programmers instead of end users. HAL, on the other hand, is obsolete as well as not part of the FreeBSD operating system. It's a separate port. Many ports do follow the quality approach for documentation, see man xmms, man mplayer or even man opera for examples. Many modern software does not provide documentation in the standard way, try man firefox or any KDE program. In some cases, documentation is left to the users and scattered across the Internet in web pages and Wikis. Thats what I love about FBSD- the documentation is better than any other system out there, in the handbook but the man pages are the most comprehensive. Its these ports where there is little to no documentation at all thats the problem. One thing I'd like to do is thank the port maintainers- even when the app itself may have no man page, some maintainers have taken the care to document a man page (or at least a doc under share/) themselves where they can. Very thoughtful! A point to make regards HAL is there is next to nix in complete and/or understandable documentation anywhere for it. Obsolete or not, that is a bad case... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: HAL must die!
On Sat, 19 Mar 2011 18:18:58 +1000, Da Rock freebsd-questi...@herveybayaustralia.com.au wrote: Thats what I love about FBSD- the documentation is better than any other system out there, in the handbook but the man pages are the most comprehensive. Fully agree. As a developer, I like to simply man whatever to find out more about it, and if the manpage doesn't answer my questions in detail, I'll find them in the source code which is very tidy and well commented. Quality is more important to the FreeBSD developers than sheer quantity, followed by planned obsolescence. This one of the MAIN points that makes FreeBSD superior to most competitors out there. Its these ports where there is little to no documentation at all thats the problem. Without the intention to sound impolite: This seems to be a tradition coming from modern Linux. As programs advance that fast, nobody has the time (or feels the need) to adopt documentation properly. One thing I'd like to do is thank the port maintainers- even when the app itself may have no man page, some maintainers have taken the care to document a man page (or at least a doc under share/) themselves where they can. Very thoughtful! Sometimes, programs offer -h or --help to give at least a clue about command line parameters to accomplish things you can't do via the program's interface. An example ois OpenOffice: openoffice.org-3.0.0-swriter -h provides such a short overview. A point to make regards HAL is there is next to nix in complete and/or understandable documentation anywhere for it. Obsolete or not, that is a bad case... Obsolete / incomplete / incorrect / unusable documentation equals NO documentation - especially from a user's point of view. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: User authentication on Linux with FreeBSD OpenLDAP backend fails: pam_ldap: error trying to bind as user/Failed password for
On 03/18/11 17:02, Dan Nelson wrote: In the last episode (Mar 18), O. Hartmann said: I try to use a FreeBSD OpenLDAP (FreeBSD 8.2-STABLE/amd64, most recent OpenLDAP/openldap-sasl-server-2.4.24) as an authentication backend for an UBUNTU 10.10 server (using openldap 2.4.23). Most of the installation on the Ubuntu server has been successfully done (I'm not familiar with Linux, but it seems that things like pam and ldap are quite similar to FreeBSD's installation). From the Linux/Ubuntu server, I'm able to get all users and groups via 'getent passwd' and 'getent group', even 'id' on an OpenLDAP backed up user is successfully. But when it comes to a login via sshd, login fails with this error (loged on Linux Ubuntu in /var/log/auth.log): Mar 18 12:01:00 freyja sshd[26824]: Failed password for testuser from 192.168.0.128 port 40734 ssh2 Mar 18 12:01:23 freyja sshd[26854]: pam_ldap: error trying to bind as user uid=testuser,ou=users,dc=geoinf,dc=freyja,dc=com (Confidentiality required) Confidentiality required means that the server is refusing to authenticate over a non-encrypted connection. Try switching pam_ldap to ldaps (in your pam ldap.conf, either change your uri lines to ldaps:// or add the line ssl on) and see if that works. Well, I tried several things now and I do not understand this world anymore :-( For short again: The conceptional setup I use is a working concept within all FreeBSD boxes around here autheticating users via our OpenLDAP server, also ran by FreeBSD (8.2-STABLE/amd64). On the Linux/Ubuntu 10.10 server I tried the following: ldapsearch: ldap_sasl_interactive_bind_s: Confidentiality required (13) additional info: TLS confidentiality required ldapsearch -xZ: ...listing of the DIT of the LDAP server looking up an user ID definitely within the DIT: positive response from the LDAP server. I also can obtain passwd/group informations via getent passwd/group. I also checked the connection to the LDAPserver with the SSL credetials by openssl s_client -connect LDAPserver:636 -showcerts and receive a lot of informations CONNECTED(0003) depth=1 /C [...] verify error:num=19:self signed certificate in certificate chain verify return:0 --- Certificate chain 0 s:/C=DE/ST [...] -BEGIN CERTIFICATE- MIIDljCCAv+gAwIBA [...] -END CERTIFICATE- 1 s:/C [...] i:/C=DE [...] -BEGIN CERTIFICATE- MIIDojCC[...] -END CERTIFICATE- --- Server certificate subject=/C [...] issuer=/C [...] --- No client certificate CA names sent --- SSL handshake has read 2175 bytes and written 421 bytes --- New, TLSv1/SSLv3, Cipher is AES256-SHA Server public key is 2048 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1 Cipher: AES256-SHA Session-ID: 2FCAD4AAFD18AD13013AE6A8BFF872036DAC94174F0DE626E8FF0C7F98FC7EE3 Session-ID-ctx: Master-Key: X Key-Arg : None TLS session ticket: - b5 48 c7 cc 09 99 fb a5-0e 1e 75 1b 4f aa a1 69 .Hu.O..i 0010 - 37 a5 4f c7 [...] Start Time: 1300547707 Timeout : 300 (sec) Verify return code: 19 (self signed certificate in certificate chain) --- I guess this signals everything is all right with the certificate connecting via SSL/TLS. I'm not familiar with Linux/Ubuntu's PAM setup, the setup has been done via apt-get/installation of the appropriate tools and facilities (ldap, pam_ldap, nss_ldap). I've no idea what's going wrong ... There is also some kind of weirdness around here. While login in via ssh (or better: trying to login via ssh), I received this: Mar 19 16:44:39 freyja sshd[1625]: Did not receive identification string from 125.88.109.121 Mar 19 16:44:40 freyja sshd[1623]: Failed password for ohartmann from XXX.XXX.XXX.XXX port 52686 ssh2 Mar 19 16:45:01 freyja CRON[1626]: pam_unix(cron:session): session opened for user root by (uid=0) Mar 19 16:45:01 freyja CRON[1626]: pam_unix(cron:session): session closed for user root IP 125.88.109.121 is located in China, 125.88.109.121 Server Details IP address: 125.88.109.121 Server Location: Guangzhou, Guangdong in China ISP: ChinaNet Guangdong Province Network ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Freebsd Firefox problems
I have finally managed to solve this issue. Upgrading to 8.2 didn't solve anything. But after I installed ccache I decided to recompile all my installed ports in the hope that it solved my problems. After recompiling all my ports (1000 ports, including openoffice). The problem still persisted. But after reading another thread I removed pulse audio support from libcanberra and this solved the problem. I first removed gstreamer support as well but this does not cause the problem. Regards, Sander On 07/10/10 09:37, Hartmann, O. wrote: On 07/10/10 02:46, Sander Janssen wrote: Hello, I am currently having the same problems you were having with firefox 3.6 on FreeBSD in February (I found the threads on the Freebsd-Ports mailing list). The thread doesn't seem to come up with an answer and I am wondering if you managed to solve the problem? I am talking about firefox crashing when you use a context menu. I have tried a portupgrade -Rf firefox to try to recompile every depency but nothing has any effect. In my case thunderbird works correctly. Any information would be useful. Thanks in advance, Sander Hello. I have still this obscure problems. When gettext was updated and we have had to update any dependend port, within this procedure Firefox 3.6 worked correctly as expected. But after the update was performed, everything remained as it was before. I did several times portmaster -f (which is the same as -R with portupgrade) to build every necessary port, but with no effect. I also performed the one-day-taking gettext update and, additionaly, I recompiled every port (nearly 1000 on my systems). No effect. When delegating the client firefox to another X terminal, say to my workstation at home (login with ssh -Y for X11 portforwarding), no problems occur, so I guess the problem is riggered by X11 on the local machine and especially with the ATI radeonhd driver (which does not work correctly on many boxes and with low end Radeon HD 46XX or 47XX cards). I have no idea. I use Opera for now on the machine in question. Regards, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Freebsd Firefox problems
On 03/19/11 16:37, Sander Janssen wrote: I have finally managed to solve this issue. Upgrading to 8.2 didn't solve anything. But after I installed ccache I decided to recompile all my installed ports in the hope that it solved my problems. After recompiling all my ports (1000 ports, including openoffice). The problem still persisted. But after reading another thread I removed pulse audio support from libcanberra and this solved the problem. I first removed gstreamer support as well but this does not cause the problem. Regards, Sander my installation of libcanberra doesn't have pulse-audio enabled anymore since enabling pulse-audio support in several other libs and apps resulted in problems updating via portmaster (as far as I can recall). At this very moment, my firefox seems to be ok. Regards, Oliver On 07/10/10 09:37, Hartmann, O. wrote: On 07/10/10 02:46, Sander Janssen wrote: Hello, I am currently having the same problems you were having with firefox 3.6 on FreeBSD in February (I found the threads on the Freebsd-Ports mailing list). The thread doesn't seem to come up with an answer and I am wondering if you managed to solve the problem? I am talking about firefox crashing when you use a context menu. I have tried a portupgrade -Rf firefox to try to recompile every depency but nothing has any effect. In my case thunderbird works correctly. Any information would be useful. Thanks in advance, Sander Hello. I have still this obscure problems. When gettext was updated and we have had to update any dependend port, within this procedure Firefox 3.6 worked correctly as expected. But after the update was performed, everything remained as it was before. I did several times portmaster -f (which is the same as -R with portupgrade) to build every necessary port, but with no effect. I also performed the one-day-taking gettext update and, additionaly, I recompiled every port (nearly 1000 on my systems). No effect. When delegating the client firefox to another X terminal, say to my workstation at home (login with ssh -Y for X11 portforwarding), no problems occur, so I guess the problem is riggered by X11 on the local machine and especially with the ATI radeonhd driver (which does not work correctly on many boxes and with low end Radeon HD 46XX or 47XX cards). I have no idea. I use Opera for now on the machine in question. Regards, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shell script termination with exit function in backquotes
On Mon, Mar 14, 2011 at 6:40 PM, Andres Perera andre...@zoho.com wrote:
On Mon, Mar 14, 2011 at 7:46 AM, Maxim Khitrov m...@mxcrypt.com wrote:
On Mon, Mar 14, 2011 at 3:16 AM, Andres Perera andre...@zoho.com wrote:
On Sun, Mar 13, 2011 at 9:49 PM, Devin Teske dte...@vicor.com wrote:
If you make the changes that I've suggested, you'll have consistent
execution. The reason you're having inconsistent behavior is because Linux
has /bin/sh symbolically linked to /bin/bash while FreeBSD has a more
traditional shell (we'll call it bourne shell plus).
that is misleading because command substitutions have traditionally
invoked subshells, and freebsd sh(1)/ash is an exception, not the norm
in this case, ksh and bash deviates are clearly closer to standard
bourne behaviour
Thanks for that explanation. I can understand the benefits of
optimizing away subshell execution, but that can clearly lead to
unexpected behavior. Is there some documentation on when this
optimization is utilized (i.e. the command executed without a
subshell)? Would I be correct in assuming that it is only restricted
to built-in commands that are known not to produce any output, such as
'exit'?
i would check the source, autoconf docs, and http://www.in-ulm.de/~mascheck/
netbsd has been patched to fix `exit 1`, according to the last site
Here's another, but related, problem that I just ran into. The man page reads:
Commands may be grouped by writing either
(list)
or
{ list; }
The first form executes the commands in a subshell. Note that built-in
commands thus executed do not affect the current shell...
Here's my script:
#!/bin/sh
{ A=1; }; echo $A
echo | { B=2; }; echo $B
{ C=3; } /dev/null; echo $C
And here's the output:
1
3
Where did the '2' go? Again, I have to assume that when stdin is piped
to a group of commands, those commands are executed in a subshell
despite curly braces. But where is this behavior documented? It seems
that there are a lot of corner cases that can only be understood if
you are familiar with the shell implementation. Documentation can
certainly be improved in places.
- Max
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shell script termination with exit function in backquotes
On Mar 19, 2011, at 9:15 AM, Maxim Khitrov wrote:
On Mon, Mar 14, 2011 at 6:40 PM, Andres Perera andre...@zoho.com wrote:
On Mon, Mar 14, 2011 at 7:46 AM, Maxim Khitrov m...@mxcrypt.com wrote:
On Mon, Mar 14, 2011 at 3:16 AM, Andres Perera andre...@zoho.com wrote:
On Sun, Mar 13, 2011 at 9:49 PM, Devin Teske dte...@vicor.com wrote:
If you make the changes that I've suggested, you'll have consistent
execution. The reason you're having inconsistent behavior is because
Linux has /bin/sh symbolically linked to /bin/bash while FreeBSD has a
more traditional shell (we'll call it bourne shell plus).
that is misleading because command substitutions have traditionally
invoked subshells, and freebsd sh(1)/ash is an exception, not the norm
in this case, ksh and bash deviates are clearly closer to standard
bourne behaviour
Thanks for that explanation. I can understand the benefits of
optimizing away subshell execution, but that can clearly lead to
unexpected behavior. Is there some documentation on when this
optimization is utilized (i.e. the command executed without a
subshell)? Would I be correct in assuming that it is only restricted
to built-in commands that are known not to produce any output, such as
'exit'?
i would check the source, autoconf docs, and http://www.in-ulm.de/~mascheck/
netbsd has been patched to fix `exit 1`, according to the last site
Here's another, but related, problem that I just ran into. The man page reads:
Commands may be grouped by writing either
(list)
or
{ list; }
The first form executes the commands in a subshell. Note that built-in
commands thus executed do not affect the current shell...
Here's my script:
#!/bin/sh
{ A=1; }; echo $A
echo | { B=2; }; echo $B
{ C=3; } /dev/null; echo $C
And here's the output:
1
3
Where did the '2' go?
You're learning that there are deviations to the rule as-mentioned in the
man-page.
At least two variations to the rule that { ... } is a block of commands
executed in the current shell are:
1. When the block appears as a function and
2. When the block appears on the right-hand side of a pipe (with or without
following pipe(s)).
The reason for these deviations is quite simple in-fact...
The shell needs to create a new set of stdin/stdout file-descriptors for the
block of commands that you've created, and executing said commands within a
sub-shell achieves that.
I hope that helps explain.
--
Devin
Again, I have to assume that when stdin is piped
to a group of commands, those commands are executed in a subshell
despite curly braces. But where is this behavior documented? It seems
that there are a lot of corner cases that can only be understood if
you are familiar with the shell implementation. Documentation can
certainly be improved in places.
- Max
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shell script termination with exit function in backquotes
On Sat, Mar 19, 2011 at 12:44 PM, Devin Teske dte...@vicor.com wrote:
On Mar 19, 2011, at 9:15 AM, Maxim Khitrov wrote:
On Mon, Mar 14, 2011 at 6:40 PM, Andres Perera andre...@zoho.com wrote:
On Mon, Mar 14, 2011 at 7:46 AM, Maxim Khitrov m...@mxcrypt.com wrote:
On Mon, Mar 14, 2011 at 3:16 AM, Andres Perera andre...@zoho.com wrote:
On Sun, Mar 13, 2011 at 9:49 PM, Devin Teske dte...@vicor.com wrote:
If you make the changes that I've suggested, you'll have consistent
execution. The reason you're having inconsistent behavior is because
Linux has /bin/sh symbolically linked to /bin/bash while FreeBSD has a
more traditional shell (we'll call it bourne shell plus).
that is misleading because command substitutions have traditionally
invoked subshells, and freebsd sh(1)/ash is an exception, not the norm
in this case, ksh and bash deviates are clearly closer to standard
bourne behaviour
Thanks for that explanation. I can understand the benefits of
optimizing away subshell execution, but that can clearly lead to
unexpected behavior. Is there some documentation on when this
optimization is utilized (i.e. the command executed without a
subshell)? Would I be correct in assuming that it is only restricted
to built-in commands that are known not to produce any output, such as
'exit'?
i would check the source, autoconf docs, and http://www.in-ulm.de/~mascheck/
netbsd has been patched to fix `exit 1`, according to the last site
Here's another, but related, problem that I just ran into. The man page
reads:
Commands may be grouped by writing either
(list)
or
{ list; }
The first form executes the commands in a subshell. Note that built-in
commands thus executed do not affect the current shell...
Here's my script:
#!/bin/sh
{ A=1; }; echo $A
echo | { B=2; }; echo $B
{ C=3; } /dev/null; echo $C
And here's the output:
1
3
Where did the '2' go?
You're learning that there are deviations to the rule as-mentioned in the
man-page.
I've learned this a long time ago :)
My point is that these deviations should be noted in the man page to
help eliminate such surprises. A single sentence would have sufficed
in this case.
The reason for these deviations is quite simple in-fact...
The shell needs to create a new set of stdin/stdout file-descriptors for the
block of commands that you've created, and executing said commands within a
sub-shell achieves that.
Something very similar to this should be noted in the man page. I
figured out why my code wasn't working quickly after thinking about
how data would be piped to stdin. Others may waste a lot of time
trying to figure out why their code doesn't do what the man page
states it should be doing.
- Max
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: User authentication on Linux with FreeBSD OpenLDAP backend fails: pam_ldap: error trying to bind as user/Failed password for
On 03/18/11 17:02, Dan Nelson wrote: In the last episode (Mar 18), O. Hartmann said: I try to use a FreeBSD OpenLDAP (FreeBSD 8.2-STABLE/amd64, most recent OpenLDAP/openldap-sasl-server-2.4.24) as an authentication backend for an UBUNTU 10.10 server (using openldap 2.4.23). Most of the installation on the Ubuntu server has been successfully done (I'm not familiar with Linux, but it seems that things like pam and ldap are quite similar to FreeBSD's installation). From the Linux/Ubuntu server, I'm able to get all users and groups via 'getent passwd' and 'getent group', even 'id' on an OpenLDAP backed up user is successfully. But when it comes to a login via sshd, login fails with this error (loged on Linux Ubuntu in /var/log/auth.log): Mar 18 12:01:00 freyja sshd[26824]: Failed password for testuser from 192.168.0.128 port 40734 ssh2 Mar 18 12:01:23 freyja sshd[26854]: pam_ldap: error trying to bind as user uid=testuser,ou=users,dc=geoinf,dc=freyja,dc=com (Confidentiality required) Confidentiality required means that the server is refusing to authenticate over a non-encrypted connection. Try switching pam_ldap to ldaps (in your pam ldap.conf, either change your uri lines to ldaps:// or add the line ssl on) and see if that works. I managed it! My FreeBSD OpenLDAP-server have had in it's config DIT (cn=config) the follwoing entries, which seems to confuse Linux (but not the FreeBSD clients, no matter why): olcSecurity: simple_bind=256 After reducing this security strenth value down to olcSecurity: simple_bind=128 everything works fine so far. At the moment, I have no explanation for this. Either FreeBSD clients are always binding with a higher security strength level or ignoring this. Thanks, Oliver ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shell script termination with exit function in backquotes
Maxim Khitrov m...@mxcrypt.com wrote: ... these deviations should be noted in the man page to help eliminate such surprises. A single sentence would have sufficed in this case. As always, I'm sure patches would be welcome :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
tcp/ip failures with fbsd 8.2 386 on ESX 4.1
FreeBSD 8.2 32-bit ESXi 4.1 em0 driver to the ESXi Intel emulation syslog-ng 2.0.10 em0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether 00:50:56:90:00:01 inet a.b.c.85 netmask 0xffe0 broadcast a.b.c.95 media: Ethernet autoselect (1000baseT full-duplex) status: active We've be running FreeBSD 7.x for a couple of years on ESXi 4.0 and 4.1 with no problems. We're having tcp/ip failures with 8.2 as syslog-ng server. trafshow shows aggregate port 514 traffic hitting peaks of about 25K char/sec. After sometimes many hours of the syslog-ng VM server running well, monit from other machines signals port 514 is down, up, down, up. this is confirmed by other machines with nmap a.b.c.d -p 514 -sU ... showing closed, open, closed, etc. syslog-ng logging for all syslog clients stops more or less simultaneously. trafshow filtered for port 514 shows udp packets arriving, but instead of showing the source and destinations by PTR domain name, it switches to showing their IPs. to test the external DNS, on the syslog-ng VM, we try dig @recursive.server -x a.b.c.d and get no response. Other machines query the recursive server successfully. Without rebooting the FreeBSD VM, we do /etc/rc.d/netif restart /etc/rc.d/routing restart which allows full operation. dmesg and messages show no errors. Suggestions? Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: tcp/ip failures with fbsd 8.2 386 on ESX 4.1
Maybe try disabling dns lookups within syslog-ng? - Original Message - From: Len Conrad [mailto:lcon...@go2france.com] Sent: Saturday, March 19, 2011 05:40 PM To: freebsd-questions@freebsd.org freebsd-questions@freebsd.org Subject: tcp/ip failures with fbsd 8.2 386 on ESX 4.1 FreeBSD 8.2 32-bit ESXi 4.1 em0 driver to the ESXi Intel emulation syslog-ng 2.0.10 em0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether 00:50:56:90:00:01 inet a.b.c.85 netmask 0xffe0 broadcast a.b.c.95 media: Ethernet autoselect (1000baseT full-duplex) status: active We've be running FreeBSD 7.x for a couple of years on ESXi 4.0 and 4.1 with no problems. We're having tcp/ip failures with 8.2 as syslog-ng server. trafshow shows aggregate port 514 traffic hitting peaks of about 25K char/sec. After sometimes many hours of the syslog-ng VM server running well, monit from other machines signals port 514 is down, up, down, up. this is confirmed by other machines with nmap a.b.c.d -p 514 -sU ... showing closed, open, closed, etc. syslog-ng logging for all syslog clients stops more or less simultaneously. trafshow filtered for port 514 shows udp packets arriving, but instead of showing the source and destinations by PTR domain name, it switches to showing their IPs. to test the external DNS, on the syslog-ng VM, we try dig @recursive.server -x a.b.c.d and get no response. Other machines query the recursive server successfully. Without rebooting the FreeBSD VM, we do /etc/rc.d/netif restart /etc/rc.d/routing restart which allows full operation. dmesg and messages show no errors. Suggestions? Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: tcp/ip failures with fbsd 8.2 386 on ESX 4.1
Maybe try disabling dns lookups within syslog-ng? - Original Message - From: Len Conrad [mailto:lcon...@go2france.com] Sent: Saturday, March 19, 2011 05:40 PM To: freebsd-questions@freebsd.org freebsd-questions@freebsd.org Subject: tcp/ip failures with fbsd 8.2 386 on ESX 4.1 FreeBSD 8.2 32-bit ESXi 4.1 em0 driver to the ESXi Intel emulation syslog-ng 2.0.10 em0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST metric 0 mtu 1500 options=9bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM ether 00:50:56:90:00:01 inet a.b.c.85 netmask 0xffe0 broadcast a.b.c.95 media: Ethernet autoselect (1000baseT full-duplex) status: active We've be running FreeBSD 7.x for a couple of years on ESXi 4.0 and 4.1 with no problems. We're having tcp/ip failures with 8.2 as syslog-ng server. trafshow shows aggregate port 514 traffic hitting peaks of about 25K char/sec. After sometimes many hours of the syslog-ng VM server running well, monit from other machines signals port 514 is down, up, down, up. this is confirmed by other machines with nmap a.b.c.d -p 514 -sU ... showing closed, open, closed, etc. syslog-ng logging for all syslog clients stops more or less simultaneously. trafshow filtered for port 514 shows udp packets arriving, but instead of showing the source and destinations by PTR domain name, it switches to showing their IPs. to test the external DNS, on the syslog-ng VM, we try dig @recursive.server -x a.b.c.d and get no response. Other machines query the recursive server successfully. Without rebooting the FreeBSD VM, we do /etc/rc.d/netif restart /etc/rc.d/routing restart which allows full operation. dmesg and messages show no errors. Suggestions? Len the failure just happened again. this time ssh sessions, like the one running trafshow, are cut off. ssh again gets connection refused on another machine running a looping, logging script of nmap a.b.c.d -p 514 -sU show port 514 open It seems like the tcp/ip or em0 driver gets screwed up. Len ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org font size=1 div style='border:none;border-bottom:double windowtext 2.25pt;padding:0in 0in 1.0pt 0in' /div This email is intended to be reviewed by only the intended recipient and may contain information that is privileged and/or confidential. If you are not the intended recipient, you are hereby notified that any review, use, dissemination, disclosure or copying of this email and its attachments, if any, is strictly prohibited. If you have received this email in error, please immediately notify the sender by return email and delete this email from your system. /font ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Shell script termination with exit function in backquotes
On Sat, Mar 19, 2011 at 11:45 AM, Maxim Khitrov m...@mxcrypt.com wrote:
Here's another, but related, problem that I just ran into. The man page reads:
Commands may be grouped by writing either
(list)
or
{ list; }
The first form executes the commands in a subshell. Note that built-in
commands thus executed do not affect the current shell...
and it also says that the rhs in a pipe is always executed in a subshell
Here's my script:
#!/bin/sh
{ A=1; }; echo $A
echo | { B=2; }; echo $B
{ C=3; } /dev/null; echo $C
And here's the output:
1
3
Where did the '2' go? Again, I have to assume that when stdin is piped
to a group of commands, those commands are executed in a subshell
despite curly braces. But where is this behavior documented? It seems
that there are a lot of corner cases that can only be understood if
you are familiar with the shell implementation. Documentation can
certainly be improved in places.
this time it's a case of you not being familiar, and not violations of
principle of least suprise like ash command substitutions
the only broadly deployed shells that do not execute the (whole) rhs
in a subshell are ksh and descendants, and even then there are many
exceptions
the bracket grouping is irrelevant
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
