Running FBSD 4.5-RELEASE
Just looked at "dmesg" and noticed this at the end of the output:
Limiting open port RST response from 261 to 200 packets per second
Limiting open port RST response from 312 to 200 packets per second
Limiting open port RST response from 282 to 200 packets per second
Limit
I have formatted my hard disk using the floppy that came with it. It is now
a 32bit FAT. I ran FIPS and everything seemed to go OK except that I
received a message at the end of FIPS that said it could not partition
FAT12, but I have no idea where it is getting the FAT12 from.
Please note that F
i've seen the following log in my messages can any body tell me what does it
mean?
May 21 02:50:29 darkstar sm-mta[55021]: k4KLoTeq055021: localhost [127.0.0.1]
did not issue MAIL/EXPN/VRFY/ETRN during connection to MSA
regards,
Imran
___
freebsd-qu
Err, I've got a bunch of mail questions...
What the heck is going on here?
Apr 12 23:26:48 postfix/qmgr[73146]: 8B46133C3E: from=<>, size=2716,
nrcpt=1 (queue active)
Apr 12 23:26:48 postfix/qmgr[73146]: D956C33C39: from=<>, size=2712,
nrcpt=1 (queue active)
Apr 12 23:26:48 postfix/qmgr[73146]: 5
On Tuesday 23 July 2002 05:11 pm, Jack L. Stone wrote:
> Running FBSD 4.5-RELEASE
>
> Just looked at "dmesg" and noticed this at the end of the output:
> Limiting open port RST response from 261 to 200 packets per second
> Limiting open port RST response from 312 to 200 packets per second
> Limiti
At 05:15 PM 7.23.2002 -0500, Tim wrote:
>On Tuesday 23 July 2002 05:11 pm, Jack L. Stone wrote:
>> Running FBSD 4.5-RELEASE
>>
>> Just looked at "dmesg" and noticed this at the end of the output:
>> Limiting open port RST response from 261 to 200 packets per second
>> Limiting open port RST respon
On Tue, 24 Jun 2003 06:19, Frank wrote:
> I have formatted my hard disk using the floppy that came with it. It is
> now a 32bit FAT. I ran FIPS and everything seemed to go OK except that I
> received a message at the end of FIPS that said it could not partition
> FAT12, but I have no idea where i
On Sunday 21 May 2006 05:19, Imran Imtiaz wrote:
> i've seen the following log in my messages can any body tell me what does
> it mean?
>
> May 21 02:50:29 darkstar sm-mta[55021]: k4KLoTeq055021: localhost
> [127.0.0.1] did not issue MAIL/EXPN/VRFY/ETRN during connection to MSA
It means that someo
Henry wrote:
Err, I've got a bunch of mail questions...
What the heck is going on here?
Apr 12 23:26:48 postfix/qmgr[73146]: 8B46133C3E: from=<>, size=2716,
nrcpt=1 (queue active)
Apr 12 23:26:48 postfix/qmgr[73146]: D956C33C39: from=<>, size=2712,
nrcpt=1 (queue active)
Apr 12 23:26:48 postfix/q
But how come I can't see what IP the person is connecting from? So I
can block him through my firewall since he is getting annoying :(
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscr
Henry wrote:
> Err, I've got a bunch of mail questions...
> What the heck is going on here?
>
> Apr 12 23:26:48 postfix/qmgr[73146]: 8B46133C3E: from=<>, size=2716,
> nrcpt=1 (queue active)
> Apr 12 23:26:48 postfix/qmgr[73146]: D956C33C39: from=<>, size=2712,
> nrcpt=1 (queue active)
> Apr 12 23:
Imran Imtiaz wrote:
i've seen the following log in my messages can any body tell me what does it
mean?
May 21 02:50:29 darkstar sm-mta[55021]: k4KLoTeq055021: localhost [127.0.0.1]
did not issue MAIL/EXPN/VRFY/ETRN during connection to MSA
Do you run something like Nagios or BigBrother on y
in port sysutils/hal there is an option
fixed_mountpoints=
which is "off" by default.
Is the meaning of this option documented somewhere?
I've had lots of trouble with hal/dbus/X in the past
I wonder if my options are to blame.
many thanks
--
Anton Shterenlikht
Room 2.6, Queen's Build
On Thu, 2009-08-13 at 13:37 +0100, Anton Shterenlikht wrote:
> in port sysutils/hal there is an option
>
> fixed_mountpoints=
>
> which is "off" by default.
> Is the meaning of this option documented somewhere?
This option tells hal to use fixed names for /media mount points instead
of vol
(3583 MB)
avail memory = 3678240768 (3507 MB)
ACPI APIC Table:
AP #1 (PHY# 1) failed!
panic y/n? [y]
What does this mean (and what do I do about it)?
I am off to Google but as I am in a real tight spot I thought I would
ask for some help asap before I go and try and figure this out.
Thanks
boots it comes up and
real memory = 3758030848 (3583 MB)
avail memory = 3678240768 (3507 MB)
ACPI APIC Table:
AP #1 (PHY# 1) failed!
panic y/n? [y]
What does this mean (and what do I do about it)?
That basically means that the kernel failed to start the second CPU.
-Glenn
I am off to Google
On Jul 29, 2005, at 2:23 AM, Glenn Dawson wrote:
At 12:51 AM 7/29/2005, Chad Leigh -- Shire.Net LLC wrote:
Hi
Now when it boots it comes up and
real memory = 3758030848 (3583 MB)
avail memory = 3678240768 (3507 MB)
ACPI APIC Table:
AP #1 (PHY# 1) failed!
panic y/n? [y]
What does this
Noticed the message in the subject in last night's security run.
Is this a sign of impending drive failure? Some google searches turned
up information about Areca drivers and lots of unanswered questions.
This system doesn't have an Areca driver, and it's been rock-solid
for about 2 months now.
On Friday 22 June 2007 15:45, Bill Moran wrote:
> Noticed the message in the subject in last night's security run.
>
> Is this a sign of impending drive failure? Some google searches turned
> up information about Areca drivers and lots of unanswered questions.
> This system doesn't have an Areca d
In response to Nikos Vassiliadis <[EMAIL PROTECTED]>:
> On Friday 22 June 2007 15:45, Bill Moran wrote:
> > Noticed the message in the subject in last night's security run.
> >
> > Is this a sign of impending drive failure? Some google searches turned
> > up information about Areca drivers and lo
20 matches
Mail list logo
