At system startup, the init script is run with limits calculated on the
basis of the core MAXFILES.
After you run sysctl limits of the system may be altered, for example
kern.maxfilesperproc, but the script will continue to work with the old
values.
This is bad in two ways:
1. When using the
This is not my personal problem, this in: /etc/rc.subr
if [ -n $_user ]; then
_doit=su -m $_user -c 'sh -c \$_doit\'
fi
--
Rozhuk Ivan
-Original Message-
From: owner-freebsd-hack...@freebsd.org [mailto:owner-freebsd-
hack...@freebsd.org] On Behalf Of Joerg Sonnenberger
ioctl(FIONREAD)
-Original Message-
From: owner-freebsd-hack...@freebsd.org [mailto:owner-freebsd-
hack...@freebsd.org] On Behalf Of Ivan Voras
Sent: Sunday, April 08, 2012 6:17 AM
To: freebsd-hackers
Subject: Socket buffer usage
Hi,
I'm tracking down an obscure bug in my
My EeePC netbook shows for the two SSD:
$ uname -a
FreeBSD tiny 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r226986: Tue Nov 1
14:27:40 CET 2011 guru@caracas:/usr/obj/usr/src/sys/GENERIC i386
$ gpart show
= 63 7880481 ada0 MBR (3.8G)
63 7880481 1 freebsd [active]
Hi, All!
I've fixed many warnings: warning: 'XXX' may be used uninitialized in this
function
PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=168979
But there are still warning: - param large-function-growth limit reached
[-Winline] and sometimes the compiler just crashes with errors:
{standard
# install
gpart create -s GPT ada1
gpart show
gpart add -i 1 -t freebsd-boot -b 40 -s 512 ada1
gpart add -i 2 -t freebsd-ufs -b 552 -s . ada1
gpart bootcode -b /boot/pmbr ada1
gpart bootcode -p /boot/gptboot -i 1 ada1
# for data
gpart create -s GPT ada1
gpart show
gpart add -i 1 -t
I updated amdtemp and now I need your help with testing.
Now the driver should support all AMD processors.
For a family of 15h and 16h, not all sensors are available - for my system
does not find drivers for ati SMBus, and other systems based on the AMD I
have not.
/*-
* Copyright (c) 2008,
7 matches
Mail list logo