network profile
| bio | website | SynOdins.com |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 11 months |
| seen | 4 hours ago | |
| stats | profile views | 67 |
|
Jun 13 |
comment |
ls command - define number of columns You can also just write your own script, I did so some years ago and use it all the time: synodins.com/scripts/ls_crystal. By either writing your own or using mine you have complete control over how the script operates. |
|
Jun 5 |
revised |
Rsync over Rsync via cronjob edited title |
|
Jun 4 |
comment |
Rsync over Rsync via cronjob Brilliant, then I most likely don't have to worry about this at all. |
|
Jun 4 |
comment |
Rsync over Rsync via cronjob yes they're the same. |
|
Jun 4 |
comment |
Rsync over Rsync via cronjob Thanks for the info, its interesting. But best of all would be if Rsync-ing over another wouldn't do any harm to begin with. |
|
Jun 4 |
asked | Rsync over Rsync via cronjob |
|
Jun 4 |
accepted | Rsync after copy |
|
Jun 4 |
comment |
Rsync after copy I tested it, I scp'd a 100Mb folder from a remote location to local, and then I rsync'd from that remote to this new local over it, and it took a tiny amount of time at first, and the second time I rsync'ed it was around 0.5 sec, so basically yes, copying before Rsync is ok. |
|
Jun 4 |
revised |
Rsync after copy deleted 50 characters in body |
|
Jun 4 |
comment |
Rsync after copy Yes but when running rsync after having run copy, will then only the changes be sent? |
|
Jun 4 |
asked | Rsync after copy |
|
May 29 |
comment |
Bought speakers (HS-307 USB), driver issue how do I load the snd-usb-audio module? |
|
May 29 |
comment |
Bought speakers (HS-307 USB), driver issue I could find this hecticgeek.com/2012/01/… but he says "And if PulseAudio is working just fine for you, then I highly recommend that you stick with it." So I guess I should just count my losses and buy another speaker. |
|
May 29 |
asked | Bought speakers (HS-307 USB), driver issue |
|
May 29 |
awarded | Popular Question |
|
May 25 |
comment |
Removing access privileges to backup while maintaining current setup This copy of this giant directory is a part of the backup system. There are many instances of this folder stored in many different places. Not damaging whatever user privileges have been set within the folder is to me a part of having a high quality backup solution. I want to minimize the chances that anyone can break into the system and change anything, without marginalizing the quality of the backup. |
|
May 24 |
revised |
Change one typed key for another added 85 characters in body |
|
May 24 |
accepted | `cp -al` snapshot whose hard links get directed to a new file when edited |
|
May 24 |
comment |
Removing access privileges to backup while maintaining current setup What do you mean root:root. To me it's just root. |
|
May 24 |
asked | Removing access privileges to backup while maintaining current setup |
