As Anton Berezin wrote:
> > > - signal(SIGCHLD, SIG_IGN);
> > > + signal(SIGCHLD, SIG_DFL);
> Umm, I don't understand. I do not want automatic zombie reaping, I want
> exactly the opposite, and my patch does just that.
Ah sorry, i was confused.
--
cheers, J"or
Sometime in the last few days, disklabel -Brw auto seems to have stopped
working for me on alpha It used to be the thing of:
dd if=/dev/zero of=/dev/da5 bs=1024k count=10
...
disklabel -Brw da5 auto
Now I get:
dd if=/dev/zero of=/dev/da5 bs=1024k count=10
...
disklabel -Brw da5 auto
diskla
Take the Skillometer Skills
Challenge! Win $100!
Get the recognition
you deserve. As an accomplished IT professional, we invite you to
take the Skillometer Skills Challenge. Skillometer
provides web-based skills testing for current and leading-edge Information
Technologies. Our tests
[subscribing to FreeBSD-scsi as I type this]
`mt status` shows "variable" as the default, and I am not specifying a blocksize to
dump. Below is an example of how I am doing
this, and all other partitions use the same options.
/sbin/dump -0 -a -n -u -f /dev/nsa0 /
On a side note, what happened
[ moved to scsi, followup there ]
Hard to say. It looks like we're somehow missing early warning and going all
the way to end of tape. I've had real trouble reproducing this situation. I've
had some reports, but I've not been able to really make it happen for me, and,
yes, I use DDS tapes also.
This is a new issue [was not present in -current a few months ago].
Attempting a dump to an HP C1533A DDS-2 drive, dump seems to "freeze the tape" at EOT.
Inserting the next volume of the dump and typing "yes" only produces write errors.
Performing an `mt rewind`, prior to typing "yes" clears t
On Thu, Jul 12, 2001 at 10:40:12PM +0300, Giorgos Keramidas wrote:
> Anton Berezin <[EMAIL PROTECTED]> writes:
> > Umm, I don't understand. I do not want automatic zombie reaping, I
> > want exactly the opposite, and my patch does just that.
> I might be wrong in many ways, but...
> is it then
< said:
> I might be wrong in many ways, but...
> is it then mandatory that you `reset' SIGCHLD to SIG_DFL ?
Possibly. In the general case (as specified by standards), what
happens to SIGCHLD if it was set to SIG_IGN before exec() is
ill-defined. Some systems will inherit the SIG_IGN setting,
Anton Berezin <[EMAIL PROTECTED]> writes:
> On Thu, Jul 12, 2001 at 08:45:55AM +0200, Joerg Wunsch wrote:
> > Anton Berezin <[EMAIL PROTECTED]> wrote:
> >
> > > if (fork() == 0) {
> > > - signal(SIGCHLD, SIG_IGN);
> > > + signal(SIGCHLD, SIG_DFL);
> >
>
At 8:45 AM +0200 7/12/01, Joerg Wunsch wrote:
>Anton Berezin <[EMAIL PROTECTED]> wrote:
>
>> if (fork() == 0) {
>> - signal(SIGCHLD, SIG_IGN);
>> + signal(SIGCHLD, SIG_DFL);
>
>This is unportable.
His change is pretty portable, as I have been run
From: Peter Wemm <[EMAIL PROTECTED]>
Subject: Re: No more snapshots of -CURRENT?
Date: Thu, 12 Jul 2001 05:49:59 -0700
> Actually, I think we just need to pester jkh nicely to get somebody to
> copy over the stable build script, s/stable/current/, s/-rRELENG_4/-A/
> and fire it up.
I'm willing
No, it simply means that the machine has been too ill to make
snapshots for awhile. We're in the process of replacing it, but
everyone involved has been really busy. :(
- Jordan
From: John Indra <[EMAIL PROTECTED]>
Subject: No more snapshots of -CURRENT?
Date: Thu, 12 Jul 2001 13:50:34 +0700
>
On Thu, Jul 12, 2001 at 05:49:59AM -0700, Peter Wemm wrote:
> Jesper Skriver wrote:
> > On Thu, Jul 12, 2001 at 05:31:30AM -0700, Peter Wemm wrote:
> > > Alfred Perlstein wrote:
> > > > * John Indra <[EMAIL PROTECTED]> [010712 01:51] wrote:
> > > > > Hi all...
> > > > >
> > > > > I have been visi
Jesper Skriver wrote:
> On Thu, Jul 12, 2001 at 05:31:30AM -0700, Peter Wemm wrote:
> > Alfred Perlstein wrote:
> > > * John Indra <[EMAIL PROTECTED]> [010712 01:51] wrote:
> > > > Hi all...
> > > >
> > > > I have been visiting current.freebsd.org for the past weeks, and see no
> > > > newer i386
On Thu, Jul 12, 2001 at 05:31:30AM -0700, Peter Wemm wrote:
> Alfred Perlstein wrote:
> > * John Indra <[EMAIL PROTECTED]> [010712 01:51] wrote:
> > > Hi all...
> > >
> > > I have been visiting current.freebsd.org for the past weeks, and see no
> > > newer i386 snapshots then 20010618. Does it me
Alfred Perlstein wrote:
> * John Indra <[EMAIL PROTECTED]> [010712 01:51] wrote:
> > Hi all...
> >
> > I have been visiting current.freebsd.org for the past weeks, and see no
> > newer i386 snapshots then 20010618. Does it mean -CURRENT is in no "stable"
> > condition right now?
>
> current is n
On Thu, Jul 12, 2001 at 08:45:55AM +0200, Joerg Wunsch wrote:
> Anton Berezin <[EMAIL PROTECTED]> wrote:
>
> > if (fork() == 0) {
> > - signal(SIGCHLD, SIG_IGN);
> > + signal(SIGCHLD, SIG_DFL);
>
> This is unportable.
> If you want automatic zombi
i386/
the newest -current snapshot is 5.0-CURRENT-20010712-JPSNAP.
current.jp.FreeBSD.org is not the mirror of current.FreeBSD.org.
If you want to know about current.jp.FreeBSD.org, please see
http://current.jp.freebsd.org/
--
It seems Benjamin Close wrote:
> Hi All,
> FreeBSD -current hasn't correctly detected the CDROM drive in my laptop
> for some time now. I've traced the problem down to the drive returning
> an invalid ATAPI_LSB_MAGIC and ATAPI_MSB_MAGIC which is checked at line
> 704 in dev/ata/ata-all.c
>
On Thu, 12 Jul 2001 01:44:44 -0500,
Alfred Perlstein <[EMAIL PROTECTED]> said:
Alfred> * Alfred Perlstein <[EMAIL PROTECTED]> [010712 01:42] wrote:
>> * Seigo Tanimura <[EMAIL PROTECTED]> [010711 19:08] wrote:
>> >
>> > The patch and the results of build test are now on the web page.
>> >
>>
* Seigo Tanimura <[EMAIL PROTECTED]> [010711 19:08] wrote:
>
> The patch and the results of build test are now on the web page.
>
> The discussion of ktrace(2) problem does not cover the solution of
> BSD/OS, so it needs updating.
Right now I'm only reviewing the file part and
I'm only up to '
> At Thu, 12 Jul 2001 15:26:58 +0900,
> I wrote:
> > Actually this doesn't help libpam.so.1, because the new pam modules
> > (pam_*.so) do not work with it. Which means you need to recompile
> > the programs linked with it, such as sudo, xdm, and the X server.
>
On Thu, Jul 12, 2001 at 02:08:34AM -0500, Alfred Perlstein wrote:
>> newer i386 snapshots then 20010618. Does it mean -CURRENT is in no "stable"
>> condition right now?
>current is never "stable", if you want stable stil with -stable. :)
I KNOW. That's why I put double quotes around the stable w
23 matches
Mail list logo
