I have an alias for eth0 called eth0:0.
Short version: I want to route packets from one virtual interface to another through an external gateway and not through the loopback interface.
Detailed: I want to route packets from eth0:0 (by using LD_PRELOAD, I can change the src IP address) to eth0. ...
@84104 Its like trollscience for serverfault. Doesn't understand ip aliasing (or that its been deprecated for years), doesn't understand linux routing, why is LD_PRELOAD anything to do with it? Love to know how he reckons he'll ever process the packet if he ever got it back as removing it from the local routing table makes linux consider it an IP for forward.
you can't publish something under, e.g. the BSD license, remove it from a later version, and say "AND ANYONE WITH THE OLD VERSION? NO. YOU HAVE TO DESTROY IT. YOU CAN'T USE IT" -- the genie is out of the bottle, and they're covered by the prior licensing
Honestly it doesn't affect me - I don't need any of the "contested" features and if they have to do a BSDI-style rip shit out to be legal I'm not gonna cry over it. What I do need is fucking active development and bug fixes - and Bacula has kinda stopped providing those in the open-source edition :-/
@MatthewIfe then UKFast has a cause of action :-) either way, that particular chunk of code isn't important to me, so like I said, if they do a BSDI-style "These 6 files must be baleeted" I'm not going to cry. (Hell if I have to baleet them myself in my own git repo I don't care)
I'm just particularly cognizant of the fact that I'm running... I think it's 3 years old now? software with bugs that actually bite me in production, and Bacula Systems seems to have abandoned anything that's not Enterprise.
@MatthewIfe 's broken in Bacula too. But I use virtual tape files so I don;t care :P
@Wesley I still have some analysis to do on the crash dump, but we all crashed at the exact same instant, and the crash dump says Teefer.sys (which is the antivirus packet filter component of Symantec AV) tried to access memory address 0x0 which crashed the system.
Yeah, not saying choose one or the other. Saying dont use an autochanger ;). We use an autochanger on our virtual tape files too, days of having to look through multi-threaded nightmare code to figure out all the damned race conditions.
If Bacula Systems starts updating their shit again (like they claim they will) the point is moot IMHO
@MatthewIfe why do you use an autochanger on your virtual tapes? Disk is so fast :)
What I really need to do is rewrite the remote-sync-and-locking routines we use (basically our "tape unmount" code) - every time a tape fills our backups block while it gets sync'd to the remote storage dump
but that's our own internal shit that I wrote in an hour and haven't revisited yet. Stupid shell script....
@MatthewIfe yeah - I spool everything in parallel and then despool to the virtual tapes (which is the big serial bottleneck, but we're only moving like 100-150 gigs on big nights)
@voretaq7 you can do it using one tape device but it interleaves the jobs block by block, it makes restoring the data or extracting it in desperate situations painful.
now if Bacula Systems fixes the autochanger code in their open source edition that might motivate my ass to stick with them - it would be a nice improvement.
@voretaq7 if you do it in parallel in bacula it doesn't work like that, normally one block on the volume is dedicated to one 'session' or 'job'. If you dont mess with that value the block is typically 64512 bytes in size.
@MatthewIfe 20 February 2013: Bacula 5.2.13 has been released. <-- Bacula Systems and I have different definitions of "soon" sir - a year without a patch when I'm getting bugged by bugs :-/
I know way too much about this because I'm having to write a whole bunch of code to verify whats in our volumes matches whats in the catalog (which bacula have told me due to the bugs mentioned above is unlikely to be the case)
@MatthewIfe the spooled behavior is as I noted above - IDK if that's intentional, but it's the empirical behavior at least in my environment and it's desirable :)
@MatthewIfe "we'll include it in the enterprise edition. Thanks and give us some money if you want to use it" seems to be their general attitude lately
@MatthewIfe they definitely interleave if a job is longer than the size of a spool, but my spools are "generously sized" proportional to my data - our biggest machines might be 5 spools, so they're spread across five bulk-writes :)
Ah right do you spool to different locations per job? I suspect that thatll be done sequentially. Only where multiple jobs go to the same spool you get interleaving.
@MatthewIfe I'll give them credit for doing the right thing when I see them doing the right thing -- like I said there are lots of stupid annoying bugs (like the director locking up if you query a SD or FD that's "busy" and doesn't respond) that I've been told don't exist in Enterprise
@MatthewIfe yeah we have per-job spools, and a cap on the max amount of spooled data
so when a job is done spooling that spool gets written out as one bulk dump to the tape
(again, not sure if that's by design or not, but it's what happens and it's what I want so gift horse, mouth, etc. :-)
@voretaq7 well it technically exists less in bacula 5.2.13 in theory too because they removed the device locking and replaced it with volume locking. Albeit now they've introduced a whole bunch of autochanger bugs cause of it ;p)
yes, break my backups. They're not enterprise critical or anything...
@MatthewIfe the FDs aren't usually my problem - if I do status storage while our unmount command is running though the director lays down and dies until the unmount is done
I've LOVE to backup more clients but would want local storage daemons to do it, then migrate to off site locations (or go full crazy and do virtual fulls weekly and ship them to another sd)