On Mon, 7 May 2001 10:18:38 -0700
[EMAIL PROTECTED] wrote:
> Lets try another realistic example:
>
> cp -uvp ab* cde*.f* g? h/*.i? j/kl /m
> What's the find | cpio invocation for that? When you come up with it, it
echo ab* cde*.f* g? h/*.i? j/kl /m | cpio ...
Messy - No
On Tue, 8 May 2001, John Baldwin wrote:
> That's easy enough. Well, it used to be at least. You can use 'ps' to
> find the address of the struct proc (first pointer in the display) and
> then do 'call psignal(addr, 9)' to send SIGKILL to the process. Then
> hit 'c' to continue and voila, the
>From: walt <[EMAIL PROTECTED]>
>Date: 08 May 2001 19:58:05 -0700
>cvsup'd CURRENT 5-8-2001 around 1900 PST
>make buildworld stopped here:
>===> usr.sbin/pstat
>cc -O -pipe -I/usr/src/usr.sbin/pstat/../../sys
>-I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.sbin/pstat/pstat.c
>/usr/src/u
cvsup'd CURRENT 5-8-2001 around 1900 PST
make buildworld stopped here:
===> usr.sbin/pstat
cc -O -pipe -I/usr/src/usr.sbin/pstat/../../sys -I/usr/obj/usr/src/i386/usr/include
-c /usr/src/usr.sbin/pstat/pstat.c
/usr/src/usr.sbin/pstat/pstat.c: In function `ufs_print':
/usr/src/usr.sbin/pstat/p
On 08-May-01 Dag-Erling Smorgrav wrote:
> Terry Lambert <[EMAIL PROTECTED]> writes:
>> So now the question becomes "what is he testing that is
>> resulting in 4.3 locking up?".
>
> Good question. It does some non-trivial stuff besides allocating:
> buffered I/O and fork()/exec()'ing sync(1).
>
[ cc severely trimmed ]
Dag-Erling Smorgrav <[EMAIL PROTECTED]> writes:
> I would *love* to have a DDB equivalent to 'kill -9', so I could drop
> to the DDB prompt, check ps, kill a process or two, and drop back out
> of DDB. It would have saved me a reboot and a longish fsck in this
> case.
Mm
[ This time I *did* try and use the FreeBSD mailing list search engined- to no
result that I can see. ]
I now get, when I try and rlogin:
p_match: clnt_call: RPC: Program unavailable
in the client.
I *have* changed hosts.allow to allow rpcbind locally in hosts.allow
(if that's pertine
Dima Dorfman wrote:
> Corey Brune <[EMAIL PROTECTED]> writes:
> > I forgot the kernel secure level was set to 1 when I started make build.
> > The build almost finishes, but dies when it tries to install
> > /usr/lib/libcrypt.so.2 saying operation not permitted. I cannot chflags
> > because of th
On Tue, May 08, 2001 at 02:29:35PM -0700, Matthew Jacob wrote:
> And how is that piece of mail (about cvsup) pertinent?
Well, there is a follow-up:
[EMAIL PROTECTED] , or
http://www.freebsd.org/cgi/getmsg.cgi?fetch=195431+0+/usr/local/www/db/text/2001/freebsd-current/20010506.freebsd-current
And how is that piece of mail (about cvsup) pertinent?
> Please see [EMAIL PROTECTED]
>
> On Tue, May 08, 2001 at 11:16:41AM -0700, Matthew Jacob wrote:
>
> > ===> gnu/usr.bin/perl/perl
> > Extracting config.h (with variable substitutions)
> > Extracting cflags (with variable substitutions)
>
Terry Lambert <[EMAIL PROTECTED]> writes:
> A number of operating systems will allow programs to be
> parked "precious". In AIX, this is done by establishing
> a signal handler for the resource starvation condition;
> programs without the handler "just die". Programs with
> the handler are permi
Terry Lambert <[EMAIL PROTECTED]> writes:
> So now the question becomes "what is he testing that is
> resulting in 4.3 locking up?".
Good question. It does some non-trivial stuff besides allocating:
buffered I/O and fork()/exec()'ing sync(1).
> Your suggested replacement test might be fun to ru
Corey Brune <[EMAIL PROTECTED]> writes:
> I forgot the kernel secure level was set to 1 when I started make build.
> The build almost finishes, but dies when it tries to install
> /usr/lib/libcrypt.so.2 saying operation not permitted. I cannot chflags
> because of the secure level. Does anyone kno
I forgot the kernel secure level was set to 1 when I started make build.
The build almost finishes, but dies when it tries to install
/usr/lib/libcrypt.so.2 saying operation not permitted. I cannot chflags
because of the secure level. Does anyone know a way around this?
Thanks for any suggestions
Hello.
After resup my sources (a 2 hours ago) i tried make buildworld and
it failed:
Extracting myconfig (with variable substitutions)
Missing right curly or square bracket at lib/SelfLoader.pm line 69, at end of line
syntax error at lib/SelfLoader.pm line 69, at EOF
Compilation failed in requir
The following jucy tidbit has been hiding in the accept(2) man page
for several years, but has apparently never been implemented.
One can obtain user connection request data without confirming the con-
nection by issuing a recvmsg(2) call with an msg_iovlen of 0 and a non-
zer
Please see [EMAIL PROTECTED]
On Tue, May 08, 2001 at 11:16:41AM -0700, Matthew Jacob wrote:
> ===> gnu/usr.bin/perl/perl
> Extracting config.h (with variable substitutions)
> Extracting cflags (with variable substitutions)
> Extracting writemain (with variable substitutions)
> Extracting myconfi
On 08-May-01 Edwin L. Culp wrote:
> A couple of days ago, I installed current on a Dell that had been an
> NT server. Everything works fine except is seems very slow. A make
> world on current takes over 5 hours. A little more than my old K6-2
> 300 laptop.
>
> This is the first SMP kernel
===> gnu/usr.bin/perl/perl
Extracting config.h (with variable substitutions)
Extracting cflags (with variable substitutions)
Extracting writemain (with variable substitutions)
Extracting myconfig (with variable substitutions)
Missing right curly or square bracket at lib/SelfLoader.pm line 69, at
world broken at /usr/src/usr.sbin/pstat/pstat.c because IN_SHLOCK is
undeclared, is this something new added to sys/ufs/ufs/inode.h ?
d.-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
A couple of days ago, I installed current on a Dell that had been an
NT server. Everything works fine except is seems very slow. A make
world on current takes over 5 hours. A little more than my old K6-2
300 laptop.
This is the first SMP kernel I have used but I have disabled it with no
not
Dennis Glatting wrote:
> > What is memory exhaustion?
>
> Uh, when I perform a malloc() and get a NULL back? I
> dunno, what do you call that?
Hitting an administratively enforced resource limitation.
> Why would it kill random processes as opposed to the
> offending process?
The offending pr
Jordan Hubbard wrote:
> That's like saying that putting someone
> into orbit is a simple matter of determining what escape velocity is
> necessary from an object with earth's mass and deciding how many tons
> of payload you want to insert at what altitude. The devil is, as they
> say, all in the
Dag-Erling Smorgrav wrote:
> Plus, your program doesn't even do what you think it does (because a)
> it has at least one significant bug and b) malloc() doesn't behave the
> way you think it does). And even if it did, the /dev/random stuff is
> pointless, you can achieve the same effect by settin
On 08-May-01 Seigo Tanimura wrote:
> On Mon, 07 May 2001 12:37:22 -0700 (PDT),
> John Baldwin <[EMAIL PROTECTED]> said:
>
> John> You need the lock when clearing the bit in p_flag. That is why the
> proc locks
> John> are there, so all those proc locks need to stay. When you clear a bit,
> y
cc -O2 -fno-strength-reduce -pipe -march=pentiumpro -DLIBWRAP -DHAVE_LOGIN_CAP
-DLOGIN_ACCESS -I/usr/src/secure/usr.sbin/sshd/../../../usr.bin/login -DUSE_PAM
-DHAVE_PAM_GETENVLIST -DKRB4 -DSKEY -DXAUTH_PATH=\"/usr/X11R6/bin/xauth\"
-I/usr/obj/usr/src/i386/usr/include -c
/usr/src/secure/usr.
cc -O2 -fno-strength-reduce -pipe -march=pentiumpro
-I/usr/src/usr.sbin/pstat/../../sys -c /usr/src/usr.sbin/pstat/pstat.c
/usr/src/usr.sbin/pstat/pstat.c: In function `ufs_print':
/usr/src/usr.sbin/pstat/pstat.c:494: `IN_SHLOCK' undeclared (first use in this
function)
/usr/src/usr.sbin/pstat/
On Mon, 07 May 2001 12:37:22 -0700 (PDT),
John Baldwin <[EMAIL PROTECTED]> said:
John> You need the lock when clearing the bit in p_flag. That is why the proc locks
John> are there, so all those proc locks need to stay. When you clear a bit, you are
John> writing all the bits, so you need to
In message <[EMAIL PROTECTED]> Jan Chrillesen writes:
: > OLDCARD or NEWCARD? If oldcard, are you using the identical
: > configuration as you are on 4.2? The same irq for the pcic device,
: > the same irq list in /etc/pccard.conf, the same memory ranges in
: > /etc/pccard.conf, etc.
:
: I buil
On Sun, 06 May 2001, Warner Losh <[EMAIL PROTECTED]> wrote:
> OLDCARD or NEWCARD? If oldcard, are you using the identical
> configuration as you are on 4.2? The same irq for the pcic device,
> the same irq list in /etc/pccard.conf, the same memory ranges in
> /etc/pccard.conf, etc.
I build it
30 matches
Mail list logo
