octoleo/telegram-bot-bash
1
1
Fork 0
mirror of https://github.com/octoleo/telegram-bot-bash.git synced 2024-11-29 18:53:52 +00:00
Code Issues Projects Releases Wiki Activity

remove count.jssh.flock after cleanup

Browse Source
This commit is contained in:
Kay Marquardt (Gnadelwartz) 2020-06-11 12:37:36 +02:00
parent e663979206
commit 15f6da85dc
3 changed files with 7 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
bashbot.sh
View File

@ -11,7 +11,7 @@
# This file is public domain in the USA and all free countries. # This file is public domain in the USA and all free countries.
# Elsewhere, consider it to be WTFPLv2. (wtfpl.net/txt/copying) # Elsewhere, consider it to be WTFPLv2. (wtfpl.net/txt/copying)
# #
#### $$VERSION$$ v0.96-pre-38-g15928bd #### $$VERSION$$ v0.96-pre-40-ge663979
# #
# Exit Codes: # Exit Codes:
# - 0 sucess (hopefully) # - 0 sucess (hopefully)
@ -812,6 +812,7 @@ start_bot() {
fi fi
# cleanup countfile on startup # cleanup countfile on startup
jssh_deleteKeyDB "CLEAN_COUNTER_DATABASE_ON_STARTUP" "${COUNTFILE}" jssh_deleteKeyDB "CLEAN_COUNTER_DATABASE_ON_STARTUP" "${COUNTFILE}"
[ -f "${COUNTFILE}.jssh.flock" ] && rm -f "${COUNTFILE}.jssh.flock"
########## ##########
# bot is ready, start processing updates ... # bot is ready, start processing updates ...

6
doc/3_advanced.md
View File

@ -213,7 +213,7 @@ e.g. resend on throttling. In addtion every send error is logged in logs/ERROR.l
#### Trasmission results #### Trasmission results
On every message send to telgram (transmission) the results are provided in bash variables, like its done when a new message On every message send to telegram (transmission) the results are provided in bash variables, like its done when a new message
is received. is received.
**Note**: the values of the variables contains always the result of the LAST transmission to telegram, **Note**: the values of the variables contains always the result of the LAST transmission to telegram,
@ -229,7 +229,7 @@ every send action will overwrite them!
By default you don't have to care about retry, as bashbot resend the message after the requested time automatically. By default you don't have to care about retry, as bashbot resend the message after the requested time automatically.
Only if the retry fails also an error is returned. The downside is that send_message functions will wait until resend is done. Only if the retry fails also an error is returned. The downside is that send_message functions will wait until resend is done.
If you want to disable automtic error processing and handle all errors manually (or don't care) If you want to disable automatic error processing and handle all errors manually (or don't care)
set ```BASHBOT_RETRY``` to any no zero value. set ```BASHBOT_RETRY``` to any no zero value.
[Telegram API error codes](https://core.telegram.org/api/errors) [Telegram API error codes](https://core.telegram.org/api/errors)
@ -274,5 +274,5 @@ Note: If you disable automatic retry, se above, you disable also connection prob
#### [Prev Getting started](2_usage.md) #### [Prev Getting started](2_usage.md)
#### [Next Expert Use](4_expert.md) #### [Next Expert Use](4_expert.md)
#### $$VERSION$$ v0.96-pre-39-gb6e9f9e #### $$VERSION$$ v0.96-pre-40-ge663979

4
doc/7_develop.md
View File

@ -89,7 +89,7 @@ example_echo() {
} }
``` ```
An SEND event is executed when a Message is send tomtelegram. An SEND event is executed when a Message is send to telegram.
* BASHBOT_EVENT_SEND is exceuted if data is send or uploaded to Telegram server * BASHBOT_EVENT_SEND is exceuted if data is send or uploaded to Telegram server
@ -338,5 +338,5 @@ fi
#### [Prev Function Reference](6_reference.md) #### [Prev Function Reference](6_reference.md)
#### $$VERSION$$ v0.96-pre-39-gb6e9f9e #### $$VERSION$$ v0.96-pre-40-ge663979