Send inn-workers mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/inn-workers
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of inn-workers digest..."


Today's Topics:

   1. Re: Berkeley DB relicensed to AGPLv3 (Julien ?LIE)
   2. Re: Berkeley DB relicensed to AGPLv3 (Russ Allbery)
   3. Log articles in realtime? (Jesse Rehmer)
   4. Re: Log articles in realtime? (Julien ?LIE)
   5. Re: Log articles in realtime? (Russ Allbery)
   6. Re: Log articles in realtime? (Russ Allbery)


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

Message: 1
Date: Wed, 03 Jul 2013 19:53:56 +0200
From: Julien ?LIE <[email protected]>
To: [email protected]
Subject: Re: Berkeley DB relicensed to AGPLv3
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed

Hi Russ,

> Oracle is claiming on their web site to have relicensed Berkeley DB under
> the Affero GPL v3:
>
> http://www.oracle.com/technetwork/products/berkeleydb/downloads/oslicense-093458.html

Thanks for the pointer.  Interesting to know.



>      Notwithstanding any other provision of this License, if you modify
>      the Program, your modified version must prominently offer all users
>      interacting with it remotely through a computer network (if your
>      version supports such interaction) an opportunity to receive the
>      Corresponding Source of your version by providing access to the
>      Corresponding Source from a network server at no charge, through some
>      standard or customary means of facilitating copying of software.
>
> which together imply that INN linked with Berkeley DB is a "covered work"
> (because it's based in part on Berkeley DB), hence must be licensed under
> the AGPLv3, which in turn requires that any modified versions offer all
> users interacting with it remotely some way to download the source.

This paragraph applies only if the Program was modified.  Which I guess 
is almost always the case when packaged to fit into the distribution of 
an OS.



> However, read strictly, it could imply that anyone running a
> version of INN linked with Berkeley DB who has modified the source in some
> way is required to present as part of the NNTP banner or in some similar
> way a URL to the source code.  (Possibly including the source for Berkeley
> DB?  It's really not clear.)

A sentence could be added to the answer for the HELP command (instead of 
the NNTP banner).  It would be less intrusive.
It could be a feature we allow, independently of Berkeley DB support. 
As we already have motd.innd and motd.nnrpd to customize the answer for 
the LIST MOTD command, we could provide two new optional help.innd and 
help.nnrpd files whose contents would just be appended to the current 
result of the HELP command.
This way, the possibility for anyone (end user or packager) to add 
whatever he wants would be provided.


Just a question:  if the end user removes help.innd and help.nnrpd, 
would it cause a problem?  Should the message when INN is linked with 
Berkeley DB be more tied to the code?  (that is to say unremovable 
unless INN is rebuilt)

-- 
Julien ?LIE

? Et vous allez reprendre votre bateau? Et, mergitur ou pas,
   fluctuat ! Compris ! Fluctuat ! ? (Goudurix)


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

Message: 2
Date: Wed, 03 Jul 2013 11:06:06 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: Berkeley DB relicensed to AGPLv3
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8

Julien ?LIE <[email protected]> writes:

>> However, read strictly, it could imply that anyone running a version of
>> INN linked with Berkeley DB who has modified the source in some way is
>> required to present as part of the NNTP banner or in some similar way a
>> URL to the source code.  (Possibly including the source for Berkeley
>> DB?  It's really not clear.)

> A sentence could be added to the answer for the HELP command (instead of
> the NNTP banner).  It would be less intrusive.

True, but it's not clear that actually satisfies the requirement.  The
license says that the source must be offered to all users who interact
with the program.  The banner would clearly qualify, since it's always
sent, but putting something in HELP or LIST MOTD is only sent to users who
run those commands (which is almost none of them).  So it comes down to a
technical legal question of whether putting the offer in the output of an
optional command still counts as "offering," or if the source is then only
"offered" to users who run that command.

> Just a question:  if the end user removes help.innd and help.nnrpd,
> would it cause a problem?  Should the message when INN is linked with
> Berkeley DB be more tied to the code?  (that is to say unremovable
> unless INN is rebuilt)

I think it's fine if the user is just made aware of this, since it's the
person running INN who would, in theory, be in violation of the license,
and for most practical purposes it's probably not going to matter.  ISC
clearly isn't going to sue them over this, so it would have to involve
Oracle suing them somehow over not complying with the license, which is
really quite a stretch.

-- 
Russ Allbery ([email protected])             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.


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

Message: 3
Date: Wed, 03 Jul 2013 15:15:59 -0500
From: Jesse Rehmer <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Log articles in realtime?
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

I'd really like to have the article log (/usr/local/news/log/news) 
written to in realtime, or closer to realtime much like Diablo 
performs.  I don't see that there are any configuration settings which 
may control this, unless I've overlooked something.  Before I start 
digging in source code I was curious if anyone else had been able to 
implement realtime logging?

Note that when I say realtime I just mean that the log appears to be 
updated as each article is received in Diablo and I'd prefer that 
behavior for INN if possible.

Cheers,
Jesse
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/inn-workers/attachments/20130703/4004b691/attachment-0001.html>

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

Message: 4
Date: Wed, 03 Jul 2013 22:29:08 +0200
From: Julien ?LIE <[email protected]>
To: "[email protected]" <[email protected]>
Subject: Re: Log articles in realtime?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252; format=flowed

Hi Jesse,

> I'd really like to have the article log (/usr/local/news/log/news)
> written to in realtime, or closer to realtime much like Diablo
> performs.  I don't see that there are any configuration settings which
> may control this, unless I've overlooked something.  Before I start
> digging in source code I was curious if anyone else had been able to
> implement realtime logging?

I suggest you have a look at:

   http://www.eyrie.org/~eagle/software/inn/docs/innd.html

-u
The news log (the trace information for every article accepted by innd) 
is normally buffered. This option changes the log to be unbuffered.



   http://www.eyrie.org/~eagle/software/inn/docs/inn.conf.html

innflags
The flags to pass to innd on startup. See innd(8) for details on the 
possible flags. The default value is unset.
Note that these flags are only used when innd is started from rc.news or 
nntpsend.




I hope it deals with your need.

-- 
Julien ?LIE

? Et vous allez reprendre votre bateau? Et, mergitur ou pas,
   fluctuat ! Compris ! Fluctuat ! ? (Goudurix)


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

Message: 5
Date: Wed, 03 Jul 2013 13:32:00 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: Log articles in realtime?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

Jesse Rehmer <[email protected]> writes:

> I'd really like to have the article log (/usr/local/news/log/news)
> written to in realtime, or closer to realtime much like Diablo performs.
> I don't see that there are any configuration settings which may control
> this, unless I've overlooked something.  Before I start digging in
> source code I was curious if anyone else had been able to implement
> realtime logging?

> Note that when I say realtime I just mean that the log appears to be
> updated as each article is received in Diablo and I'd prefer that
> behavior for INN if possible.

Change whatever script you use to start innd to pass the -u option to
innd.

    -u  The news log (the trace information for every article accepted by
        innd) is normally buffered. This option changes the log to be
        unbuffered.

-- 
Russ Allbery ([email protected])             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.


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

Message: 6
Date: Wed, 03 Jul 2013 13:32:54 -0700
From: Russ Allbery <[email protected]>
To: [email protected]
Subject: Re: Log articles in realtime?
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii

Russ Allbery <[email protected]> writes:

> Change whatever script you use to start innd to pass the -u option to
> innd.

>     -u  The news log (the trace information for every article accepted by
>         innd) is normally buffered. This option changes the log to be
>         unbuffered.

...probably by using innflags as Julien mentioned.  Doh.

-- 
Russ Allbery ([email protected])             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.


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

_______________________________________________
inn-workers mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/inn-workers

End of inn-workers Digest, Vol 53, Issue 2
******************************************

Reply via email to