X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:to:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=q+bPv815yOZWZryL
	+HLMbYKWX5Q/Q459Mpo42GJriInxN1JzzjavCZjAjBXeGx2BAaG0ApkfPvSxIXol
	I5sQCla5xUyaskrItM2iD+575CfJPzy+yltK3PbyAekTooHHzoqTz60zpcYj3cO2
	1VN5Z061Hcp2G9qURk9M+fiGDNo=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:references:to:reply-to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=GQ8oHl/yVQfI+Cp+KIu3Nu
	Vjn30=; b=a+7YNsvxAsgABiNwkGH/yVUOIg0rrMvhBBwTEr4DNuxdCBt3HBRjfC
	budSUV+o1P81SwdGSaOTrkP55UTACY9+YOSb/cmR+W5yz3NR+X1WnLZ/d5QyUwkE
	13LiF7CBDw54gZAn4W3SP6EXiFFdnYLfdoMkjcaF29P7yRa5OXkKY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=andrey, Repin, repin, Andrey
X-HELO: smtp-out-so.shaw.ca
X-Authority-Analysis: v=2.2 cv=F5wnTupN c=1 sm=1 tr=0 a=WqCeCkldcEjBO3QZneQsCg==:117 a=WqCeCkldcEjBO3QZneQsCg==:17 a=IkcTkHD0fZMA:10 a=xzGy4ndpJ4Z6idkXywUA:9 a=QEXdDO2ut3YA:10
Subject: Re: $ uptime: bad data in /proc/loadavg
References: <258891239.20170513054453@yandex.ru>
To: cygwin@cygwin.com
Reply-To: Brian.Inglis@SystematicSw.ab.ca
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Message-ID: <e7555476-f160-5a9f-4241-dff07810fcbc@SystematicSw.ab.ca>
Date: Fri, 12 May 2017 21:41:00 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <258891239.20170513054453@yandex.ru>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfEqQQW/2CIvnfynxOrK60viOb/Ilw0OpvxR5PvlBprn+a/BT4VSBidM5dx4VhdRe5REbhK0o9O/q32vbVrjHzWSkLaqe1f9O05XZrzD0gcO0uNJ2KLIr h2MK4YczoS7wkIDQaJi5p2rLh3nHlgo+0DFg7HYprWp+wwX50gveeZo2RtftihcAbXG+67U1ONVB4w==
X-IsSubscribed: yes

On 2017-05-12 20:44, Andrey Repin wrote:
> Just a few days ago it worked, but now
> $ uptime
> bad data in /proc/loadavg
> $ cat /proc/loadavg
> 0,00 0,00 0,00 1/3

Something is localizing output from /proc/loadavg 
- assume you're using ru locale? 
Check if you also get it with uptime -p or uptime -s. 
Was there a bug report about not localizing /proc 
or some similar output recently? 

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

