Date: Wed, 12 Oct 2016 12:54:10 +0200 (CEST) From: =?ISO-8859-1?Q?Trond_Endrest=F8l?= <Trond.Endrestol@fagskolen.gjovik.no> To: FreeBSD questions <freebsd-questions@freebsd.org> Subject: interfaces.ifTable.ifEntry.ifOutOctets always zero for xn(4) Message-ID: <alpine.BSF.2.20.1610121249310.45618@mail.fig.ol.no>
next in thread | raw e-mail | index | archive | help
Does anyone know why interfaces.ifTable.ifEntry.ifOutOctets is always zero for xn(4)? This happens on XenServer 7.0.0 with stable/11 r306639 as the guest. Running MRTG in conjunction with net-mgmt/net-snmp gives me zero for the counter for the outgoing octets, while the counter for the incoming octets ticks away as it should. Is this a bug in the xn(4) driver? -- +-------------------------------+------------------------------------+ | Vennlig hilsen, | Best regards, | | Trond Endrestøl, | Trond Endrestøl, | | IT-ansvarlig, | System administrator, | | Fagskolen Innlandet, | Gjøvik Technical College, Norway, | | tlf. mob. 952 62 567, | Cellular...: +47 952 62 567, | | sentralbord 61 14 54 00. | Switchboard: +47 61 14 54 00. | +-------------------------------+------------------------------------+ From owner-freebsd-questions@freebsd.org Wed Oct 12 12:12:37 2016 Return-Path: <owner-freebsd-questions@freebsd.org> Delivered-To: freebsd-questions@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 614EBC0ED9A for <freebsd-questions@mailman.ysv.freebsd.org>; Wed, 12 Oct 2016 12:12:37 +0000 (UTC) (envelope-from jkeen@verizon.net) Received: from vms173025pub.verizon.net (vms173025pub.verizon.net [206.46.173.25]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 44373AB5 for <freebsd-questions@freebsd.org>; Wed, 12 Oct 2016 12:12:37 +0000 (UTC) (envelope-from jkeen@verizon.net) Received: from vz-proxy-l001.mx.aol.com ([64.236.82.153]) by vms173025.ctn.ui.verizon.net (Oracle Communications Messaging Server 7.0.5.32.0 64bit (built Jul 16 2014)) with ESMTPA id <0OEX009CALSENWA0@vms173025.ctn.ui.verizon.net> for freebsd-questions@freebsd.org; Wed, 12 Oct 2016 06:12:15 -0500 (CDT) X-CMAE-Score: 0 X-CMAE-Analysis: v=2.2 cv=EKN26xRC c=1 sm=1 tr=0 a=FJ1kTJ0/xm5uTekQe8vMdQ==:117 a=N659UExz7-8A:10 a=CH0kA5CcgfcA:10 a=dXkyNnQV6H2Towv8ym4A:9 a=pILNOxqGKmIA:10 Received: by 71.246.118.77 with SMTP id 704a2f45; Wed, 12 Oct 2016 11:12:15 GMT Subject: Re: $PS1 does not render command-line prompt in color in a FreeBSD VM To: freebsd-questions@freebsd.org References: <d2b31340-dac9-fb6a-ba31-1ec8ac3707e2@verizon.net> <20161012050817.0f11b749.freebsd@edvax.de> From: James E Keenan <jkeen@verizon.net> Message-id: <8971b5d8-0e97-c1eb-711c-d9fc5628a279@verizon.net> Date: Wed, 12 Oct 2016 07:12:14 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-version: 1.0 In-reply-to: <20161012050817.0f11b749.freebsd@edvax.de> Content-type: text/plain; charset=windows-1252; format=flowed Content-transfer-encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions/>; List-Post: <mailto:freebsd-questions@freebsd.org> List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:freebsd-questions-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 12 Oct 2016 12:12:37 -0000 On 10/11/2016 11:08 PM, Polytropon wrote: > On Tue, 11 Oct 2016 21:56:05 -0400, James E Keenan wrote: >> This question concerns display of colors in the command-line prompt on >> two different FreeBSD installations. >> >> For a couple of months I have been using VirtualBox 5.1.2 to run >> FreeBSD-10.3 as a guest on an Ubuntu Linux 16.04 LTS host. When working >> in this VM I have been trying to avoid Linuxisms so as to better learn >> how to work in a BSD environment. One case: I'm using Bourne shell >> rather than Bash as the shell for my own user. > > Side note: the Bourne shell (/bin/sh) is FreeBSD's default scripting > shell, but it's a poor dialog shell, that's why this task is usually > reserved for the C shell (a tcsh in fact), which is recommended for > interactive use (and not as bad as people often assume). > > > >> In my .shrc file, I have >> this assignment for the spelling and color of my command-line prompt: >> >> PS1="[^[[31m\W^[[0m] \$ " >> >> ... where in each of two cases the '^[' is the ESCAPE character \033. >> This produces a prompt which I can verbally describe as: >> >> open-bracket in white; basename of pwd in red; close-bracket, space, >> dollar-sign, space in white >> >> ... which in the terminal looks like: >> >> [jkeenan] $ >> >> where 'jkeenan' is in red and all the rest is in white. So far so good. >> >> Yesterday I installed FreeBSD-11 as a VM on the same Linux host -- only >> this time I switched to using VMWare to house the VM. I brought over my >> .profile, .shrc, .vimrc, etc., files from the 10.3 VM to this new one. >> I expected them to Just Work. However the terminal inside the VMWare >> console seems to be unable to digest the codes for color in the >> assignment to $PS1. That value for $PS1 is rendering as: >> >> [[31mjkeenan[0m] $ >> >> ... all rendered in white; nothing in red. The control sequences to >> change from white to red and back again are simply being literally >> displayed. >> >> I should note that the VMWare console is perfectly capable of rendering >> different colors. Vim gets nice colors in syntax highlighting for both >> sh and perl. >> >> Does anyone have a clue as to why $PS1 DWIMs on FreeBSD-10.3 in >> VirtualBox while FreeBSD-11.0 does not in VMWare? > > Has there been a change to the shell, is the configuration file > somehow "damaged", or are you using some nonstandard $TERM setting > (or other setting in a relevant file) in that specific combination? > No, as stated above, I copied over the .shrc file from one FreeBSD VM to another. I did so with all the other relevant config files. So I'm trying to determine why that file is processed differently in the two environments. > Hint: It helps to "diff .shrc.works .shrc.doesnot" and look for > the PS1 setting output (which there ideally should be none). > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.20.1610121249310.45618>