Bans get lost
 

News:

29 December 2022 - PtokaX 0.5.3.0 (20th anniversary edition) released...
11 April 2017 - PtokaX 0.5.2.2 released...
8 April 2015 Anti child and anti pedo pr0n scripts are not allowed anymore on this board!
28 September 2015 - PtokaX 0.5.2.1 for Windows 10 IoT released...
3 September 2015 - PtokaX 0.5.2.1 released...
16 August 2015 - PtokaX 0.5.2.0 released...
1 August 2015 - Crowdfunding for ADC protocol support in PtokaX ended. Clearly nobody want ADC support...
30 June 2015 - PtokaX 0.5.1.0 released...
30 April 2015 Crowdfunding for ADC protocol support in PtokaX
26 April 2015 New support hub!
20 February 2015 - PtokaX 0.5.0.3 released...
13 April 2014 - PtokaX 0.5.0.2 released...
23 March 2014 - PtokaX testing version 0.5.0.1 build 454 is available.
04 March 2014 - PtokaX.org sites were temporary down because of DDOS attacks and issues with hosting service provider.

Main Menu

Bans get lost

Started by nikita800, 23 April, 2007, 14:47:30

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

nikita800

If from the dispatcher of problems(tasks) (CTRL+ALT+DEL) to finish process Ptokax.exe bans are not kept. It and should be?
More in detail: I enter !banip 255.255.255.255, ban it is visible in a window of a hub. I press CTRL+ALT+DEL and compulsorily I close process Ptokax.exe Then again I start a hub - ban it is not kept.

bastya_elvtars

I think if you kill via the task manager, nothing saves data properly. Saving settings on given intervals would indeed be nice, though.
Again, I think this is the expected behaviour.
Everything could have been anything else and it would have just as much meaning.

CrazyGuy

Quote from: nikita800 on 23 April, 2007, 14:47:30
If from the dispatcher of problems(tasks) (CTRL+ALT+DEL) to finish process Ptokax.exe bans are not kept. It and should be?
More in detail: I enter !banip 255.255.255.255, ban it is visible in a window of a hub. I press CTRL+ALT+DEL and compulsorily I close process Ptokax.exe Then again I start a hub - ban it is not kept.

PtokaX saves settings when closing.
I suggest to close it properly.
Windows doesn't save settings either if you unplug your computer from the electricity net  ::)

nikita800

Ok. Clearly that it is needed to close (to complete) work of khaba correct methods (by methods), but nevertheless, it would be desirable that Ptokax saved automatically parameters through a certain or set time domain.

Stormbringer

solution of this problem (if there is one) because during all this years that I use DC I have never kill ptokax.exe for any reason... (explorer.exe thousands and thousands of time lol)
Use cobian backup, and make a backup of the hub every time you want, the software is free, very easy to use, and save all script folder of ptokax folder, it can be run as service, you have even the possibility to zip the backup you made

CrazyGuy

Quote from: Stormbringer on 26 April, 2007, 10:42:12
solution of this problem (if there is one) because during all this years that I use DC I have never kill ptokax.exe for any reason... (explorer.exe thousands and thousands of time lol)
Use cobian backup, and make a backup of the hub every time you want, the software is free, very easy to use, and save all script folder of ptokax folder, it can be run as service, you have even the possibility to zip the backup you made


I doubt this is in any way helpfull. It would, if PtokaX would save the info to disk rather than keeping it in memory. So basically, a backup software has nothing to backup ;)
Again, just close the program as you should and no problems will arise :)

LoTeK_

#6
If closing the application with ctrl+alt+del is the same as unplug power then I know about many applications/games that saves all data anyway.
I think the use of ctrl+alt+del by nikita800 was to simulate an unespected power loss or system selfrestart, if that happens after 3 month of hub activities and bans are not saved, this is not good.
I agree with him, a timer for saving all data would be a good improvement, but, I can breathe without it.

dmvn

+1 to this feature request. Please note that 0.4.x branch is NOT stable because it's new, so explicit termination of a process ptokax.exe is not a rare action  :(

PPK

Quote from: dmvn on 14 June, 2008, 09:24:02
Please note that 0.4.x branch is NOT stable
If is NOT stable then how is possible that i'm not getting any bug reports related to stability  ???
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

dmvn

Probably you were lucky, but this one http://forum.ptokax.org/index.php?topic=7927.0 is a direct proof. Also I can add that I do NOT reported about px036 crashes, while there were some... I know it's hard to debug smth that hangs in one case from 1000000. Those crashes were from that bucket :) So I waited patiently for px4.

Ok, let's not to fall into flaming about 'good/bad programs', PX is a good program. But it also has errors as *ANY* program, so please don't become angry when any crash/bugs reported. </offtop_mode_off/> :)

dmvn

subj: That is a GOOD scripting solution, thank you.
PS. Won't continue any stability offtopic, it's useless (I only point you that you're mistaken again sayin that only me can reproduce that bug, please read carefully that topic).

PPK

Quote from: dmvn on 15 June, 2008, 08:26:10
but this one http://forum.ptokax.org/index.php?topic=7927.0 is a direct proof.
No is not, user using direct connect incompatible client (apexdc) sending to hub invalid command can't be proof :P
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

dmvn

Quote from: PPK on 15 June, 2008, 23:15:17
No is not, user using direct connect incompatible client (apexdc) sending to hub invalid command can't be proof :P
Strange way of programming... First of all, that UC is proper (and worked PERFECTLY on px0360, btw for a 1.5 years). Second one is that program that can be exploited (hanged) via sending invalid data is a buggy program, imho :P

PPK

Quote from: dmvn on 15 June, 2008, 23:22:15
First of all, that UC is proper (and worked PERFECTLY on px0360, btw for a 1.5 years).
No is not, direct connect don't have command starting with $<  :P
Quote from: dmvn on 15 June, 2008, 23:22:15
Second one is that program that can be exploited (hanged) via sending invalid data is a buggy program, imho :P
Yes but that program is not PtokaX, as i shown in other topic that command cause only that user who sent it was disconnected.. nothing else  8)
"Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall

dmvn

If you don't want to debug how Apex parses UC, i won't argue. The main matter is far from it. The proper way to think about that UC is that you typed !tempban command from client chat line, and that's all. And this leads to hang in some conds.

I'm sure that this topic can be closed now. The solution is found.

SMF spam blocked by CleanTalk