6,842 reputation
11738
bio website
location Boston, MA
age
visits member for 5 years, 1 month
seen Jul 17 at 16:35

Jul
10
comment Expose a mongodb streaming data server that's behind a firewall, to the internet
I agree an SSH tunnel is the way to go here. Keep in mind that using an SSH tunnel will probably get the poster fired if anyone ever figures out what they're up to.
Jul
2
awarded  Curious
Jul
1
comment Gbit uplink vs Regular switch port
TCP expects to drop packets. Dropped packets are how TCP calibrates available bandwidth -- it increases the transmit rate until it observes dropped frames, then it backs off, then increases transmit rate until it sees dropped frames, etc. Generally on switches the "uplink" port is just another port that is identical to the others, even if it has an SFP physical link as well as a standard rj45 connector.
Jun
28
awarded  Custodian
Jun
28
reviewed Approve suggested edit on Nginx replicate incoming post traffic to multiple servers
Jun
28
reviewed Approve suggested edit on nginx reverse proxy with basic_auth - 404 Not found
Jun
28
reviewed Approve suggested edit on how to set php SERVER_PORT var to 80, behind varnish?
Jun
27
comment is zfs snapshot -r of several pools atomic?
That's really cool! Thanks for the info!
Jun
26
asked is zfs snapshot -r of several pools atomic?
Jun
18
awarded  Yearling
Apr
28
comment ZFS snapshots and atomic updates
@syneticon-dj -- that's not actually the behavior I observed -- I saw quite clearly that a static (in the source pool) file would not cause IO errors in the destination pool; files changing frequently on the source pool, however, would show this behavior on the target pool.
Apr
24
comment ZFS snapshots and atomic updates
And -- I could see lots of situations where I'd want to use a filessytem this way -- let's say I had a bunch of web files I wanted to atomically update on a bunch of remote servers. I could use rsync and change a symbolic link or I could send a new snapshot to all of them.
Apr
24
comment ZFS snapshots and atomic updates
I wasn't sure what would happen. Unix has a pretty convenient way of dealing with files as they change; I wasn't sure if the same conventions would apply in this scenario. If I'm reading a file and someone else changes it, I'll either see the changes or not, depending on my current offset in the file and where the change took place. Snapshots certainly add another dimension to this problem.
Apr
24
comment ZFS snapshots and atomic updates
The error is seen by the program reading the file, not the programs involved in the snapshot replication.
Apr
24
revised ZFS snapshots and atomic updates
added 303 characters in body
Apr
24
asked ZFS snapshots and atomic updates
Apr
15
awarded  Popular Question
Apr
9
awarded  Nice Answer
Mar
21
answered Using more than 80% power on a circuit in a disaster scenario
Feb
13
awarded  Notable Question