hey

How are you,

No Waiting for Doc#Tors, Complete privacy.

We are your one Stop Shoppp for Considerab1e     M3d!!!!c <at> 1      D!s_c0untts. 

------------------------------------------------------------------------

copy the address below and paste in a your web browser:

borofluohydric.iyodopack.com

------------------------------------------------------------------------

To me a painted paroquet.
In which I have during the last eight years studied the methods of my friend Sherlock Holmes, .
Remember my years, heavy with sorrow --  .
Look at my face -- dark as the night --  .
A sour Scotswoman called Hooch..

Goodbye,

Kip Davison
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

hey

Hello linux-admin <at> vger.kernel.org,

A11          Pre#scr!pt!0ns       are filled by          L!#cens#ed        Ph <at> r#m <at> !_sts.

We have more than 150        med!z cat !0ns. 

------------------------------------------------------------------------

copy the address below and paste in a your web browser:

aureola.iyodopack.com

------------------------------------------------------------------------

I have no time for idle cares.
All you dark children in the world out there, .
Make of my pass a road to the light .
Longer than sun, or any revolving satellite, .
Yet shining like the sun with love's true light. .

Sincerely,

Gena Battelle
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

LOG target for rate-limiting on iptables not working...?

I've rate-limited the incoming connections to some ports. The rate
limiting works, but it doesn't log to syslog... other non-rate-limiting
rules where LOG targets exist work, so I know logging in principle works.
What am I missing? No LOG target for this module? :)

Rule:

# POP3 (max 5 per minute)

$FW -I INPUT -p tcp --dport 110 -i eth0 -m state --state NEW -m recent
--set

$FW -I INPUT -p tcp --dport 110 -i eth0 -m state --state NEW -m recent
--update --seconds 60 --hitcount 5 -j LOG --log-level warn --log-prefix
"RLIMIT[POP3]: "

$FW -I INPUT -p tcp --dport 110 -i eth0 -m state --state NEW -m recent
--update --seconds 60 --hitcount 5 -j REJECT

Also, is there any advantage to use DROP instead of REJECT? Just
curious.

J

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: LOG target for rate-limiting on iptables not working...?

I usually just have a rule like logreject:

$FW -I INPUT -p tcp --dport 110 -i eth0 -m state --state NEW -m recent
--update --seconds 60 --hitcount 5 -j LogReject1

# RULE: Logreject:
$FW -N LogReject1
$FW -I LogReject1  -j LOG --log-level warn --log-prefix "RLIMIT[POP3]:

$FW -I LogReject1  -j REJECT

Jens Knoell wrote:

>I've rate-limited the incoming connections to some ports. The rate
>limiting works, but it doesn't log to syslog... other non-rate-limiting
>rules where LOG targets exist work, so I know logging in principle works.
>What am I missing? No LOG target for this module? :)
>
>
>
>Rule:
>
># POP3 (max 5 per minute)
>
>$FW -I INPUT -p tcp --dport 110 -i eth0 -m state --state NEW -m recent
>--set
>
>$FW -I INPUT -p tcp --dport 110 -i eth0 -m state --state NEW -m recent
>--update --seconds 60 --hitcount 5 -j LOG --log-level warn --log-prefix
>"RLIMIT[POP3]: "

Re: LOG target for rate-limiting on iptables not working...?

Reject will send either a Reset (RST) packet (TCP)
or an ICMP reject (UDP)

Drop will silently ignore the packet's existence.
The sender will get no response at all

If you have no listening ports, and everything that is not
associated with an outgoing connection is DROPped (as opposed
to rejected) it makes it rather hard for a random attacker
to realize that your

Generally I would say that errant packets from 'presumed friendly'
machines can probably be safely rejected.  Packets from 'presumed 
hostile' addresses should probably be silent dropped.

Jens Knoell wrote:

>I've rate-limited the incoming connections to some ports. The rate
>limiting works, but it doesn't log to syslog... other non-rate-limiting
>rules where LOG targets exist work, so I know logging in principle works.
>What am I missing? No LOG target for this module? :)
>
>Also, is there any advantage to use DROP instead of REJECT? Just
>curious.

--

-- 
Stephen Samuel +1(604)450-0066             samnospam <at> bcgreen.com
		   http://www.bcgreen.com/
   Powerful committed communication. Transformation touching
     the jewel within each person and bringing it to light.

Re:

Hey whats up,

Completely Safe...NO Side Ef fe cts. 

KEEP THE WEY-GHT OFF PERMANENTLY.

No racing hearte.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

COPY the Address below and paste in your BROeWSER:

brokage.landoftheburd.com

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

His workbook is wedged in the window,.
One picture puzzle piece.
I give thee the first suggestion, the problem and indirection,) .
Or a fold in the red.
No safety , no love, no respect was I due..

Sincerely,
Jerry Schulz
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

RE: Computer suddenly failed - solved

 Hello ,

I found a solution on the previous problem. Somewhere in the maling
lists I found to check IDE cabel. And there was problem. I just chenaged
IDE cabel  (really damaged ) and now it's ok ( no disc change )

Thanks

Jevos, Peter wrote:

> I'd like to ask you about strange problem. I hope I chose a correct 
> mailing list I have 2 IDE disks in RAID 1 with Reiserfs.
> Once I noticed message in the log:
> 
> hde: dma_timer_expiry: dma status == 0x20
> hde: timeout waiting for DMA
> PDC202XX: Primary channel reset.
> hde: timeout waiting for DMA
> hde: (__ide_dma_test_irq) called while not waiting
> hde: status timeout: status=0xd0 { Busy }
>  PDC202XX: Primary channel reset.
> hde: drive not ready for command
> ide2: reset: success
> hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> hde: drive not ready for command
> hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }

Your drive has died.

> DMA on hde was turned off so I turned it on again. Than I tried to 

Linux Горящие туры в ГОА - 800$ 2 недели

Гоа – Индия!!!

Билеты – 250$

Туры – 3* - 800$ на 2 недели

Т. 258-54-82

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

hey there

Quota for root ?

Hi,

Is it possible to create quota for root?
I have process that runs with root, which I want to limit its writing,
so it will not fill the whole File System.

Can it be done with quota ?

Thanks in advanced,
Sion

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html