With the exception of the changed IP address, that's what's in the howto. Also, if I'm thinking it through correctly, the "auto lo:0" line should fire the interface up at boot, right?
The clustered database systems are using lo:0 as the to listen to the virtual IP address for the database cluster, so I'm pretty sure that it is supposed to be set up on lo:0. (eth0 is used for the box's real ip address)
That all being said. Shouldn't that commands listed bring up the loopback subinterface (lo:0) at boot?
Sorry I meant eth0:0.
The lo entry is for 127.0.0.x.
You can have / should have multiple IP's on the eth0 interface. That's where the systems communicate on. localhost is ONLY used inside a system. Thus it's not possible to talk to an external system over lo interfaces.
just means to discard output. Any response/output of the command in front of the '>' sign is lost. It's sometimes useful to remove the > /dev/null to see the actual output and if oke, add it again. It can hide too much
The Following User Says Thank You to martinfst For This Useful Post:
Recent comments
10 hours 45 min ago
15 hours 49 min ago
20 hours 14 min ago
22 hours 3 min ago
1 day 12 hours ago
1 day 12 hours ago
1 day 17 hours ago
1 day 23 hours ago
2 days 47 min ago
2 days 2 hours ago