Hi!
Im using two FreeBSD machines trying to get iSCSI to work and it works
allright, but extremley slow. It peaks at about 50MB/s if I have
multiple dd's runningt against the target.
I have two separate networks but I get no difference in speed whichever
I use. One regular 1G network connect
On 11/19/2012 02:48 PM, Daniel Braniss wrote:
try increasing the tag opening - see camcontrol(8)
danny
I tried camcontrol tags daX -N 32 (and a few different values) but cant
see any change in speeds.
(pass25:iscsi0:0:0:0): dev_openings 30
(pass25:iscsi0:0:0:0): dev_active2
(pass25:i
>
> On 11/19/2012 02:48 PM, Daniel Braniss wrote:
> > try increasing the tag opening - see camcontrol(8)
> >
> > danny
> >
> >
> >
> I tried camcontrol tags daX -N 32 (and a few different values) but cant
> see any change in speeds.
>
> (pass25:iscsi0:0:0:0): dev_openings 30
> (pass25:iscsi0:0:
I run a nightly ports tree update and I have been getting the following
errors the last couple of days. I haven't seen this asked before so is
this just me or is anyone else seeing this? Have I fat-fingered
something?
Updating '/usr/ports':
Skipped '/usr/ports/astro' -- Node remains in confl
On 14.11.2012, at 11:50, Markus Gebert wrote:
> On 14.11.2012, at 08:21, Konstantin Belousov wrote:
>
>> On Wed, Nov 14, 2012 at 01:41:04AM +0100, Markus Gebert wrote:
>>>
>>> On 13.11.2012, at 19:30, Markus Gebert wrote:
>>>
To me it looks like the unix socket GC is triggered way too
Hey all,
The FAQ for FreeBSD needs a significant amount of updating and
changing. The first step in that process is to figure out what needs
to be changed.
If you can a take a moment and thoroughly review just one
question and add your comments and concerns it
would be immensely helpful.
http:/
On Mon, Nov 19, 2012 at 8:28 AM, Frank Seltzer wrote:
> I run a nightly ports tree update and I have been getting the following
> errors the last couple of days. I haven't seen this asked before so is this
> just me or is anyone else seeing this? Have I fat-fingered something?
>
> Updating '/usr
On Mon, Nov 19, 2012 at 9:44 AM, Eitan Adler wrote:
> Hey all,
>
> The FAQ for FreeBSD needs a significant amount of updating and
> changing. The first step in that process is to figure out what needs
> to be changed.
>
> If you can a take a moment and thoroughly review just one
> question and a
On Mon, Nov 19, 2012 at 9:44 AM, Eitan Adler wrote:
> Hey all,
>
> The FAQ for FreeBSD needs a significant amount of updating and
> changing. The first step in that process is to figure out what needs
> to be changed.
>
> If you can a take a moment and thoroughly review just one
> question and a
On Mon, 19 Nov 2012, Kevin Oberman wrote:
On Mon, Nov 19, 2012 at 8:28 AM, Frank Seltzer wrote:
I run a nightly ports tree update and I have been getting the following
errors the last couple of days. I haven't seen this asked before so is this
just me or is anyone else seeing this? Have I
On 11/19/12 18:44, Eitan Adler wrote:
Hey all,
The FAQ for FreeBSD needs a significant amount of updating and
changing. The first step in that process is to figure out what needs
to be changed.
If you can a take a moment and thoroughly review just one
question and add your comments and concern
On 11/19/12 18:44, Eitan Adler wrote:
Hey all,
The FAQ for FreeBSD needs a significant amount of updating and
changing. The first step in that process is to figure out what needs
to be changed.
If you can a take a moment and thoroughly review just one
question and add your comments and concern
19.11.2012, 22:04, "Andrea Venturoli" :
> On 11/19/12 18:44, Eitan Adler wrote:
>
>> Hey all,
>>
>> The FAQ for FreeBSD needs a significant amount of updating and
>> changing. The first step in that process is to figure out what needs
>> to be changed.
>>
>> If you can a take a moment and t
UNCLASSIFIED
Hi,
Could this be an indication of the recent security incident:
http://www.freebsd.org/news/2012-compromise.html
ie, non-svn modifications to a svn repository have occurred?
Greg.
-Original Message-
From: owner-freebsd-sta...@freebsd.org
[mailto:owner-freebsd-sta...@free
Svn says it sees conflicts. Best thing is to view what the conflicts are
using 'svn status' and 'svn diff'. That might shine some more light on
this case.
Ronald.
On Mon, 19 Nov 2012 23:35:11 +0100, Robinson, Greg
wrote:
UNCLASSIFIED
Hi,
Could this be an indication of the recent sec
On Mon, Nov 19, 2012 at 11:37 AM, Frank Seltzer wrote:
>
>
> On Mon, 19 Nov 2012, Kevin Oberman wrote:
>
>> On Mon, Nov 19, 2012 at 8:28 AM, Frank Seltzer
>> wrote:
>>>
>>> I run a nightly ports tree update and I have been getting the following
>>> errors the last couple of days. I haven't seen
On Mon, 19 Nov 2012, Kevin Oberman wrote:
On Mon, Nov 19, 2012 at 11:37 AM, Frank Seltzer wrote:
On Mon, 19 Nov 2012, Kevin Oberman wrote:
On Mon, Nov 19, 2012 at 8:28 AM, Frank Seltzer
wrote:
I run a nightly ports tree update and I have been getting the following
errors the last coup
On 19 November 2012 21:43, Frank Seltzer wrote:
>
>
> On Mon, 19 Nov 2012, Kevin Oberman wrote:
>
>> On Mon, Nov 19, 2012 at 11:37 AM, Frank Seltzer
>> wrote:
>>>
>>>
>>>
>>> On Mon, 19 Nov 2012, Kevin Oberman wrote:
>>>
On Mon, Nov 19, 2012 at 8:28 AM, Frank Seltzer
wrote:
>
>
On Mon, 19 Nov 2012, Eitan Adler wrote:
It's now up to 24.
Updating '/usr/ports':
Skipped '/usr/ports/mail' -- Node remains in conflict
Skipped '/usr/ports/net' -- Node remains in conflict
Skipped '/usr/ports/multimedia' -- Node remains in conflict
Skipped '/usr/ports/dns' -- Node remains in
On 2012-Nov-19 23:12:33 -0500, Frank Seltzer wrote:
>On Mon, 19 Nov 2012, Eitan Adler wrote:
>> did you run svn checkout on a directory which wasn't controlled by svn
>> (with stuff in it?). If so you need to remove those directories and
>> run "svn up".
>
>No, svn created the directory. I moved
On Mon, 19 Nov 2012 14:37:00 -0500 (EST)
Frank Seltzer wrote:
>
>
> On Mon, 19 Nov 2012, Kevin Oberman wrote:
>
> > On Mon, Nov 19, 2012 at 8:28 AM, Frank Seltzer
> > wrote:
> >> I run a nightly ports tree update and I have been getting the
> >> following errors the last couple of days. I ha
21 matches
Mail list logo
