> I run 4.4 stable with only one tweak: iic at piixpm disabled
> (commented in GENERIC):
> #iic* at piixpm? # disabled because boot freezed on it
I rebuild kernel without this tweak and disable iic in UKC. Results in
tech@ list.
--
engineer
162|mail.plusoft.com.br||<
o...@email >|1231915013|1231917030|1231929413|6|0
GREY|200.162.44.162|mail.plusoft.com.br||<
o...@email >|1231915015|1231917032|1231929415|6|0
GREY|200.162.44.162|mail.plusoft.com.br||<
o...@email >|1231915013|1231917030|1231929413|6|0
GREY|200.162.44.162|mail.plusoft.com.br||<
o...@email >|1231915015|1231917032|1231929415|6|0
# date -r 1231915016
Wed Jan 14 11:36:56 YEKT 2009
# date
Wed Jan 14 14:27:06 YEKT 2009
What is it? Why this WHITE entry raised again? I just can't do anything with
itb&
And can't delete annoying GREY entries.
--
engineer
immeditately preceeding blacklists. Check
> spamd.conf(5) for more details.
>
> What you want is possible, but you have to do it yourself in pf.conf.
> The good news is that it's easy...
Ok, I understand.
Thank's.
--
engineer
; 127.0.0.1 port spamd
Oh, sorry, I forgot to supply one string. Actually it looks like this:
no rdr on $ext_if proto tcp from to $mx_IP port smtp
rdr on $ext_if proto tcp from any to $mx_IP port smtp -> 127.0.0.1 port spamd
--
engineer
9993|1231834393|1231834393|1|0
It seems like spamd completely skipped WHITElisted network
(194.67.23.0 - 194.67.23.255).
I was thinking that all WHITElisted nets will be in the
immediately, just after spamd started...
--
engineer
> This issue is likely to have been addressed by the reliability fix #005,
> as seen on http://www.openbsd.org/errata44.html.
It helps. Thank you!
--
engineer
; using exception 16
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask e765 netmask ef65 ttymask
mtrr: Pentium Pro MTRR support
softraid0 at root
root on sd0a swap on sd0b dump on sd0b
--
engineer
Hi, engineer.
> Hmm... I done this trisk, but it's not works ;). I add
> CHECK=`raidctl -s raid1 | grep '/dev/wd1e: optimal'`
> if [ -n "$CHECK" ]; then
> raidctl -f /dev/wd1e raid1
> fi
> # Check parity on raid devices.
> raidctl -P all
Hi, engineer.
Hmm... I done this trisk, but it's not works ;). I add
CHECK=`raidctl -s raid1 | grep '/dev/wd1e: optimal'`
if [ -n "$CHECK" ]; then
raidctl -f /dev/wd1e raid1
fi
# Check parity on raid devices.
raidctl -P all
into /etc/rc on /dev/wd0a (where liv
root/admin, or so... But, again, let it be, anyhow, SYSTEM WORKING.
I understand that it is very specific solution, very dependent on
that configuration, but this if not for all cases, this is for SUCH
cases! And this can be useful for those who use such configurations.
So, what you can say about this?
--
engineer
fore start system. I read ccd(4), ccdconfig(4), but they are not
describe what I want to know.
And, briefly, what difference between RAID and CCD in such fields
like "performance", "what to do after one disk fail", and "what will
be when one disk fail while system running".
--
engineer
cks. This is so long with my more that 150G on RAID.
I want ask, what will occur if not do "raidctl -P all" in /etc/rc,
but set it in /etc/rc.local, after daemons started?
What can fsck with such "uncleaned/unreconstructed" RAID?
--
engineer
}
queue q_pri_2 priority 7
queue q_def_2 priority 1 priq(default)
So, can I dispense just one altq?
altq on $grp priq bandwidth 10Mb queue { q_pri, q_def }
queue q_pri priority 7
queue q_def priority 1 priq(default)
--
engineer
13 matches
Mail list logo