Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
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 Netdot-devel digest..."
Today's Topics:
1. two issues (one possible bug, and PostgreSQL advice sought)
(William Bulley)
----------------------------------------------------------------------
Message: 1
Date: Fri, 22 Aug 2014 09:47:08 -0400
From: William Bulley <[email protected]>
Subject: [Netdot-devel] two issues (one possible bug, and PostgreSQL
advice sought)
To: Carlos Vicente <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=us-ascii
This is a question about a possible bug in htdocs/management/ip.html
of v1.0.6 Netdot near line 600 (code reproduced here below):
#######################################################################################
# REBUILD_TREE
#
#######################################################################################
}elsif ( $_action eq 'REBUILD_TREE' ){
if ( $tree_version eq '4' || $tree_version eq 'all' ){
Ipblock->build_tree(4);
}elsif ( $tree_version eq '6' || $tree_version eq 'all' ){
Ipblock->build_tree(6);
}
$m->comp('.show_message', title=>"Action Message", msg=>"IP Tree Rebuilt
Successfully");
}
#######################################################################################
# View
#
#######################################################################################
It appears to me that the above "if" statement will either build
the IPv4 tree OR the IPv6 tree, but NOT BOTH -- even if the value
of "$tree_version" is 'all'! Shouldn't there be two separate
(parallel, if you will) "if" statements here, should the value of
"$_action" be 'REBUILD_TREE'???
if (test as above)
Ipblock->build_tree(4);
if (test as above)
Ipblock->build_tree(6);
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
As Netdot moves toward PostgreSQL (as we have here) has anyone
given any thought to database replication (in the case of having
a "hot spare") or the best methods of database backup (saving)
for PostgreSQL? Are there any "industry" backup "best practices"
that folks know of (thinking of Anton here...)?
The act of dumping the database to a DDL file (SQL commands to
recreate the database later), while straightforward, does not
scale well if one has tens of thousands of rows spread across
several dozen tables (even without the *_history tables that are
now not part of Netdot as of v1.0.6).
Regards,
web...
--
/"\ ASCII RIBBON / William Bulley
\ / CAMPAIGN AGAINST /
X HTML E-MAIL AND / E-MAIL: [email protected]
/ \ LISTSERV POSTINGS /
72 characters width template ----------------------------------------->|
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 89, Issue 5
*******************************************
