Website Downtime

[Jason 786]

Shit will break soon. It will then be fixed.

That is all.

[Marine 2580]

okie dokie

[Clay 24]

I'm 12 and what is LightTPD?

[centran 4457]

So... the new design is coming?

[Jason 786]

I'm 12 and what is LightTPD?

Getting replaced by nginx D:

[blob 1985]

So excited

[Jason 786]

While doing this, I asked myself why wouldn't I tar -czvf something before moving it to another server.

Simple answer: zipping a file in an effort to reduce transfer time is utterly pointless when you can transfer it at 110 MB/s.

46% [=================>                     ] 454,161,857  107M/s  eta 2s

[Clay 24]

Getting replaced by nginx D:

ohshi

While doing this, I asked myself why wouldn't I tar -czvf something before moving it to another server.

Simple answer: zipping a file in an effort to reduce transfer time is utterly pointless when you can transfer it at 110 MB/s.

46% [=================>                     ] 454,161,857  107M/s  eta 2s

I lol'd.

[centran 4457]

While doing this, I asked myself why wouldn't I tar -czvf something before moving it to another server.

Forget transfer times.... if you can connect to the server at the time of transfer then why would you tar at all?

rsync -e 'ssh -ax' -axHhPzv --numeric-ids --stats --delete --delete-before /src/ user@server:/dest/

There is a lot there you might not need. Especially the -a flag... that is archive mode and will preserve all permissions/groups/owners/timestamps. If you are moving to a new server then that might be a bad thing and would have to reset permissions to what it is on the new system. Also there might be symlinks that don't exist or the path changed.

The -z flag will compress the files during transfer. Also if the transfer fails for some reason then rsync will restart from where it failed.

[Clay 24]

Forget transfer times.... if you can connect to the server at the time of transfer then why would you tar at all?

rsync -e 'ssh -ax' -axHhPzv --numeric-ids --stats --delete --delete-before /src/ user@server:/dest/

There is a lot there you might not need. Especially the -a flag... that is archive mode and will preserve all permissions/groups/owners/timestamps. If you are moving to a new server then that might be a bad thing and would have to reset permissions to what it is on the new system. Also there might be symlinks that don't exist or the path changed.

The -z flag will compress the files during transfer. Also if the transfer fails for some reason then rsync will restart from where it failed.

rsync is so godly. I used it to transfer my package manager's cache folder to my notebook, eliminating all download times, and it seriously flew at about 25 mb/s, with compression. Local network, obviously, but I was expecting 9ish.

[Jason 786]

Forget transfer times.... if you can connect to the server at the time of transfer then why would you tar at all?

rsync -e 'ssh -ax' -axHhPzv --numeric-ids --stats --delete --delete-before /src/ user@server:/dest/

There is a lot there you might not need. Especially the -a flag... that is archive mode and will preserve all permissions/groups/owners/timestamps. If you are moving to a new server then that might be a bad thing and would have to reset permissions to what it is on the new system. Also there might be symlinks that don't exist or the path changed.

The -z flag will compress the files during transfer. Also if the transfer fails for some reason then rsync will restart from where it failed.

I would normally use rsync, but since one of the boxes was going to be formatted, I was taking a very large number of files off of it and putting them both onto my home computer, and onto the other box. The first of those two is the reason I tarred it.