recentpopularlog in

kme : filesharing   47

Uploading big files > 512MB — ownCloud 8.0 Server Administration Manual 8.0 documentation
Set the following two parameters inside the corresponding .ini file:
<code class="language-ini">php_value upload_max_filesize = 16G
php_value post_max_size = 16G

Adjust these values for your needs. If you see PHP timeouts in your logfiles, increase the timeout values, which are in seconds:
<code class="language-ini">php_value max_input_time 3600
php_value max_execution_time 3600</code>
webmaster  sysadmin  owncloud  bigfiles  uploader  filesharing  collaboration  solution 
november 2019 by kme - Easy and fast file sharing from the command-line. |
<code class="language-bash">
transfer() {
# write to output to tmpfile because of progress bar
tmpfile=$( mktemp -t transferXXX )
curl --progress-bar --upload-file $1$(basename $1) >> $tmpfile;
cat $tmpfile;
rm -f $tmpfile;
curl  cli  commandline  filesharing  cloudstorage  service  tipsandtricks  alternativeto 
november 2017 by kme
networking - Using xdg-open for accessing network with normal explorer - Unix & Linux Stack Exchange []
Yes, you can separate the domain from the user with a semicolon, just like in Mac's Finder:
Tips for mounting SMB shares

xdg-open doesn't appear to be able to mount shares that aren't mounted. For example, here's a SMB share that hasn't been explicitly mounted yet via Nautilus:

% xdg-open 'smb://MYDOM;sam@bart/sam'
gvfs-open: smb://MYDOM;sam@bart/sam/: error opening location: The specified location is not
remotefilesystems  filesharing  smb  samba  commandline  linux  maybesolution 
september 2017 by kme
Tech Tip: Really Simple HTTP Server with Python | Linux Journal
Open up a terminal and type:

$ cd /home/somedir
$ python -m SimpleHTTPServer

NB: for Python 3.x, this is 'python -m http.server'
webdevel  filesharing  collaboration  fileserver  webserver  fuckina  python  python3 
april 2016 by kme
Their product people made a mistake branding this as a common English word that is basically ungooglable. Searching for "barracuda copy" or "" might help.
cloudstorage  filesharing  collaboration  storage  service  alternativeto  dropbox 
may 2014 by kme
ssh login works but sftp doesn't...
The answer is below:
scp2/sftp and sftp-server use a special file-transfer protocol, which they speak over this SSH session. The protocol is in fact based on the same packet protocol used by SSH.

In order for this to work, the SSH session must be "clean" — that is, it must have on it only information transmitted by the programs at either end. What often happens, though, is that there are statements in either the system or per-user shell startup files on the server (.bashrc, .profile, /etc/csh.cshrc, .login, etc.) which output text messages on login, intended to be read by humans (like fortune, echo "Hi there!", etc.). Such code should only produce output on interactive logins, when there is a tty attached to standard input. If it does not make this test, it will insert these text messages where they don't belong: in this case, polluting the protocol stream between scp2/sftp and sftp-server. The first four bytes of the text gets interpreted as a 32-bit packet length, which will usually be a wildly large number, provoking the error message above.

This was the fix for not being able to SFTP to a Mac OS X server. Because (as I recall), users on that server were not allowed to change their own shells, I had by .bashrc 'exec' zsh WITHOUT checking to see if it was interactive ([ -z "$PS1" ], via
ssh  sftp  solution  troubleshooting  nautilus  filesharing  networking 
january 2014 by kme
ssh works, but sftp doesn't | OpenSSH | Dev
For some reason your sftp-server is exiting immediately. Check that
/usr/sbin/sftp-server exists, is executable and doesn't crash
when executed.

For a better test of sftp-server, you can run it directly from
sftp: "sftp -P /usr/sbin/sftp-server blah"

Good suggestions, but no nice on this OS X server I'm troubleshooting. The sftp-server binary is actually at /usr/libexec/sftp-server, though.

nautilus  troubleshooting  filesharing  sftp  mac  osx  sysadmin  networking 
january 2014 by kme
Mount an AFP share from Linux - Stack Overflow
You'd hope a smart server would decline plaintext authentication. But these instructions won't build an afp_mount binary with any of the encrypted UAMs. Per INSTALL, you need to install libgcrypt(-dev).

sudo apt-get install stow libfuse-dev libreadline-dev libgcrypt-dev
./configure --prefix=/usr/local/stow/afpfs-ng
sudo make install
cd /usr/local/stow && sudo stow afpfs-ng
sudo ldcondig
mac  osx  afp  filesharing  linux  fuse  solution  dangerwillrobinson  ftfy 
january 2014 by kme
alexthepuffin - afpfs-ng 0.8.1 An open source client for Apple Filing Protocol
I needed this because, for some reason, with gvfsd version whatever and OpenSSH version 5.6 or 5.9.something and 5.2.something on a Mac OS X server, I couldn't mount sshfs using Nautilus anymore. Nor did SSH with FileZilla work, for some reason.
afs  maybesolution  mac  osx  filesharing  linux  fuse 
january 2014 by kme
Tech, Life, and Triathlon...: NFS mount Ubuntu linux drive on Mac OS X Leopard
The 'map_static' mount option is an interesting solution, although the ReadyNAS may not support it (see:
Now we need to make a map of our user and group IDs we obtained in #1 and #2 above. This will ensure that when we NFS mount our drive on our Mac, the permissions and file ownership will all be set correctly. A common directory for this file is in /etc/nfs. If this directory doesn't exist for you, go ahead and create it.

Create a file in this directory called - it can be called anything, but the naming convention is to use the name of the accessing server, in this case the hostname of your Mac. Mine, creatively enough, has a hostname of mac so my file is called

Here's what my file looks like:

# mapping for client: mac
# remote local
uid 501 1000
gid 20 1000

The first two lines are just comments. The second two map the uid and gid from steps 1 and 2 above. Here, remote means your Mac, and local means your Linux box.

NFS gets its export information (the directories that are allowed to be NFS mounted) from the file /etc/exports. If this file does not exist, just create it. Here's what my file looks like:

/home/doej mac(rw,insecure,map_static=/etc/nfs/

The first argument is the directory on Linux that you want to be able to NFS mount. In this case, I've chosen to mount my home directory. The second parameter are the mount options. To see a full list of options, execute man exports. I've listed my Mac hostname as the server that is allowed to NFS mount this directory. The options I've chosen are:

rw - read/write
insecure - allow non-root user to NFS mount directory
map_static - the file we created above that maps our user and group IDs from Mac to Linux box. If you want to be able to write to your NFS mount, you MUST have this option set and set correctly.
mac  linux  nfs  filesharing  networking  tipsandtricks  readynas 
january 2014 by kme

Copy this bookmark:

to read