Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | schurzi’s |
Description | Skip to content schurzi’s blog Suche Navigation Running a Cronjob every first Monday of a Month Geschrieben von Martin Schurz am Dienstag, 7. April 2015 W |
Keywords | N/A |
WebSite | drachen-server.de |
Host IP | 138.201.181.5 |
Location | Germany |
Site | Rank |
gleitschirm-forum.ch | 25,424,205 |
drachenforum.net | 1,687,075 |
drachen-tarot.de | 0 |
superdrachen.hpage.com | 0 |
Euro€1,102
Zuletzt aktualisiert: 2022-08-21
drachen-server.de hat Semrush globalen Rang von 41,726,203. drachen-server.de hat einen geschätzten Wert von € 1,102, basierend auf seinen geschätzten Werbeeinnahmen. drachen-server.de empfängt jeden Tag ungefähr 551 einzelne Besucher. Sein Webserver befindet sich in Germany mit der IP-Adresse 138.201.181.5. Laut SiteAdvisor ist drachen-server.de sicher zu besuchen. |
Kauf-/Verkaufswert | Euro€1,102 |
Tägliche Werbeeinnahmen | Euro€19,285 |
Monatlicher Anzeigenumsatz | Euro€6,612 |
Jährliche Werbeeinnahmen | Euro€551 |
Tägliche eindeutige Besucher | 551 |
Hinweis: Alle Traffic- und Einnahmenwerte sind Schätzungen. |
Host | Type | TTL | Data |
drachen-server.de. | A | 86399 | IP: 138.201.181.5 |
drachen-server.de. | NS | 86400 | NS Record: nsd1.schlundtech.de. |
drachen-server.de. | NS | 86400 | NS Record: nsb1.schlundtech.de. |
drachen-server.de. | NS | 86400 | NS Record: nsa1.schlundtech.de. |
drachen-server.de. | NS | 86400 | NS Record: nsc1.schlundtech.de. |
drachen-server.de. | MX | 86400 | MX Record: 10 drachen-server.de. |
drachen-server.de. | TXT | 86400 | TXT Record: v=spf1 mx a ip4:217.9.117.244/32 ip4:138.201.181.5/32 a:drachen-server.de -all |
Skip to content schurzi’s blog Suche Navigation Running a Cronjob every first Monday of a Month Geschrieben von Martin Schurz am Dienstag, 7. April 2015 When it comes to automation one of your first thoughts is usually Cron. With Cron you can schedule you tasks in many different ways and almost everything is possible, but some things can be tricky. For example, scheduling a job to run on every first Monday of a month. The following line should do the trick, or maybe not? 0 14 1-7 * Mon /bin/task Reading this in the usual way this should produce: on 14:00 every 1st to 7th day of a month, if this day is a Monday, /bin/task will be executed. Wrong! Take a look at the documentation and you will understand the "correct" behaviour. $ man 5 crontab ... Note: The day of a command’s execution can be specified by two fields — day of month, and day of week. If both fields are restricted (ie, aren’t *), the command will be run when either field matches the current time. For example, "30 4 1,15 * |
HTTP/1.1 302 Found Date: Mon, 20 Dec 2021 10:17:29 GMT Server: Apache Location: https://drachen-server.de/ Content-Type: text/html; charset=iso-8859-1 HTTP/1.1 200 OK Date: Mon, 20 Dec 2021 10:17:30 GMT Server: Apache Strict-Transport-Security: max-age=15768000 X-Powered-By: PHP/7.4.16 Status: 200 OK Set-Cookie: s9y_6cc804b4e4c904d79825fc8e41605606=vr2dut01clbkc27rlnp5bu6a5j; path=/ Expires: 0 Cache-Control: private, pre-check=0, post-check=0, max-age=0 Pragma: no-cache Set-Cookie: s9y_6cc804b4e4c904d79825fc8e41605606=2a4bckupnoen8e1ar98h345qad; path=/ X-Session-Reinit: true X-Blog: Serendipity Vary: Accept-Encoding Content-Type: text/html; charset=UTF-8 |