Re: bug in OS/2 perproxy build 374?
waldo kitty <[email protected]> Tue, 17 Feb 2009 12:00:11 -0500
| Newsgroups | gmane.comp.distributed-net.proxyper |
|---|---|
| Organization | Waldo's Place USA - DarkStar ThunderBird |
| Message-ID | <[email protected]> |
Roman Trunov wrote:
> waldo kitty wrote:
>
>> i've just installed the perproxy build 347 on my os2 (warp3) box and
>> used the ini file from my previous version (343)... after some time of
>> fiddling about wondering why build 347 was not running, i ran it from
>> the command line and was it complain about a missing [ogrp2] section
>> in the ini file...
>
> in current state .ini file must have at least three sections: [ogrp2],
> [ogrng] and [rc5-72]. proxy will not run if even one of them is missing.
i wasn't aware of that...
> theoretically, it's possible to remove few lines of source code for
> closed [ogrp2] contest but it's rather useless because code for ogr-ng
> and -p2 is shared almost completely.
i can easily understand that... i guess the confusing part was that the missing
section was not created as other sections have been done in past versions... i
mean, i've never had to create any sections in all the years that i've been
running a perproxy... i've edited the ones that were created but i've never had
to create them...
>> now, some 15 minutes before i installed the 347 build, i did edit the
>> ini file and removed all of the closed contest sections but i do not
>> specifically recall removing a ogrp2 section... to the best of my
>> knowledge, previous versions of the perproxy created the necessary ini
>> file sections if they did not exist and filled them with default
>> values... version 347 apparently did/does not do this... at least not
>> with the ogrp2 section...
>
> i'm sure you've unintentionally removed the section yourself. perproxy
> not created missed .ini sections automatically and refused to start in
> such cases for quite a few years.
actually, i did intentionally remove all sections that were listed as
contestclosed=1 to clean up the ini file of all the old unnecessary sections
before loading the new 347 build of the perproxy...
i don't understand your last statement "not created missed .ini sections
automatically and refused to start"??
thanks for your response!
--
NOTE: NEW EMAIL ADDRESS!!
_\/
(@@) Waldo Kitty, Waldo's Place USA
__ooO_( )_Ooo_____________________ telnet://bbs.wpusa.dynip.com
_|_____|_____|_____|_____|_____|_____ http://www.wpusa.dynip.com
____|_____|_____|_____|_____|_____|____ ftp://ftp.wpusa.dynip.com
_|_Eat_SPAM_to_email_me!_YUM!__|_____ wkitty42 -at- windstream.net
---
avast! Antivirus: Outbound message clean.
Virus Database (VPS): 090216-1, 02/16/2009
Tested on: 2/17/09 12:00:13
avast! - copyright (c) 1988-2009 ALWIL Software.
http://www.avast.com
_______________________________________________
proxyper mailing list
proxyper-Ra3b/QYEcJ3d140v2zMXi0fjHoOT/h/[email protected]
http://lists.distributed.net/mailman/listinfo/proxyper