Hello, I wonder if this script is, I can not find it. It automatcly stops users that leave hubs download. Similar to inbuild function in DC, but script apply for whole hub rather than just single user. Is there such, or could there be?
From client to client
Thanks Kepp, you can delete my thread now... Guess there is no way to log it :(
QuoteOriginally posted by Rulle
Thanks Kepp, you can delete my thread now... Guess there is no way to log it :(
You can log it, but this automatically disconnect user feature is up to individuals in my opinion.
QuoteOriginally posted by Rulle
Thanks Kepp, you can delete my thread now... Guess there is no way to log it :(
hmm, well he cant delete ur thread he isnt a moderator, well, the most u can do is delete ur post, and the others as well, and so on and so on, :)
QuoteOriginally posted by bastya_elvtars
You can log it,
Ok great, how is this done?
Normal procedure would be login for a few seconds and one or more quick searches then logout.. I guess.
QuoteOriginally posted by Rulle
QuoteOriginally posted by bastya_elvtars
You can log it,
Ok great, how is this done?
Normal procedure would be login for a few seconds and one or more quick searches then logout.. I guess.
OK then, let's start over. What do you want to log?
Well, I wanna log users who come in to hub and use up slot without being loggen in and sharing,, Why? Because of strict slotrules, wanting higher speed in small hub. But I guess a logger for those short-stoppers would do it, maybe people logged in less than 10 minutes doing intense search. And why not not with a following search which tells if searched file was actually found on hub :)
Hope I didn't make too bad explanation :)
QuoteOriginally posted by Rulle
Well, I wanna log users who come in to hub and use up slot without being loggen in and sharing,, Why? Because of strict slotrules, wanting higher speed in small hub. But I guess a logger for those short-stoppers would do it, maybe people logged in less than 10 minutes doing intense search. And why not not with a following search which tells if searched file was actually found on hub :)
Hope I didn't make too bad explanation :)
So:
1) User logs in.
2) Does a search immediately.
3) Gets a response (responses can not be captured 100%, but gotta see the DC++ wiki on this.)
What comes then?
Hmm, maybe after 10 times over a period of a month or so it makes a log of inactive user if hubtime is very short every single time or almost..