On Monday 24 September 2007 20:58, Artem Kuchin wrote:
> > What i don't understand is why timer rate on each cpu is 1995? I have
> > set it to 1000, not 1995 or 2000. I have seen it showing 2000 on
> > another box.
> > So
> > 1) why not 1000?
I can only make assumptions about the doubling, and I
FreeBSD 6.2-STABLE (GENERIC SMP kernel rebuild from today sources) does
not launch second core of Pentium Dual Core e2160 CPU, it detects the
cores [Cores per package: 2] but it does not launch the second CPU
[SMP: AP CPU #1 Launched! <-- this should pop in dmesg but it doesnt]
How can I help you
Nikos Vassiliadis wrote:
On Monday 24 September 2007 20:58, Artem Kuchin wrote:
What i don't understand is why timer rate on each cpu is 1995? I
have set it to 1000, not 1995 or 2000. I have seen it showing 2000
on another box.
So
1) why not 1000?
I can only make assumptions about the doublin
On Tuesday 25 September 2007 12:13, Artem Kuchin wrote:
> I have dual CPU with HT. If i turn on HT (and it does help in my case)
> it shoud 2000 int x4 = 8000 ints per second. SO, i have saved 200
> int/second from NIC and got myself 8000 ints/second from timer.
This kind of load(200intrs/s) earn
Nikos Vassiliadis wrote:
On Tuesday 25 September 2007 12:13, Artem Kuchin wrote:
I have dual CPU with HT. If i turn on HT (and it does help in my
case) it shoud 2000 int x4 = 8000 ints per second. SO, i have saved
200 int/second from NIC and got myself 8000 ints/second from timer.
This kind of
On Mon, Sep 24, 2007 at 09:29:08AM -0400, Victor Star wrote:
> ==- 8<
> -
> fireball# ldd /usr/lib/pam_unix.so
> /usr/lib/pam_unix.so:
> libutil.so.5 => /lib/libutil.so.5 (0x28167000)
> libcrypt.so.3 => /lib/li
Artem Kuchin wrote:
> I enabled device polling in the kernel, in nics and
> set HZ=1000.
HZ=1000 is the default anyway. You only need to set it
if you want a value other than 1000.
For example, on my notebook I have set HZ=600 because that
machine often used for various media playback (video).
vermaden <[EMAIL PROTECTED]> wrote:
> FreeBSD 6.2-STABLE (GENERIC SMP kernel rebuild from today sources) does
> not launch second core of Pentium Dual Core e2160 CPU, it detects the
> cores [Cores per package: 2] but it does not launch the second CPU
> [SMP: AP CPU #1 Launched! <-- this should
3) Is timer int really generated on each cpu? Am i really wasting cpu
time on ~4000 ints per second?
4000 ints per second is rather nothing on any modern CPU.
Have a look at the top(1) display of an otherwise idle
system. The "%interrupt" column should be zero, even if
it's processing 4000 time
Artem Kuchin wrote:
> Oliver Fromme wrote:
> > Artem Kuchin wrote:
> > > 3) Is timer int really generated on each cpu? Am i really wasting
> > > cpu time on ~4000 ints per second?
> >
> > 4000 ints per second is rather nothing on any modern CPU.
> > Have a look at the top(1) display of an o
Hi,
Today I noticed the following behaviour on a 6-stable
machine:
$ cd /tmp
$ mkdir -p foo/var
$ cd foo/bar
$ rm -rf ../
rm: ../: Invalid argument
$ rm -rf ../
$
Note that the command "rm -rf ../" was entered twice.
The first time I got an error message (and exit code 1),
the second time it ap
On 9/25/07, Oliver Fromme <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Today I noticed the following behaviour on a 6-stable
> machine:
>
> $ cd /tmp
> $ mkdir -p foo/var
> $ cd foo/bar
> $ rm -rf ../
> rm: ../: Invalid argument
> $ rm -rf ../
> $
>
> Note that the command "rm -rf ../" was entered twice.
>
I just did a firmware upgrade on my Dell 2850 FreeBSD server. I'm seeing the
following warnings at boot time. (I am not sure that they weren't there before
the firmware upgrade.)
Should I be worried about this? And if so, what do I need to do...
Thanks!
Copyright (c) 1992-2006 The FreeBSD
On Tue, Sep 25, 2007 at 05:12:50PM +0200, Oliver Fromme wrote:
> Hi,
>
> Today I noticed the following behaviour on a 6-stable
> machine:
>
> $ cd /tmp
> $ mkdir -p foo/var
> $ cd foo/bar
Looks like you have mistyped 'mkdir' argument :)
> $ rm -rf ../
> rm: ../: Invalid argument
Please type
On Tue, 25 Sep 2007 17:12:50 +0200 (CEST)
Oliver Fromme <[EMAIL PROTECTED]> wrote:
> $ cd /tmp
> $ mkdir -p foo/var
> $ cd foo/bar
> $ rm -rf ../
> rm: ../: Invalid argument
> $ rm -rf ../
> $
>
> Note that the command "rm -rf ../" was entered twice.
> The first time I got an error message (and
Hello,
Sorry if this is off-topic here, but I want to ask few questions about
the cvs that is in FreeBSD base system.
We have project that is in cvs and we uses different branches.
I want to separate permitions for different developers, and to allow all
of them to commit
changes in HEAD, but
On Tue, 25 Sep 2007, Oliver Fromme wrote:
> Note that the command "rm -rf ../" was entered twice.
> The first time I got an error message (and exit code 1),
> the second time it apparently succeeded.
Check the man page for rm:
-f Attempt to remove the files without prompting for conf
Oliver Fromme wrote:
Artem Kuchin wrote:
Oliver Fromme wrote:
Artem Kuchin wrote:
3) Is timer int really generated on each cpu? Am i really wasting
cpu time on ~4000 ints per second?
4000 ints per second is rather nothing on any modern CPU.
Have a look at the top(1) display of an otherwise i
Torfinn Ingolfsen wrote:
> Oliver Fromme wrote:
>
> > $ cd /tmp
> > $ mkdir -p foo/var
> > $ cd foo/bar
> > $ rm -rf ../
> > rm: ../: Invalid argument
> > $ rm -rf ../
> > $
> >
> > Note that the command "rm -rf ../" was entered twice.
> > The first time I got an error message (and e
Hi Mike,
Now, before I got a chance to try it out it suddenly works again.
As good of a new as it is, I don't really like things fixing themselves without
my knowledge of
what's going on... Looks like a good time to start learning about rootkits. Of
course there is a
possibility of some resource
Artem Kuchin wrote:
> Oliver Fromme wrote:
>> Artem Kuchin wrote:
>>> Oliver Fromme wrote:
Artem Kuchin wrote:
> 3) Is timer int really generated on each cpu? Am i really wasting
> cpu time on ~4000 ints per second?
4000 ints per second is rather nothing on any modern CPU.
I think this is a bug, here is a fix obtained from NetBSD.
The reasoning (from NetBSD's rm.c,v 1.16):
Strip trailing slashes of operands in checkdot().
POSIX.2 requires that if "." or ".." are specified as the basename
portion of an operand, a diagnostic message be written to standard
error, etc
* Oliver Fromme <[EMAIL PROTECTED]> [2007-09-25 19:43 +0200]:
> By the way, an additional confusion is that ".." and "../"
> are handled differently. Specifying ".." always leads to
> this message:
>
> rm: "." and ".." may not be removed
>
> and nothing is actually removed. It is confusing that
Nicolas Rachinsky wrote:
> Oliver Fromme wrote:
> > By the way, an additional confusion is that ".." and "../"
> > are handled differently. Specifying ".." always leads to
> > this message:
> >
> > rm: "." and ".." may not be removed
> >
> > and nothing is actually removed. It is confus
Oliver Fromme wrote:
> Nicolas Rachinsky wrote:
> > Oliver Fromme wrote:
> > > By the way, an additional confusion is that ".." and "../"
> > > are handled differently. Specifying ".." always leads to
> > > this message:
> > >
> > > rm: "." and ".." may not be removed
> > >
> > > and not
Hi,
On Tue, Sep 25, 2007 at 11:25:34AM -0400, Maxim Khitrov wrote:
> On 9/25/07, Oliver Fromme <[EMAIL PROTECTED]> wrote:
> > To add further confusion, another "rm -rf ../" does
> > not print an error message and seemingly succeeds,
> > even though ".." does not exist anymore in the current
> > di
Hello!
On Tue, Sep 25, 2007 at 11:54:14PM +0200, Oliver Brandmueller wrote:
> In sh:
>
> $ which rm
> /bin/rm
> $ cd /tmp
> $ mkdir -p foo/bar
> $ cd foo/bar
> $ rm -rf ../
> rm: ../: Invalid argument
$ pwd
/tmp
$ ktrace -i /bin/sh
$ which rm
/bin/rm
$ mkdir -p foo/bar
$ cd foo/bar
$ rm -rf ../
--On Tuesday, September 25, 2007 8:49 AM +0200 Søren Schmidt
<[EMAIL PROTECTED]> wrote:
Yarema wrote:
Hi, I need some help recovering from this. First some back story.
Running 6.2-STABLE i386 from Sep 17, 2007. My /home slice is mounted
from /dev/ar0s1e where the relevant kernel messages loo
On 9/25/07, Oliver Fromme <[EMAIL PROTECTED]> wrote:
> Torfinn Ingolfsen wrote:
> > Oliver Fromme wrote:
> >
> > > $ cd /tmp
> > > $ mkdir -p foo/var
> > > $ cd foo/bar
> > > $ rm -rf ../
> > > rm: ../: Invalid argument
> > > $ rm -rf ../
> > > $
> > >
[...]
> > Quick testing here:
> >
On Tue, 25 Sep 2007 17:55 +0100, jan.grant wrote:
On Tue, 25 Sep 2007, Oliver Fromme wrote:
Note that the command "rm -rf ../" was entered twice.
The first time I got an error message (and exit code 1),
the second time it apparently succeeded.
Check the man page for rm:
-f Attemp
I need to configure my ATI X700 to be able to have a dual monitor since i
really need it for representations, I have not have any luck in the last
year searching around to make it work, I am asking any one that has an a
machine like mine and has resolved this issue to kindly send me any
information
I need to configure my ATI X700 to be able to have a dual monitor since i
really need it for representations, I have not have any luck in the last
year searching around to make it work, I am asking any one that has an a
machine like mine and has resolved this issue to kindly send me any
information
Dne Wed, 26 Sep 2007 08:41:38 +0300
"Maher Mohamed" <[EMAIL PROTECTED]> napsal(a):
> I need to configure my ATI X700 to be able to have a dual monitor
> since i really need it for representations, I have not have any luck
> in the last year searching around to make it work, I am asking any
> one t
33 matches
Mail list logo
