- db-wg - mailman.ripe.net

RIPE Database software release 2.1
by Chris Fletcher 27 Oct '97

27 Oct '97

RIPE Database software Version 2.1 is now available from: ftp://ftp.ripe.net/ripe/dbase/software/ripe-dbase-2.1.tar.gz The release notes are included below. There a some new features including a new installation procedure and conversion to perl5. Please let us know if you have problems. Replies to <ripe-dbm(a)ripe.net>. Regards, Chris Fletcher - RIPE NCC RELEASE NOTES for RIPE Database 2.1 SUPPORTED SYSTEMS This release has been tested with perl5.00401 on bsdi2.1 and GNU/linux systems. Please let us know if you have problems running it on other systems. FEATURES When an update sends an acknowledgement and a notification to the same mail address one or the other can be suppressed see SUPPRESSMESS in the config file. New concise format for acknowledgements and notifications. '-v' provides detailed object descriptions. Re-implemented Makefiles and package configuration for ease of use. Includes an 'uninstall' target to carefully remove the executable and libraries when upgrading. Now two help files, one about the whois interface delivered by whois and one about the mail interface delivered by mail. Notifications are sent when an object is created with a notify: attrib. Whole package runs under perl5.004 with DB_File interface to Berkley db. Perl5 hides a lot of platform specific things from scripts so various configuration options have been made obsolete and removed. DB_File allows you to increase the size of the in memory db file cache which greatly improves indexing performance. see DBCACHESIZE We have not tried it with other DBM packages but it should not be hard to change if you want to use GDBM_File. This could become a configuration option (or maybe use AnyDBM_File) if there is demand for it. Changed syntax of 'changed:' & 'withdrawn:' to allow a 4 digits in the year part of the date (8 digits in total rather than 6). Automatically added dates are 8 digits. Existing 6 digit date fields are left unchanged. BUG FIXES added word boundary matches to subject line parsing now matches 'new object' and not 'My Apple Newton'. added 'i' to regexp check of MAIL-FROM so is not case-sensitive changed code to match comments in ripedb.config won't log incoming serial updates to files if SERIALINCOMINGDIR is not defined. MISC Added copyright message to all source files to better assert our rights but licence has not changed from previous versions. I have had problems with bitwise operations on the large integers used to represent IP addresses. With some versions of perl5 a bitwise '&' returns a signed result. This causes classless lookups to fail. See comments about iprightzeromask in misc.pl. It seems to work with perl5.00401 Changes to ripedb.config The following values have been removed... HELP (replaced by WHOISHELP & AUTODBMHELP) RENICECMD (optional - will use setpriority(2) if not set) The following values have been added... WHOISHELP AUTODBMHELP ATTDESC OBJDESC DBCACHESIZE SUCCESSTXT HELPHEADER FAILURETXT

1 0

Re: some problem in syntax.pl
by Steven Bakker 20 Oct '97

20 Oct '97

>>>>> On Sat, 18 Oct 1997, "HH" == Hwang Hyojung wrote: HH> why do you eval check ? Isn't this necessary ? Rather, I think, HH> $regex is checked if it is valid email address. How do you think HH> about it ? If it is necessary, please explain why this is needed . HH> Thanks in advance !! Please read RIPE-157, section 2.3.3., Authorization Schemes (shouldn't that be "Authorisation", Ambrose? :-). There is a section labeled, `The "MAIL-FROM" scheme:', which explains that the MAIL-FROM value in the "mntner" object is treated as a regular expression, against which From:- headers will be matched. So, yes the "eval" is necessary to make sure people submit a valid regex in their "mntner" objects. While we are on the subject, RIPE-157 mentions that the regex should comply to the rules in "POSIX 1003.2 section 2.8." Not having read that document, I wonder if the POSIX syntax and Perl are identical. "syntax.pl" checks whether the regex is Perl-compliant. For example, does '(abc)' mean "the literal string '(abc)'", or (a-la Perl), "the subpattern 'abc'"? Cheers, Steven

1 0

some problem in syntax.pl
by Hwang Hyojung 18 Oct '97

18 Oct '97

Hi, I am Hyojung Hwang and working for Korea Telecom. I am using ripe dbase software. I found some problem or starnge things in this code. In syntax.pl, checking 'auth' attribute, --- elsif ($authstr[0] eq "MAIL-FROM") { local($regex) = $value; $regex =~ s/^\s*MAIL\-FROM\s*//; eval "/$regex/;"; if ($@) { return $O_ERROR, "\"$regex\" is not a legal regular expression"; } else { return $O_OK; } } --- why do you eval check ? Isn't this necessary ? Rather, I think, $regex is checked if it is valid email address. How do you think about it ? If it is necessary, please explain why this is needed . Thanks in advance !! -- * _ _ ==GD@: 56@L0m Hq8A@: 1$1b@L4Y. ||_|| ||_| Hwang, Hyojung / jung(a)jean.kotel.co.kr / 82-2-526-5235 |_| _|_ Internet Team / Multimedia Laboratory / KT R&D Group |_| 137-792, 17 Umyun-Dong, Seocho-Gu, Seoul, Korea

1 0

Slow update processing.
by RIPE Database Administration 14 Oct '97

14 Oct '97

Dear Colleagues, This afternoon, two large update messages were sent to <auto-dbm(a)ripe.net>. They were sent very close together in time. This has created a queue which is longer than normal. We expect this queue to be at its normal size soon. We thank you for your patience. You are not required to send in your update message again. We ask that you think of other users when you send in long update messages; please send them in outside working, "office" times. If you have any questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

1 0

auto-dbm
by Helen Dagerus 14 Oct '97

14 Oct '97

Is there something wrong with the database auto-dbm? Kind Regards Helen Dagerus Tele2/SwipNet

1 1

Database Updates.
by RIPE Database Administration 02 Oct '97

02 Oct '97

Dear Colleagues, There is a queue of Database updates. This is because of a problem which we fixed this morning. We anticipate that the queue will be processed by 1300 UTC today. Thank you for your patience. If you have anymore questions, please contact <ripe-dbm(a)ripe.net>. Regards, Ambrose Magee ____________________________ RIPE Database Administration.

1 0

Re: RIPE Database files.
by davidk＠isi.edu 02 Oct '97

02 Oct '97

[ CC'ed to the db-wg list since my question and your answer seems to be of interest for more people ] Ambrose, RIPE Database Administration writes: > > In particular, the person and role objects will only be available > if you agree to follow an acceptable use policy. > > ... > > The text files containing the whole database > > ftp://ftp.ripe.net/ripe/dbase/ripe.db.gz > > and > > ftp://ftp.ripe.net/ripe/dbase/ripe.db.long.gz > > will be removed. Are you removing the complete files ?!? I would appreciate if you could keep the files but without the person and role objects. This way, I (and probably other people) don't need to change any of my (their) scripts, Thanks in advance, David K. ---

1 0

for help
by abocintl＠public3.bta.net.cn 01 Oct '97

01 Oct '97

I choose the ripe dabase software to setup a intranet nic and need not to connect to internet. After i install the server software, i find i can use "dbupdate" applcation program to creat a new person object, but i can creat a new domain or inetnum objects which ip ranges from 10.71.0.0 to 10.71.255.255 and domain name is nic.cnpc.com.cn. Can you help me?thanks by the way, where can i find some information about "networkupdate" application program and could i creat a "mntner"object by myself?

2 1

subscribe
by Alexander Langer 25 Sep '97

25 Sep '97

subscribe langer(a)online-club.de Alexander Langer -- >>>>>>>>>>> Alexander Langer <langer(a)online-club.de> <<<<<<<<<<< >>> http://www.cichlids.com <<< >>> http://rheuma-online.de/ <<< >>> PGP-Key on Request <<< >>> <°))>< ICQ-UIN: 455213 <<< >>>>>>>>>>> Keyboard not found - Press F1 to continue... <<<<<<<<<<<

1 0

rpsl transition session
by SchmitzJo＠aol.com 22 Sep '97

22 Sep '97

Dear all, one topic which has been lurking in the back for quite some time for the IRR is a more elaborate description of routing policies than offered by RIPE-181. In the past months it has more and more emerged, become mature, and is now on the standards track of IETF: RPSL, the routing policy structured language. For future development of the Internet world it needs to be incorporated into the registries. Some preliminary work has already been done to include RPSL into the RIPE database software. But we are still in the beginning. We want to show you which work was done up to now, which work is currently done, and which work there is still to be done in the future. We also want your input to allow a smooth transition from the current version of the database to its future implementation. RPSL is a topic which is important both for routing issues, and for database evolution. Therefore, the chairmen of database wg and routing wg, Wilfried Woeber and Joachim Schmitz, decided to have a joint session of both working groups in addition to their individual wg sessions, on this special topic, the RPSL transition. The individual wg sessions (routing and db) are held on Wednesday. The RPSL transition session is prepared with the help of the RIPE NCC and RPSL developers. It will be held on Thursday at 9:00am (see meeting schedule). Its major goal is *not* to teach RPSL but to give an overview of the current situation and planned developments. Please find enclosed the draft agenda for this session. Regards Wilfried Woeber and Joachim Schmitz Draft Agenda RPSL Transition Session 1. Preliminaries (Joachim Schmitz, Wilfried Woeber) - participants' list - volunteering of scribe - questions to the audience, part one - introduction 2. Short Introduction to RPSL (Daniel Karrenberg) 3. RPSL Planned Development (David Kessens) - RaToolSet - Status of the DB code - conversion tools 4. Changes in RIPE Database Software Behaviour (David Kessens) 5. Outline of a Transition Plan for RIPE (Carol Orange) 6. AOB - questions to the audience, part two - Tutorial at next RIPE meeting ---

1 0