3 Guests, 0 Users|
UPP v2.20 Build 2010.02.07
UPP 2.x Tutorials:
+ Installation & Autoconnect Settings - by Da_L
+ Importer, Acros, & Backup Modules - by Da_L
+ General Settings part 1 - by PleegWat
+ General Settings part 2 - by PleegWat
+ Setting Up Auto-Identify - by Spaceman-Spiff
+ Fileserver Module - by Da_L (kinda old)
+ UPP Tutorial: How to Setup - by Serena-chan
+ UPP Tutorial: How to Leech - by Serena-chan
+ UPP Tutorial: How to Serve - by Serena-chan
Base Version: 2.0 Build 2003.06.08
Last Updated: ?
The version used here is upp_2.00_build_2003.06.08, which, atm this tutorial was written, is the latest pre-release for UPP2. It's possible that in the final release the looks might change a bit, but it shouldn't make much difference.
The UPP file server is very advanced and full featured, so for new people it's also pretty hard to setup. We're gonna walk through this one step by step.
Most of the times you got all the files you wanna serve combined in one directory, so I'm gonna assume that; not to make stuff harder then it is since this is just an introductory tutorial.
Now move on to the 'triggers' tab, and click 'add trigger'
The trigger field stands for the trigger itself, e.g. the part which comes after /ctcp <your nick>, or the text the user has to type in the channel. In this example assuming my nick is 'cow' on normal, people would have to type 'leech my stuff' in one of the trigger's channels, on ctcp, people would have to type '/ctcp cow leech my stuff'.
The difference between normal and ctcp; with normal triggers everyone in the channel can see when someone types your trigger to access your fserve, and in a big channel that might result in a lot of 'trigger-spamming' (where many people type your trigger out of curiosity after seeing someone else type it). I advise you to use ctcp triggers, although its completely up to you :P (except that some channels have rules telling you which kind of trigger you must use)
Required level: if you'd set this to 'at least +v', only users who are voiced in one of the channels that trigger is running in can access the fserve. When using ctcp triggers, you have the choice between 'none' and 'any'. With 'any', everybody in one of the channels can acces the fserve via that trigger, when on 'none', also people outside one of the channels can access your fserve. (Usually not a good idea)
When 'apply to !list reply' is enabled, users typing '!list' in one of the trigger's channels, will get notified of your fileserver. (Mostly this is needed / recommended)
In the channel box we have the choice between 'all', 'all except' and 'only'. I advise the option 'only', as you have the most control about your server there, and it won't start running in channels it isn't meant to run in.
Now click the 'select' button below 'queuepool'. Select the above line (queuepool 1) and choose 'edit'.
In this window you can change sends, queues, instasend, and min cps stuff. These settings will apply on all triggers using this pool. UPP knows an advanced system for serving on multiple networks and controlling queues/sends, but I'll asume you'll just work with one queuepool, to keep it easy.
When instasend is enabled, files below the specified size will send immediately, and won't end up in queues. This is usefull if you're serving .nfo's, .cue's among larger files.
The send fail system will requeue a failed send into a prioritized queue, so the leecher won't have to wait all over again, or create a prioritized fail-queu, depending upon which you have specified in the "user friendly" tab of the "send manager" (the "sends" module).
Click OK, OK and ADD and your trigger is added. You can repeat this whole process when you want to add more triggers (except you won't have to edit a queue pool if you decide to reuse/share one that you already created/tweaked).. Now back to the fserve settings dialog.
Timeout: A leecher will get disconnected when there's no activity on the fserve for x minutes; timelimit is the maximum time someone can spend on your fserve.
Max users is the maximum number of users who can browse your fserve simultaniously; on a 16k connection I'd set this to 1 or 2.
When fserve send only mode is enabled, your fserve ad won't show up (nor in !list) when all sends/queue slots are full. I don't recommend this as it can disturb fserve tracking bots.
At the bottom, you can specify which parts you wanna have in your fserve ad. (Snagged stands for the combined size of all files sent). Strip ad and short ad will both shorten the ad, and split ad will split it into 2 lines (when you have a lot of triggers which don't fit in one line)
Now click the send button to edit some more settings :)
First lets take a look at the 'speed' tab
If you enable min cps, people will have to reach a minimum speed when downloading or else UPP will automatically cancel their sends. This comes in handy when people hammer your serve with 1kb/s downloads with 10 queued ppl waiting. It's reasonable to warn 'em at least 2x, cause a connection can always have a 'burp'. Keep in mind that this will keep slow people from being able to get files from your fserve (depending on what you set your mincps to).
Max cps is if you want to have some bandwidth left for yourself too. For example, if your maximum upload is 50kb/s, you can set the max cps to 40000; then you'll have 10kb/s left for stuff besides irc.
If you're behind a firewall and/or router, and dcc doesn't work in normal mode, you can enable firewall mode on the firewall tab. On the last tab 'messages', you can enable the 2 bottom options, I personnaly like them.
On the priority tab, you can set priority levels.
If DCC watch is enabled, a queue/send will dequeue/stop if a leecher has parted all channels your fserve is running in. I don't really recommend it, as a netsplit can screw up your sends, but if you enable it, at least set a reasonable delay.
At the right you can give ops/hops/voices priority queueing level. That way other servers will get priority over normal users. You can also specify priority for certain channels/users, but I won't discuss this as you most likely won't need it.
You most likely wanna enable 'enable fservead'. This will send your ad to all fserve channels every x minutes. If you're using the firewall method, I advise that you enable 'show firewall triggers' too, so leechers know what to do.
'Never show in these channels' can be handy too. Sometimes you're serving in multiple channels, but in one of them they don't want you're ad showing up all the time, but only in !list. Then you just set the fserve up for that chan, and ad it to the never show-list.
Fserve banlist should be quite clear itself.
Last tab, then we're finally done with configuring the fserve :P
If you wanna enable users to do @find, change the settings according to the picture above :).
Enable fserve on start; force sends on connect would be enabled most likely, otherwise you'd have to start them both manually.
For the fileserver, UPP caches directories, so the script works faster and fserve sessions take less resources. If you put new content on your server very often, you might wanna enable 'cache expires in 1 hours', so UPP will refresh the cache every hour. Most of the time setting 'on-start', and from
time to time manually refreshing is enough though; 'update cache on fileserver error' is also recommended. I personally like 'don't show progress when caching', you can just work on normally like nothing happened, otherwise a little dialog will popup telling you the cache's getting updated.
« go back to top[aA]>cucusoft register code forum
Written by Da_L. Thanks to hsim for pointing out some errors in this tutorial. Of course also thanks to KyD for writing the best mirc script ever.
This tutorial has been reformated by Spaceman-Spiff and proofread by brewthatistrue.