Şunu aradınız:: why did you do it (Ukraynaca - İngilizce)

Вилучення застарілих пакунківtransaction state, checking the transaction before we do it
obsoleting packages

################################################################ # # disclaimer/ license # this template is (c) by mario weilguni & lt; mweilguni@ kde. orggt; # it is licensed under the same terms as the kppp package, # which it is part of # ################################################################ # # this is a sample rule set for kppp. you can use it as a # template when you have to create your own ruleset. if you do # so, remove all comments and add your own. this will allow # other users to check your ruleset more easily. # # please sign the tarif file with your name and email address # so that i can contact you if necessary. # # note: the rules in this rule set do not make much sense and # are only for demonstration purposes # # note on filenames: # when you create your own ruleset, use "_" in filename # instead of spaces and use ". rst as extension # i. e." austria city calls "# -- > file should be saved as" austria_ city_ calls. rst "# # thanks, bernd wuebben # wuebben@ math. cornell. edu / wuebben@ kde. org ################################################################ ################################################################ # # name of the ruleset. this is needed for accounting purposes. # ################################################################ name=default ################################################################ # currency settings ################################################################ # defines ats (austrian schilling) to be used as currency # symbol (not absolutely needed, default =" $") currency_ symbol=ats # define the position of the currency symbol. # (not absolutely needed, default is" right ") currency_ position=right # define the number of significant digits. # (not absolutely needed, default is" 2 "currency_ digits=2 ################################################################ # connection settings ################################################################ # note: rules are applied from top to bottom - the # last matching rule is the one used for the # cost computations. # this is charged whenever you connect. if you don' t have to # pay per- connection, use" 0 "here or comment it out. per_ connection=0. 0 # minimum costs per per connection. if the costs of a phone # call are less than this value, this value is used instead minimum_ costs=0. 0 # you pay. 74 for the first 180 seconds (3 minutes) no matter # whether you are connected for 1 second or 180 seconds. # this rule will take priority during the first 180 seconds # over any other rule, in particular the 'default' rule. # have a look at costgraphs. gif in the docs directory # of the kppp distribution for a graphic illustration. flat_ init_ costs=( 0. 74, 180) # this is the default rule which is used when no other rule # applies. the first component" 0. 1 "is the price of one #" unit ", while" 72 "is the duration in seconds. # therefore the following rule means:" every 72 seconds 0. 1 # ats are added to the bill "default=( 0. 1, 72) # # more complicated rules: # #" on monday until sunday from 12: 00 am until 11: 59 pm the costs # are 0. 2 each 72 seconds "on () between () use (0. 2, 2) # same as above on (monday.. sunday) between () use (0. 2, 2) # same as above. you must use 24 hour notation, or the accounting # will not work correctly. (example: write 15: 00 for 3 pm) on (monday.. sunday) between (0: 00.. 23: 59) use (0. 2, 2) # applies on friday, saturday, sunday and monday 8am until 1pm on (friday.. monday) between (8: 00.. 13: 00) use( 0. 3, 72) # attention: on( monday.. friday) between (21: 00.. 5: 00) use (0. 4, 2) # does not include saturday 0: 00- 5: 00, just monday.. friday, as it says. # applies on a given date (christmas) on (12/ 25) between () use (0. 3, 72) # a range of dates and one weekday on (12/ 25.. 12/ 27, 12/ 31, 07/ 04, monday) between () use (0. 4, 72) # use this for easter on (easter) between () use (0. 3, 72) # easter + 50 days (pfingstmontag / pentecost monday) on (easter+50) between () use (0. 3, 72) on (thursday) between (20: 00.. 21: 52) use (8. 2, 1) # the" on () "rules above all relates to current time only. you can also # make a rule depend on the number of seconds you have been connected # by specifying this time as a third argument to" use () ". # for instance, let' s say normal rate in the evening is 0. 20 per minute, # and it drops by 20% after one hour of connect time. this can be modelled # like: on () between (19: 30.. 08: 00) use (0. 20, 60) on () between (19: 30.. 08: 00) use (0. 16, 60, 3600) # note that these rules, just like other rules, are sensitive to the # order in which they appear.
################################################################ # # disclaimer/ license # this template is (c) by mario weilguni & lt; mweilguni@kde. orggt; # it is licensed under the same terms as the kppp package, # which it is part of # ################################################################ # # this is a sample rule set for kppp. you can use it as a # template when you have to create your own ruleset. if you do # so, remove all comments and add your own. this will allow # other users to check your ruleset more easily. # # please sign the tarif file with your name and email address # so that i can contact you if necessary. # # note: the rules in this rule set do not make much sense and # are only for demonstration purposes # # note on filenames: # when you create your own ruleset, use "_" in filename # instead of spaces and use ". rst as extension # i. e." austria city calls "# -- > file should be saved as" austria_city_calls. rst "# # thanks, bernd wuebben # wuebben@math. cornell. edu / wuebben@kde. org ################################################################ ################################################################ # # name of the ruleset. this is needed for accounting purposes. # ################################################################ name=default ################################################################ # currency settings ################################################################ # defines ats (austrian schilling) to be used as currency # symbol (not absolutely needed, default =" $") currency_symbol=ats # define the position of the currency symbol. # (not absolutely needed, default is" right ") currency_position=right # define the number of significant digits. # (not absolutely needed, default is" 2 "currency_digits=2 ################################################################ # connection settings ################################################################ # note: rules are applied from top to bottom - the # last matching rule is the one used for the # cost computations. # this is charged whenever you connect. if you do n't have to # pay per-connection, use" 0 "here or comment it out. per_connection=0.0 # minimum costs per per connection. if the costs of a phone # call are less than this value, this value is used instead minimum_costs=0.0 # you pay .74 for the first 180 seconds (3 minutes) no matter # whether you are connected for 1 second or 180 seconds. # this rule will take priority during the first 180 seconds # over any other rule, in particular the'default 'rule. # have a look at costgraphs. gif in the docs directory # of the kppp distribution for a graphic illustration. flat_init_costs=(0.74,180) # this is the default rule which is used when no other rule # applies. the first component" 0.1 "is the price of one #" unit ", while" 72 "is the duration in seconds. # therefore the following rule means:" every 72 seconds 0.1 # ats are added to the bill "default=(0.1, 72) # # more complicated rules: # #" on monday until sunday from 12:00 am until 11:59 pm the costs # are 0.2 each 72 seconds "on () between () use (0.2, 2) # same as above on (monday.. sunday) between () use (0.2, 2) # same as above. you must use 24 hour notation, or the accounting # will not work correctly. (example: write 15:00 for 3 pm) on (monday.. sunday) between (0:00..23:59) use (0.2, 2) # applies on friday, saturday, sunday and monday 8am until 1pm on (friday.. monday) between (8:00..13:00) use(0.3,72) # attention: on(monday.. friday) between (21:00..5:00) use (0.4,2) # does not include saturday 0:00-5:00, just monday.. friday, as it says. # applies on a given date (christmas) on (12/ 25) between () use (0.3,72) # a range of dates and one weekday on (12/ 25..12/ 27, 12/ 31, 07/ 04, monday) between () use (0.4, 72) # use this for easter on (easter) between () use (0.3,72) # easter + 50 days (pfingstmontag/ pentecost monday) on (easter+50) between () use (0.3,72) on (thursday) between (20:00..21:52) use (8.2, 1) # the" on() "rules above all relates to current time only. you can also # make a rule depend on the number of seconds you have been connected # by specifying this time as a third argument to" use() ". # for instance, let's say normal rate in the evening is 0.20 per minute, # and it drops by 20% after one hour of connect time. this can be modelled # like: on () between (19:30..08:00) use (0.20, 60) on () between (19:30..08:00) use (0.16, 60, 3600) # note that these rules, just like other rules, are sensitive to the # order in which they appear.