Sponsored Content
Special Forums IP Networking Proxy Server Need to build a quick FTP server, Advice?? Post 302920310 by Aia on Wednesday 8th of October 2014 04:37:55 PM
Old 10-08-2014
You can judge for yourself the simplicity of it. Here are two links to how implement it:

SFTP plus chroot
VSFTPD using SSL/TLS
This User Gave Thanks to Aia For This Post:
 

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Advice to build a cheap Unix machine?

Hello! In my perpetual quest to learn Unix, I want to build a cheap Unix server for my personal use. Do you guys have suggestions of web sites, vendors etc...where I could get info on things such as step-by-step instruction, 2nd hand hardware etc... I would like to go preferably with a HP... (2 Replies)
Discussion started by: alan
2 Replies

2. HP-UX

problem after server build...

Hi, I have installed HP-UX 11.31 on a rx6600 box. The installation went fine and was completed without any errors. But wheni connect to the server using ssh, it asks for a username, when i enter it, it doesnt prompt for a password: login:username blank-------- All i could see in... (1 Reply)
Discussion started by: sag71155
1 Replies

3. Web Development

Building LAMP server from scratch (build a server with compiled LAMP from CentOS mini)

Hello everyone, I would like to setup a lamp server from a minimal distro and to compile PHP, MySQL and Apache myself. I have chosen CentOS minimal for the OS and I am trying to build the stack by hand... But well, it appears I need some help! First: I am looking for good and recent... (3 Replies)
Discussion started by: freddie50
3 Replies

4. UNIX for Dummies Questions & Answers

What does it takes to Build a Mail Server?

Subject: What does it takes to build a mail server, its just for fun and learning. Am bad at being techinical, so in short, how to create a gmail-like thing? I have a registered domain, and want to setup a mail server. Have a spare laptop that is running Ubuntu 12.04. What I need to know is,... (4 Replies)
Discussion started by: Memberz Name
4 Replies

5. Red Hat

Implement FTP server on RHEL server without using FTP client

We have RHEL 5.8 in our environment, I had a query whether we can implement an FTP server using vsftpd package and Linux configurations like setsebool without using any external FTP clients like FileZilla etc. I am very confused on this. The FTP functionalities that should be present are download &... (3 Replies)
Discussion started by: RHCE
3 Replies

6. Solaris

How to build an install server for Solaris 8?

I need to boot again a server with solaris 8 because I have a problem with the file path_to_install and I have not a CD/DVD driver. So I'd like to build an install server for executing a boot by network. Could I use a server with solaris 10? Many thanks for your suggests Best Regards at... (2 Replies)
Discussion started by: ardgiu70
2 Replies

7. UNIX for Advanced & Expert Users

Build NFS Server on CentOS

Dear All, I'm using AWS EC2 instance for my application. My application is high disk I/O based and EFS could not be used in my case. So, i need to build my own NFS server on Ec2 instance. I'm looking for High availability solution for my disk which i shared for NFS. Looking for builtin... (5 Replies)
Discussion started by: Bala
5 Replies

8. Red Hat

Advice on allocating SAN storage to a virtual database server on VMware

I am relatively new to Linux and we are getting ready to convert our current oracle database servers from the AIX platform to RHEL7 servers on VMWare. I would appreciate any advice on how best to allocate storage to these machines. I plan on using LVM to maintain the disks/filesystems but am... (9 Replies)
Discussion started by: dkmartin
9 Replies
FSVS - URL format(5)						       fsvs						      FSVS - URL format(5)

NAME
Format of URLs - FSVS can use more than one URL; the given URLs are overlaid according to their priority. FSVS can use more than one URL; the given URLs are overlaid according to their priority. For easier managing they get a name, and can optionally take a target revision. Such an extended URL has the form ['name:'{name},]['target:'{t-rev},]['prio:'{prio},]URL where URL is a standard URL known by subversion -- something like http://...., svn://... or svn+ssh://.... The arguments before the URL are optional and can be in any order; the URL must be last. Example: name:perl,prio:5,svn://... or, using abbreviations, N:perl,P:5,T:324,svn://... Please mind that the full syntax is in lower case, whereas the abbreviations are capitalized! Internally the : is looked for, and if the part before this character is a known keyword, it is used. As soon as we find an unknown keyword we treat it as an URL, ie. stop processing. The priority is in reverse numeric order - the lower the number, the higher the priority. (See url__current_has_precedence() ) Why a priority? When we have to overlay several URLs, we have to know which URL takes precedence - in case the same entry is in more than one. (Which is not recommended!) Why a name? We need a name, so that the user can say 'commit all outstanding changes to the repository at URL x', without having to remember the full URL. After all, this URL should already be known, as there's a list of URLs to update from. You should only use alphanumeric characters and the underscore here; or, in other words, w or [a-zA-Z0-9_]. (Whitespace, comma and semicolon get used as separators.) What can I do with the target revision? Using the target revision you can tell fsvs that it should use the given revision number as destination revision - so update would go there, but not further. Please note that the given revision number overrides the -r parameter; this sets the destination for all URLs. The default target is HEAD. Note: In subversion you can enter URL@revision - this syntax may be implemented in fsvs too. (But it has the problem, that as soon as you have a @ in the URL, you must give the target revision every time!) There's an additional internal number - why that? This internal number is not for use by the user. It is just used to have an unique identifier for an URL, without using the full string. On my system the package names are on average 12.3 characters long (1024 packages with 12629 bytes, including newline): COLUMNS=200 dpkg-query -l | cut -c5- | cut -f1 -d' ' | wc So if we store an id of the url instead of the name, we have approx. 4 bytes per entry (length of strings of numbers from 1 to 1024). Whereas using the needs name 12.3 characters, that's a difference of 8.3 per entry. Multiplied with 150 000 entries we get about 1MB difference in filesize of the dir-file. Not really small ... And using the whole URL would inflate that much more. Currently we use about 92 bytes per entry. So we'd (unnecessarily) increase the size by about 10%. That's why there's an url_t::internal_number. Author Generated automatically by Doxygen for fsvs from the source code. Version trunk:2424 11 Mar 2010 FSVS - URL format(5)
All times are GMT -4. The time now is 03:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy