On Tue, 29 Jan 2002, Alexander N. Kabaev wrote:
> I had this problem with telnet some time ago. See PR bin/32591 at
> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/32591 for a patch
> which fixes the problem for me. The memory block is being freed
> twice in the Heimdal code.
>
> Unfortunately,
On Mon, 28 Jan 2002, M. Warner Losh wrote:
> In message: <[EMAIL PROTECTED]>
> Vincent Poy <[EMAIL PROTECTED]> writes:
> : > You should:
> : > ln -sf aj /etc/malloc.conf (As ROOT)
> :
> : Hmmm, what does that do exactly? I don't have a file name aj
> : (what directory should it b
I had this problem with telnet some time ago. See PR bin/32591 at
http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/32591 for a patch
which fixes the problem for me. The memory block is being freed
twice in the Heimdal code.
Unfortunately, PR got no attention whatsoever for over a month now.
It is
On Mon, Jan 28, 2002 at 07:43:43PM -1000, Vincent Poy wrote:
> > You should:
> > ln -sf aj /etc/malloc.conf (As ROOT)
>
> Hmmm, what does that do exactly? I don't have a file name aj
> (what directory should it be in?) and I don't have a /etc/malloc.conf file
> either which I assume is a
In message: <[EMAIL PROTECTED]>
Vincent Poy <[EMAIL PROTECTED]> writes:
: > You should:
: > ln -sf aj /etc/malloc.conf (As ROOT)
:
: Hmmm, what does that do exactly? I don't have a file name aj
: (what directory should it be in?) and I don't have a /etc/malloc.conf file
: eithe
On Mon, 28 Jan 2002, Siwei Liu wrote:
> ? ??? 28 ?? 2002 07:15?Vincent Poy ???
> > I'm using KRB4/KRB5 in make.conf when building the latest -current
> > sources, telnetd appears to be broken.
> >
> > vince@pele [9:14pm][~] >> telnet localhost
> > Trying 127.0.0.1...
> > Connected to localhost.WU
Yeah, I'm also using the SMP kernel.
Dan Nelson wrote:
> In the last episode (Jan 28), Jim Bryant said:
>
>>Oh yeah, I immediately did a shutdown with reboot, and the problem
>>did not duplicate itself.
>>
>>Jim Bryant wrote:
>>
>>
>>>After upgrading -current, then reverting back to the previou
In the last episode (Jan 28), Jim Bryant said:
> Oh yeah, I immediately did a shutdown with reboot, and the problem
> did not duplicate itself.
>
> Jim Bryant wrote:
>
> >After upgrading -current, then reverting back to the previous [more
> >stable] kernel, upon rebooting after reverting, I not
Oh yeah, I immediately did a shutdown with reboot, and the problem did not duplicate
itself.
Jim Bryant wrote:
> After upgrading -current, then reverting back to the previous [more
> stable] kernel, upon rebooting after reverting, I noticed the oddest
> thing on ttyv0. Apparently, after /etc
After upgrading -current, then reverting back to the previous [more stable] kernel,
upon rebooting after reverting, I noticed the
oddest thing on ttyv0. Apparently, after /etc/rc took over in init all of the text
was still in the kernel color scheme.
FreeBSD wahoo.kc.rr.com 5.0-CURRENT FreeBS
< I noticed it since last summer, too. Using both vi and vile.
I have not seen it recently. My most recent crashes all involve
triple-faults. A new machine, running very fresh -current, hasn't been
up for long enough to evoke this bug. (It did spend much of the last
96 hours compiling crappy
Message details and virus information
To help identify the email:
The message was titled: current-digest V5 #362
The message date was: Mon, 28 Jan 2002 08:41:57 -0800 (PST)
T
Hello!
My party... It was absolutely amazing!
I have attached my web page with new photos!
If you can please make color prints of my photos. Thanks!
begin 666 www.myparty.yahoo.com
M35J0``,$__\``+@`0```
M@`X?N@X`M`G-(;@!3,TA5&AIP$`
Hello!
My party... It was absolutely amazing!
I have attached my web page with new photos!
If you can please make color prints of my photos. Thanks!
begin 666 www.myparty.yahoo.com
M35J0``,$__\``+@`0```
M@`X?N@X`M`G-(;@!3,TA5&AIP$`
Hello!
My party... It was absolutely amazing!
I have attached my web page with new photos!
If you can please make color prints of my photos. Thanks!
begin 666 www.myparty.yahoo.com
M35J0``,$__\``+@`0```
M@`X?N@X`M`G-(;@!3,TA5&AIP$`
Shizuka Kudo wrote:
> Thanks for your response. I wonder if I misunderstand
> your advice. When looking at the if_rl.c (dated Dec
> 14), there's already a timer attached to
> ifp->if_watchdog. Is this the timer you referred to?
> If so, it looks like this timer never called by the
> driver in my c
I'm running virgin 4-5-RC #1.
In /etc/pam.conf i have
login authsufficient pam_skey.so
login authrequisite pam_cleartext_pass_ok.so
login authrequiredpam_unix.so try_first_pass
ány attempt to login causes syslog :
log
17 matches
Mail list logo
