Azovets report php p. Gallery of some characters



Report on the Ergaki-2003 campaign

Municipal Educational Establishment Local Lore Club "Ermak"

Report on the mountain hike 1 class. in the area of ​​the Ergaki ridge (Western Sayan),
committed from 06/20/2003 to 07/03/2003.

Trek leader: Shishkin S.V.

MCC of the Republic of Khakassia MU "Center for Children and Youth Tourism"



The original report is located at http://tkk-ermak.by.ru/ergaki20030.htm

Background information about the hike

1. Conducting organization:
Municipal educational institution additional education Tourist and local history club "Ermak" of the administration of the Ermakovsky district.

3. Location of the hike
Krasnoyarsk region, Ermakovsky district, Ergaki ridge.

4. Route thread:
Highway M-54 (Krasnoyarsk - State border, Tormozakovsky bridge, 614 km) - r. Malaya Buiba - lake. Raduzhnoe - (rad. outlet of Lake Raduzhnoe - waterfall in the northwest of Raduzhnoe, Raduzhnoe - Hanging Stone) - lane. Intermediate (Legs) (n/k) - trans. Khudozhnikov-2 (1A) - parking lot Mechta - (rad. exit. Dream - vdp. Mountain Spirits - lake of Mountain Spirits - peak Fat Brother (1A) - lane Taigish-1 (1A) - lake Lazurnoe - lane Vpomogatelny ( n/k) - Skazka parking lot - (rad. exit of Skazka station - Vpomogatelny lane (n/k) - Stone Castle) - (rad. exit of Skazka station - Mount Perevalnaya (1A) - pass separating the valleys of Glubokoe lakes and Severnoye (n/k) - Lake Severnoe - Vdp. - river Pryamoy Taygish - lake Bezrybnoye - lake Zolotarnoye - lake Svetloe - river Medvezhiy - highway M-54 - State border, 622 km.)

5. Defining obstacles of the route:
Total obstacles: 11
Passes - 8 (Intermediate (Legs) (n/k), Khuzhnikov-2 (1A), Taigish-1 (1A), Auxiliary (n/k), Rescuers (1A), NKT (1A), Green (1A), Marble (1A ))
Peaks: - 3 (Peak Fat Brother (n/k), Mount Perevalnaya (1A), shoulder of Ptitsa Peak (1A))

6. Information about participants:

p/p FULL NAME. Year of birth Place of work, study Address, telephone Tourist experience Duty on the hike
1 Shishkin Sergey Vasilievich 1971 TKK "Ermak, PDO With. Ermakovskoe, st. K. Marx, 129-2 t. 2-44-09 Head 1 ks Supervisor
2 Blinov Yuri Evgenievich 1966 TKK "Ermak", PDO p. Oyskiy, t. 31-3-56 Head 1 ks Deputy hands
3 Lykhin Evgeniy Anatolievich 1971 PU - 75, Kazantsevo village With. Kazantsevo, t. 2-88-70 Head 1 ks Navigator
4 Kostenko Oleg Anatolievich 1987 Student ESH 1 With. Ermakovskoe st. Red Partisans, 63 n/a pom. caretaker
5 Filatov Ruslan Valerievich 1987 ESH student ¦1 With. Ermakovskoe st. Molodezhnaya, 2-B n/a Timekeeper
6 Tselukovsky Dmitry Sergeevich 1987 ESH student ¦1 With. Ermakovskoe n/a No
7 Kuzmin Andrey Sergeevich 1987 ESH student ¦1 With. Ermakovskoe st. Molodezhnaya, 19 n/a Photographer
8 Verfel Yana Evgenievna 1987 ESH student ¦1 With. Ermakovskoye, st. Lepeshinskikh, 2-1 Participant 1 ks caretaker
9 Lanshakova Oksana Andreevna 1987 ESH student ¦1 With. Ermakovskoe st. Lenina, 81-4 n/a Chronicler
10 Mishina Yulia Nikolaevna 1987 ESH student ¦1 village Ermakovskoe, st. Krupskaya, 12-1 n/a Medic
11 Khanzhina Maria Alexandrovna 1987 Student of Oysk school n/a No
12 Goncharov Ivan Sergeevich 1987 Student of Oysk School Oysky village, Ermakovsky district n/a No
13 Popov Denis Alekseevich 1987 Student of Oysk School Oysky village, Ermakovsky district n/a No
14 Anokhina Lyudmila Viktorovna 1984 With. Kuragino. PVD No
15 Makhold Svetlana Viktorovna 1984 Student of Kazantsevsky PU-75 With. Kuragino. PVD No
16 Makhold Oksana Viktorovna 1985 Student of Kazantsevsky PU-75 With. Kuragino. PVD No
17 Nesterova Lyudmila Viktorovna 1984 Student of Kazantsevsky PU-75 With. Kuragino. PVD No

7.
A copy of the report, photographic materials, and a video about the trip are stored at:
662820, Krasnoyarsk region, Ermakovsky district, village. Ermakovskoye, st. K. Marx, 129-2.
Shishkin Sergey Vasilievich.
Tel. (391-38) 2-44-09
Email: [email protected]

Travel area information

The travel area is described in detail on the following websites:

www.ergaki.krasu.ru - this site also has two types area maps, by which you can track the thread of our route.

Arrival and departure options

The Ergaki ridge is located quite close to the M-54 highway (Krasnoyarsk-Kyzyl-State border). The most commonly used entry and exit options are the Tormozakovsky Bridge and the bridge over the Tushkanchik River. In the first case, the path from the Tormozakovsky Bridge leads to the lake. Rainbow, in the second - on the lake. Svetloe (or Medvezhiy stream). These same trails are used for emergency exit from routes, as they are the shortest and easiest. Three buses from Kyzyl to Abakan pass along the road every day, and a bus from Ermakovskoye to Usinsk twice a week. They often go in summer minibuses to (from) Abakan railway station. Distance to nearest settlements- to Aradan - 40 km, to Tanzybey - 70 km. On the Tormozakovsky Bridge and at the mouth of the river. Jerboa has tourist houses (for a fee), parking lots, baths. There is a telephone with long-distance communication on the Tormozakovsky Bridge, and in the Ermak TKK house on Tushkanchik there is a walkie-talkie with direct communication with the Ministry of Emergency Situations.

Route changes and their reasons.

The route of the hike was completed completely. Two planned days were used “as intended” - during prolonged rain.

Group schedule

Days of travel date Track section Length (km) Running time (hours-minutes) Defining Obstacles Weather conditions
1 20.06.03 Tormozakovsky Bridge (614 km of the M-54 highway) - lake. Rainbow 6 2-45 No Rain, fog, cold
2 21.06.03 Radial exits to the waterfall and Hanging Stone 2 2-37 No Cloudy, no rain
3 22.06.03 Oz. Raduzhnoye - Dream parking lot 7 7-23 lane pro-intermediate (n/k), lane. Khudozhnikov-2 (1A) Sunny, hot
4 23.06.03 Radial exit - Mountain Spirits waterfall - Mountain Spirits lake - Fat Brother peak 2 4-40 Peak Fat Brother (1A) The first half of the day is sunny, the second half is windy, cloudy, then rain
5 24.06.03 Day due to bad weather - - No Heavy rain, cold, windy
6 25.06.03 Parking lot Dream - Lazurnoe Lake 4 5-10 lane Taygish-1 (1A) In the morning - rain, then - cloudy, windy, no rain, in the evening - sunny
7 26.06.03 Lake Lazurnoe - Skazka parking lot 8 3-44 lane Auxiliary (n/a) Sunny, warm, late evening - strong hail with wind
8 27.06.03 Radial exit to the Stone Castle 3 3-03 lane Auxiliary (n/a) At the beginning of the day it rains, then sunny, then cloudy, with occasional rain.
9 28.06.03 Radial access to the Bogatyr and Gratsia waterfalls 15 9-13 Mount Perevalnaya (1A), Rescuers Pass (1A) windy, cloudy, warm, no rain
10 29.06.03 Parking Fairy Tale - Strelka 8 4-23 NKT pass(1A) sunny
11 30.06.03 Strelka - Lake Bezrybnoye 25 7-35 No sunny, hot
12 1.07.03 Lake Bezrybnoe - Medvezhiy stream 15 5-55 Green pass (1A) sunny, hot
13 2.07.03 Day due to bad weather - - No Rain, thunderstorm
14 3.07.03 Bear Creek - r. Jerboa - highway M-54 (622 km). 8 2-31 No cloudy, occasional rain, sunny in the afternoon

additional information

Our group acted as a “tourist patrol”, whose task included cleaning up parking lots and trails along the group’s route from household waste, explaining to everyone who would meet us on the way the basics of correct “ecological” behavior in nature, marking the main routes . Therefore, along with the main activities of walking the route, we cleaned and sawed the paths, removed garbage, set up tourist sites (set up stationary fire pits, installed tables, awnings, dug garbage pits, etc.).

Tourist patrol motto:

Only people can clean up after animals and livestock!

Diary of the trip.

Instead of a prologue.

The passes here smell like socks -
(ours, people's)

We decided to write this diary in a more or less “free” style. We hope that all the technical information necessary for coverage in the diary will not fall into the shadow of some “lyrical-freedom” digressions. Text highlighted in this color- these are inserts from the diary of our chronicler Oksana Lanshakova.

I wrote the NOT SELECTED text (S.V. - Sergey Shishkin) based on my memories and memories inspired by reading the chronicler’s diary and watching a video about our campaign. Moreover, further in the text, these two authors will continually interrupt each other and even duplicate each other, describing the same events in different ways.
P.S.

But the numbers on cans have a slightly different meaning.

Gallery of some characters

Instructors

Other blacks and mestizos
Mouse

(Mishina Yulia)
Oksa
(Lanshakova Oksana)
Yanka the caretaker
(Werfel Jan)
Dronych
(Kuzmin Andrey)
Russia

(Filatov Ruslan)
Dimych

(Tselukovsky Dmitry)
Oleg
(Kostenko Oleg)
Masha
(Khanzhina Maria)
Lyuska-1
(Anokhina Lyudmila)
Lyuska-2

(Nesterova Lyudmila)

1 day
20062003 - number on the can.

Arrival (or departure)
"That's where the Snark is!" - Balabon exclaimed.
Pointing to the top of the mountain;
And he pulled the sailors ashore,
.
They were pulled up by their hair

(Lewis Carroll, "The Hunting of the Snark") July 20, 2003 a group of tourists consisting of 3 instructors S.V. (Sergei Vasilievich), Uncle Zhenya (Evgeniy Anatolyevich), Uncle Yura

(Yuri Evgenievich) and just beginning mountain climbers: Svetlana and Oksana Machold
- namesakes from the village. Kazantsevo Luda and Luda (Lyuska)
- namesakes (also from there) Ivan and Dan
- avid gamblers and simply pleasant people from Oysky Masha
caretaker- Little Red Riding Hood (from the same place)
- Yanka (Werfel, Ermakovskoe village) Repairman - Drone (Dronych)
(Andrey Kuzmin, Ermakovskoe village) Oleg and Dimych
- inseparable friends (Kostenko and Tselukovsky, Ermakovskoe village) Timekeeper (Rusya)
- Ruslan Filatov (Ermakovskoe village) Medic - Mouse
(Yulia Mishina, Ermakovskoe village) and a modest but observant chronicler - Oksana L.

(Lanshakova, Ermakovskoe village)
I left the wonderful village of Ermakovskoye for Ergaki. Each one had a backpack (a backpack with a bunch of pockets, two straps, a self-reset on the belt, and, if desired, a frame), equipment (harness (top and bottom), two snap hooks, a figure eight and a rope), tents - one Royal - instructor's, two Mana-2 tents from the Rock Pillars company (you can purchase the products of this company at the address: Krasnoyarsk, Lenina St., 76), two Dragon-5 tents from the St. Petersburg company Equipment, a name badge - “Tourist Patrol” (for everyone) and The Green Tie is a distinctive feature of the tourist patrol (also for everyone).


A bus from Ermakovsky brought our group to the Tormozakovsky Bridge (614 km of the Krasnoyarsk - State Border highway) at 12-00.

We landed near the Tormozakovsky Bridge (the starting point of many tourist routes), warmed up, despite the rain, had a snack right next to the highway, drove in the first one for this hike and moved to our first stop on Lake Raduzhnoe.
After a short snack right by the road, at 12-20 we hit the road.

We went there for a reason, but with a high mission to show the true path to travelers who do not know the way to the lake. I hope no one gets lost, although only the most careless (most sucker) tourist will not reach the lake following our markings, made from S.V.’s old red sweatpants, cut into ribbons. The whole road to the lake was pleasant, except for the occasional rain, constant dampness and fog, the path was broken into mud, with which we were already smeared up to the carbines (or even higher).

Setting up the robots.txt file

robots.txt- a special file intended for search engines. It specifies the indexing parameters for a specific site. If you want your forum to be indexed correctly, then you cannot ignore the presence of this file. I’ll try to describe the procedure for creating robots.txt, specialized for phpBB forums.

Prohibition of indexing

First, you need to prohibit the indexing of all service pages that do not contain unique content and only reduce the relevance of the forum. Indexing is prohibited using the directive Disallow: with an argument in the form of a page (or a template of pages) that does not need to be indexed. Service pages in phpBB are, for example ucp.php (Personal section), faq.php (FAQ), search.php (Search), memberlist.php (Users). The code we need:

User-agent: *
Disallow: /faq.php
Disallow: /mcp.php
Disallow: /memberlist.php
Disallow: /posting.php
Disallow: /report.php
Disallow: /search.php
Disallow: /style.php
Disallow: /ucp.php

Also for phpBB it is worth prohibiting links to specific messages from indexing. They look like this - viewtopic.php?p=54#p54. To do this, we just need to specify just one line in robots.txt, using * (asterisk) to specify the template:

Disallow: /viewtopic.php?p=*

You can also prohibit the first pages of topics from indexing, since a link to a topic without specifying a page parameter leads directly to it, so additionally specifying the first page as a parameter does not make sense - you get the same content on different links. Links to the first pages look like viewtopic.php?f=69&t=724145&start=0. Therefore, to disable indexing you need to use the following code:

Disallow: /viewtopic.php?f=*&t=*&start=0$

When viewing each topic, 2 links are displayed below, leading to adjacent topics - the previous and next one in the list. For such links the parameter is used view, which has the corresponding values view=next And view=previous. It is also better to prohibit such links for indexing:

Disallow: /viewtopic.php?f=*&t=*&view=next

Specifying a sitemap file

To speed up the indexing of new pages and re-indexing of old ones, sitemap files are very helpful. Built-in sitemap in phpBB3 this moment no, but you can install one of the existing sitemap generator mods for the forum (for example, the Sitemap FX I wrote). If you don’t have a sitemap and don’t plan to install one, you can skip this point. The rest need to write a directive Sitemap: with the path to the sitemap file as an argument:

Sitemap: /sitemap.php

You can specify several sitemaps at once if you have them generated in several files:

Sitemap: /forum/sitemap/01.xml
Sitemap: /forum/sitemap/02.xml

Specifying intervals between robot calls

Sometimes it happens that the robot, when indexing your forum, creates too much load on the server, which can result in bad consequences, for example, a temporary shutdown of the server. To correct this situation, a directive was introduced Crawl-delay, which sets timeouts when robots access the site. The argument of this directive is the time in seconds, more often than which the robot should not access the site (less often, it can). If we want to specify a timeout, for example, 5 seconds, then we need to put the following code in our robots.txt:

Specifying dynamic parameters from url

PhpBB has been using sessions for quite a long time, which are added to links on the forum as a parameter sid=. If cookies are configured correctly on the forum, this parameter will appear in the address only once, then it will be recorded in the cookie. In addition, for all search engines registered on the forum in the group "Bots", sessions are disabled automatically. However, you can play it safe by registering the session identifier as a dynamic parameter in the robots.txt file - and then the robots will not take it into account when indexing pages. For this purpose the directive is used Clean-param, about which I already wrote. She has two arguments. The first argument is the actual dynamic parameter in the url. The second argument is the path prefix of the pages on which this parameter can be used. Therefore, we get the following code for robots.txt:

Clean-param: sid /index.php

Specifying the Primary Host

For Yandex, you can also specify the main host of the site. The fact is that each site can be accessed at several addresses; as an example, phpbbguru.net/ and phpbbhacks.ru/ lead to the same site. However, the search engine will only take into account one address, which will be displayed in the search results. Directive Host: with an argument in the form of the site address, you can specify the recommended address for the search engine (since, according to Yandex, this directive is not a decisive factor in determining the main host of the site, but it is of great importance).

And despite the fact that almost all forums are available at only one address, I recommend not ignoring this directive for at least two reasons. Firstly, from the point of view of Yandex, forum addresses from www. and without it are different hosts. Therefore, if you promote your forum with an address without www, but in Yandex it is indexed with www., then there will be little good. Secondly, some dishonest people can sometimes merge your forum and their domain. They buy a domain and host a full copy of your forum on it. Search system sees two identical forums with different addresses, and mistakes them for mirrors of the same forum. In this case, there is a high possibility of identifying the address of the attacker as the main host, and then all visitors from Yandex will not end up on your forum, but on a copy of it.

Let our forum be available at www.lastforum.ru and lastforum.ru. We need to define an address without www as the main host (personally, I advise doing this because I consider the www prefix to be just a relic left over from ancient times). To do this, we need to write a directive Host especially for Yandex. Important point - directive Host must be mentioned after the directive Disallow:, so you will need this code:

User-agent: Yandex
Disallow: /faq.php
Host: lastforum.ru

It is better to place such code at the end of the robots.txt file.

The final version of robots.txt for phpBB

Taking into account all of the above, you can create a complete version of the robots.txt file for the phpBB 3 forum. As an example, I’ll take the already mentioned lastforum.ru:

User-agent: *
Disallow: /faq.php
Disallow: /mcp.php
Disallow: /memberlist.php
Disallow: /posting.php
Disallow: /report.php
Disallow: /search.php
Disallow: /style.php
Disallow: /ucp.php
Disallow: /viewtopic.php?p=*

Disallow: /viewtopic.php?f=*&t=*&view=previous
Sitemap: /sitemap.php
Clean-param: sid /index.php
Clean-param: sid /viewforum.php
Clean-param: sid /viewtopic.php

User-agent: Yandex
Disallow: /faq.php
Disallow: /mcp.php
Disallow: /memberlist.php
Disallow: /posting.php
Disallow: /report.php
Disallow: /search.php
Disallow: /style.php
Disallow: /ucp.php
Disallow: /viewtopic.php?p=*
Disallow: /viewtopic.php?f=*&t=*&start=0$
Disallow: /viewtopic.php?f=*&t=*&view=next
Disallow: /viewtopic.php?f=*&t=*&view=previous
Host: lastforum.ru
Sitemap: /sitemap.php
Clean-param: sid /index.php
Clean-param: sid /viewforum.php
Clean-param: sid /viewtopic.php

Robots.txt file location

The robots.txt file should only be located in the root of the site/forum. Considering that forums can be located in three ways - separately, on a subdomain and in a directory, you need to place robots.txt accordingly. In the case of a separate forum, as well as a forum on a subdomain, the robots.txt file must be located in the root of the forum (the same folder where the file is located config.php). If the forum is located in a subdirectory of the site, then robots.txt should be located in the root of the site, and all arguments inside robots.txt should be written in accordance with the path to them from the root. That is, if the forum is located in the forum/ folder (example.com/forum/), then the previous robots.txt example will take the following form:

User-agent: * Disallow: /forum/faq.php
Disallow: /forum/mcp.php

Disallow: /forum/posting.php
Disallow: /forum/report.php
Disallow: /forum/search.php
Disallow: /forum/style.php
Disallow: /forum/ucp.php




Sitemap: /forum/sitemap.php


User-agent: Yandex
Disallow: /forum/faq.php
Disallow: /forum/mcp.php
Disallow: /forum/memberlist.php
Disallow: /forum/posting.php
Disallow: /forum/report.php
Disallow: /forum/search.php
Disallow: /forum/style.php
Disallow: /forum/ucp.php
Disallow: /forum/viewtopic.php?p=*
Disallow: /forum/viewtopic.php?f=*&t=*&start=0$
Disallow: /forum/viewtopic.php?f=*&t=*&view=next
Disallow: /forum/viewtopic.php?f=*&t=*&view=previous
Host: lastforum.ru
Sitemap: /forum/sitemap.php
Clean-param: sid /forum/index.php
Clean-param: sid /forum/viewforum.php
Clean-param: sid /forum/viewtopic.php

The article describes the functionality that is available in PHP (relevant for 5.3.x) for handling errors of all types, including code interpretation errors (E_ERROR, E_PARSE, E_WARNING, etc). This processing will help you to display the page in a controlled manner if such problems occur. The article contains many descriptions and working examples (architecture) for immediate use in your software product. In the end, the site was broken a little, well, it’s necessary to inform the search engine about this with the heading 4xx or 5xx and amuse the user, instead of returning a white screen (or worse, a screen with sacred information, for hackers) with the response 200 Ok.

The idea to write this topic arose when I bravely asked 2 questions:

  • Question about intercepting warnings and outputting errors to a specified location in the template
  • Question about catching critical errors that cause script execution to just stop
By my karma and adding to favorites, I realized that they turned out to be interesting for the PHP habra community. For this reason, I decided to formalize the solutions to these issues in the form of an article, so that it would be easier and more comprehensive for people and search engines to find the information they need.

If you are interested, the details are under the cut...

Reasons for use

The user/search engine needs a clear answer that there is a problem on the server. Without using a certain feng shui, this is quite difficult to achieve, and sometimes impossible. Here I shed light on all this, and I’m also leaving a note for myself, since a week ago I didn’t know what to do, and, probably, many beginners will also be discouraged.

Function descriptions

This functionality is available in PHP to handle errors and control output. Here is a description of their goodies and shortcomings. I will not provide documentation, I will only refer to its pages and describe my opinion. All that will be given is only a small part; I will provide links to the relevant sections of the documentation at the end of the article. So we meet:

- Control of non-critical errors: comments, warnings, user errors. In general, everything that does not terminate the interpretation abnormally.
set_error_handler - Sets a user-defined error handler.
It is needed to write all such errors to the log. If you don’t set it, then it won’t be written to the log, but I always want to know in what combat situations comments and warnings can be triggered. That is, it allows the user to automatically test the product and he will not even notice it.
If the function is not specified, then PHP only tries to display data on the screen, and if this is not given to it, then no signs of life arise from these types of errors at all.

- Control, exceptions: is an error of type E_ERROR.
set_exception_handler - Sets a custom exception handler
Well, I don’t know why this was invented at all, when there is what is described below and simply handling an error of the Exception type. So I'm telling you that it simply exists. It catches the critical exception error and allows you to do something about it. In any case, the script ends. Its default operation is enough for me personally (writes to logs, tries to display). I wouldn’t redefine it at all, otherwise I’d have to write about the exception that happened in the logs myself.

- Output control functions: Here I will describe 3 functions that you should know for different reasons. For example, for performance problems or for header output problems. In our case, we need to display error headers.

Conditions
There is a file with code that runs first or before the code in which an error may appear, and this file and all files before it are 100% debugged with the impossibility of an error appearing. This is the condition that would make it easier - without errors until all the registrations of the above functions have passed. This file describes these error control techniques in a complex. The buffer is monitored; if there is an error, then reset the buffer and display an error.
Code with comments
I’ll add on my own that I haven’t tested the code, since this is a simplified diagram of what I have in the code, comments are welcome

 

It might be useful to read: