Hi,
I'm trying to connect to a network device, with the connection follwoing the UNIX routing table we set up. Its to go via a specific network Gateway and out throught a specific Lan card (Lan4). However when trying to conenct it keeps going through Lan3 and will not get to its destination.... (3 Replies)
Is ther a way to retain say, a default gateway entered in a routing table after a reboot? I end up always having to re-enter my default gateway after I reboot my system.
Thanks! (4 Replies)
hi all...
i need to know, where is locate the routing table on sun solaris, how i can saved the configuration....
because when i restart the server, lost the configuration....
thank you...
Regards... (3 Replies)
Hello.
Is there any way to restore back the default ip routing table ?
For example, my current routing table is something like
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
109.123.95.0 0.0.0.0 255.255.255.0 U 0 ... (0 Replies)
Hi all,
Could someone please explain to me how I should read this routing table,
# netstat -rn
Routing tables
Destination Gateway Flags Refs Interface Pmtu
127.0.0.1 127.0.0.1 UH 0 lo0 32808
10.222.47.82 10.222.47.82 UH... (3 Replies)
Discussion started by: rachael
3 Replies
LEARN ABOUT DEBIAN
alzabo::changetracker
Alzabo::ChangeTracker(3pm) User Contributed Perl Documentation Alzabo::ChangeTracker(3pm)NAME
Alzabo::ChangeTracker - Saves a set of changes as callbacks that can be backed out if needed
SYNOPSIS
use Alzabo::ChangeTracker;
my $x = 0;
my $y = 1;
sub foo
{
my $tracker = Alzabo::ChangeTracker->new;
$tracker->add( sub { $x = 0; } );
$x = 1;
bar();
eval { something; };
$tracker->backout if $@;
}
sub bar
{
my $tracker = Alzabo::ChangeTracker->new;
$tracker->add( sub { $y = 1; } );
$y = 2;
}
DESCRIPTION
The trick ...
We only want to have one object of this type at any one time. In addition, only the stack frame that created it should be able to clear it
(except through a backout). Why? Here's an example in pseudo-code to help explain it:
sub foo
{
create a tracker;
store some change info in the tracker;
call sub bar;
store some change info in the tracker;
# point Y
clear changes in tracker;
}
sub bar
{
create a tracker; # internally, we really just increment our stack count
store some change info in the tracker;
clear changes in tracker; # point X
}
If at point X we were to really clear out the changes, even the changes just from sub bar, we'd have a problem. Because if at point Y,
things go to hell and we want to back out the changes, we want to back out the changes from sub foo _AND_ sub bar. However, if bar is also
an entry point we want to be able to track changes in bar and clear them from bar.
AUTHOR
Dave Rolsky, <autarch@urth.org>
perl v5.8.8 2007-12-23 Alzabo::ChangeTracker(3pm)