On Mon, 2 May 2016 00:01+0200, Wolfgang Zenker wrote:
> Hi,
>
> after updating some 10-STABLE systems a few days ago, I noticed that on
> two of those systems bsnmpd started to use up a lot of cpu time, and the
> available memory shrinked until rendering the system unusable. Killing
> bsnmpd stop
Hi all,
Some time ago I resorted to setting up a Jail to support my
SqueezeBox system: the version in ports (audio/squeezeboxserver)
is not current, and needs an old version of mysql and an old
version of perl. A Jail seemed like the right answer. For a
while it worked OK (for small values of OK
Dear all,
on a quite fresh vanilla (read: GENERIC)
FreeBSD 10.2-RELEASE-p14 (amd64)
I get many CommVault-related warnings (ioctl sign-extension ioctl) similar to
those discussed for ages related to Python (June 2010 and before).
This only happens on amd64, not on the previously used i386 sys
> On May 1, 2016, at 9:07 AM, Trond Endrestøl
> wrote:
>
> On Wed, 27 Apr 2016 13:46-0400, Scott Long wrote:
>
>> Thanks for the report. I might be mistaken, but the default system
>> is not configured to direct devd messages to user.info, so I didn’t
>> see this during my development. How
"-q" is only really intended for embedded systems that don't use the
standard syslogd or that are extremely concerned about syslogd's pipe
bandwidth and/or CPU usage. Most people should control devd's chattiness
with /etc/syslog.conf. This setting is good for most people. It will log
actions dev
On Mon May 2 15:44:19 UTC 2016 Tomoaki AOKI wrote:
> Hi.
>
> Today I encountered this problem on stable/10 and could determine the
> problematic commit is r298920, "Update file to 5.26".
>
> This commit is MFC of r298192, and reverting it fixes the issue on
> head, too.
>
> What I did (for stab
Hi!
> I get many CommVault-related warnings (ioctl sign-extension
> ioctl) similar to those discussed for ages related to Python (June
> 2010 and before).
It seems this is a general problem, but mostly on the application
side. See for example:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=1
Hi!
> It seems this is a general problem, but mostly on the application
> side. See for example:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=147938
>
> which shows that the application code uses the wrong type
> for an ioctl argument.
See
/usr/src/sys/kern/sys_generic.c:sys_ioctl()
On Tue, Apr 19, 2016 at 12:46:54PM +0200, Edward Tomasz Napierała wrote:
> On 0419T0906, Melissa Jenkins wrote:
> > I've been trying to get reboot -r to work but get an error that
> > kern.proc.pathname is undefined. It then drops to single user mode.
> > Interestingly I've checked the value of k
Hi,
I upgraded my laptop and Wifi stopped working.
It still worked on:
May 2 20:11:13 sjakie kernel: FreeBSD 11.0-CURRENT #8 r296724M: Sun Mar
13 16:03:31 CET 2016
but broke on:
May 2 20:24:53 sjakie kernel: FreeBSD 11.0-CURRENT #9 r298900M: Mon May
2 05:00:46 CEST 2016.
I booted the o
[line lengths recovered]
On Sunday, 1 May 2016 at 20:16:38 -0700, Jordan Hubbard wrote:
>
>> On May 1, 2016, at 5:49 PM, Warren Block wrote:
>>
>> The first quarter of 2016 showed that FreeBSD retains a strong sense of
>> ipseity. Improvements were pervasive, lending credence to the concept
On Mon, 2 May 2016 11:28-0600, Alan Somers wrote:
> "-q" is only really intended for embedded systems that don't use the
> standard syslogd or that are extremely concerned about syslogd's pipe
> bandwidth and/or CPU usage. Most people should control devd's chattiness
> with /etc/syslog.conf. Thi
12 matches
Mail list logo
