On Wed, Feb 03, 2010 at 05:25:03PM -0800, Pyun YongHyeon wrote:
> On Thu, Feb 04, 2010 at 11:52:55AM +1300, Jonathan Chen wrote:
> > On Tue, Feb 02, 2010 at 11:20:29PM +0200, Nikos Ntarmos wrote:
> > > On Wed, Feb 03, 2010 at 08:36:16AM +1300, Jonathan Chen wrote:
> > > > Hi,
> > > >
> > > > I've
On Thu, Feb 04, 2010 at 11:52:55AM +1300, Jonathan Chen wrote:
> On Tue, Feb 02, 2010 at 11:20:29PM +0200, Nikos Ntarmos wrote:
> > On Wed, Feb 03, 2010 at 08:36:16AM +1300, Jonathan Chen wrote:
> > > Hi,
> > >
> > > I've noticed that on a recent 8-STABLE/amd64, scp(1) appears to be
> > > stalling
On Tue, Feb 02, 2010 at 11:20:29PM +0200, Nikos Ntarmos wrote:
> On Wed, Feb 03, 2010 at 08:36:16AM +1300, Jonathan Chen wrote:
> > Hi,
> >
> > I've noticed that on a recent 8-STABLE/amd64, scp(1) appears to be
> > stalling very frequently. This is the output from a "scp -v -v"
> > of a 300Mb file
Hello.
After migrating to 8.0-STABLE from 7.2-STABLE my messages output starts
getting interleaved (see below). I'm running amd64 smp kernel. Is there
anything can be done to get rid of this? Thanks in advance.
Feb 3 19:44:49 tiger named[989]: running
Feb 3 19:44:50 tiger ntpd[1179]: ntpd 4
En/na Mikolaj Golub ha escrit:
> On Fri, 29 Jan 2010 12:37:52 +0100 Gustau Pérez wrote:
>
>
>> Hi,
>>
>> I'm using cacti to monitor some servers running FBSD. I was using 7.2
>> with SCHED_4BSD. With this configuration : bsnmpd+bsnmp-ucd was
>> returning right values for the cores' load.
>>
On Wed, Feb 03, 2010 at 01:33:15PM +0100, Jordi Espasa Clofent wrote:
> HI all,
>
> I'm hardening one test box and at present I'm planning to do:
>
> # chflags -R schg
>
> where will be some binaries that seems to be common targets
> for rootkits and lammers:
>
> ls
> du
> ps
> find
> top
> l
HI all,
I'm hardening one test box and at present I'm planning to do:
# chflags -R schg
where will be some binaries that seems to be common targets for
rootkits and lammers:
ls
du
ps
find
top
locate
strings
ifconfig
netstat login
I wonder if changing these files permissions as I've shown
On 02/03/2010 12:12 PM, Bruce Simpson wrote:
On 02/02/2010 17:19, Jordi Espasa Clofent wrote:
In FreeBSD we've nice(1), renice(8) and even rtprio, idprio(1) but if
I'm understanding correctly, they're related to CPU priorty only, not
to I/O.
That's not entirely true.
A thread's CPU priority
On 02/02/2010 17:19, Jordi Espasa Clofent wrote:
In FreeBSD we've nice(1), renice(8) and even rtprio, idprio(1) but if
I'm understanding correctly, they're related to CPU priorty only, not
to I/O.
That's not entirely true.
A thread's CPU priority is still going to affect its ability to be
Dan Naumov wrote:
> [j...@atombsd ~]$ dd if=/dev/zero of=/home/jago/test2 bs=1M count=4096
> 4096+0 records in
> 4096+0 records out
> 4294967296 bytes transferred in 143.878615 secs (29851325 bytes/sec)
>
> This works out to 1GB in 36,2 seconds / 28,2mb/s in the first test and
> 4GB in 143.8 second
kern/143521
2010/2/2 pluknet :
> Hi.
>
> I've got NMI on an almost idle system - FreeBSD 7.2-R amd64.
> I guess the reason may be in (hardware?) binary garbage
> seen once in a while on serial port (loader, then ttyd0).
> Ask me for more details.
>
> Tracing command swi4: clock sio pid 20 tid 1000
11 matches
Mail list logo