crontabs | : alarm_clock : A cron-like utility for Python

by robdmc Python Version: 0.2.2 License: MIT

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | crontabs Summary

crontabs is a Python library. crontabs has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can install using 'pip install crontabs' or download it from GitHub, PyPI.

Think of crontabs as a quick-and-dirty solution you can throw into one-off python scripts to execute tasks on a cron-like schedule. Crontabs is a small pure-python library that was inspired by the excellent schedule library for python. In addition to having a slightly different API, crontabs differs from the schedule module in the following ways.

Support

Quality

Security

License

Reuse

Support

crontabs has a low active ecosystem.

It has 139 star(s) with 11 fork(s). There are 5 watchers for this library.

It had no major release in the last 12 months.

There are 0 open issues and 8 have been closed. On average issues are closed in 260 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of crontabs is 0.2.2

Quality

crontabs has 0 bugs and 0 code smells.

Security

crontabs has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

crontabs code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

crontabs is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

crontabs releases are not available. You will need to build from source code and install.

Deployable package is available in PyPI.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi has reviewed crontabs and discovered the below as its top functions. This is intended to give you an instant insight into crontabs implemented functionality, and help decide if they suit your requirements.

Get the version string
Set the until until a datetime
Process date string or string
Defines the starting timestamp
Set the timer to start

Get all kandi verified functions for this library.

crontabs Key Features

No Key Features are available at this moment for crontabs.

crontabs Examples and Code Snippets

No Code Snippets are available at this moment for crontabs.

Community Discussions

Trending Discussions on crontabs

How to configure supervisor not to kill jobs started by cron in docker container

Cron jobs run ok as script but not @reboot

docker-compose stop / start my_image

crontab with ed by commands on stream, results in "no modification made"

crontab sudo docker permission denied

Fabric8 customResourceDefinitions test

Cron script doesn't work unless called by sh command

remove cron jobs along with their comment, environment which were created by Puppet by awk/sed

Docker cron scheduled job not running

Reason for separate Volume Container

QUESTION

How to configure supervisor not to kill jobs started by cron in docker container

Asked 2022-Feb-05 at 02:30

I wanted to run cron and run a few script started at a time set in crontab. I've installed cron on my docker container and wanted to add some crontab lines and cron starting in separate script. Here are fragments of my configuration

supervisord.conf

...

ANSWER

Answered 2022-Feb-05 at 02:30

Ok, I have to post an answer. I've realized that scripts working well, but it saved reports in system root directory, not on directories that I wanted.

It were because of lack of environment variables More you can read those topic, Where can I set environment variables that crontab will use?

but I've resolved my problem with adding that line at the start of 'run-crontabs.sh' script

Source https://stackoverflow.com/questions/70948070

QUESTION

Cron jobs run ok as script but not @reboot

Asked 2022-Jan-29 at 17:30

I'm running a Django (v3.1.7) application on a headless remote Ubuntu (v20.04.3) that I'm looking to have start at reboot using crontab. The script below runs all ok from the command line. I've been through here crontabs-reboot-only-works-for-root and the linked suggestions as well but still haven't identified the issue. I've added logging (see *.log below) but do not get any helpful output.

EDIT: The test screen works both from the command line and at reboot. The django and streaming screens do not work at reboot. Checking python executable with which python3 returns /usr/bin/python3. So it looks to me that I have the correct permissions for reboot.sh and cron should be able to find python3 as it is in PATH= in the crontab file.

/home/myapp/reboot.sh

...

ANSWER

Answered 2022-Jan-29 at 14:35

Suggesting to fix your crontab -l

Source https://stackoverflow.com/questions/70897306

QUESTION

docker-compose stop / start my_image

Asked 2022-Jan-10 at 12:26

Is it normal to lose all data, installed applications and created folders inside a container when executing docker-compose stop my_image and docker-compose start my_image?

I'm creating container with docker-compose up --scale my_image=4

update no. 1

my containers have sshd server running in them. When I connect to a container execute touch test.txt I see that the file was created. However, after executing docker-compose stop my_image and docker-compose start my_image a container is empty and ls -l shows absence of file test.txt

update no. 2

my Dockerfile

...

ANSWER

Answered 2022-Jan-10 at 12:26

So, after a brutal brute force debugging I realized that I lose data only when I fail to disconnect from ssh before stopping / restarting container. When I do disconnect data does not disappear after stopping / restarting

Source https://stackoverflow.com/questions/70404148

QUESTION

crontab with ed by commands on stream, results in "no modification made"

Asked 2021-Dec-28 at 11:16

I am trying to append a line to my crontab file. I know there are other ways to work around this problem, but still want to know what caused it. The command is run on raspberry pi 3 B+, raspbian lite is installed, with GNU ed 1.15, cron 3.0pl1-134+deb10u1.

The command that I'm stuck on is this:

...

ANSWER

Answered 2021-Nov-21 at 20:34

Following up on my VISUAL comment, these worked for me:

Source https://stackoverflow.com/questions/70043797

QUESTION

crontab sudo docker permission denied

Asked 2021-Nov-24 at 18:12

I have a bash script that works fine and I'm trying to run it using crontabs.

The main issue is that when I run the script it asks me for my sudo password in order to execute the docker command. Therefore, when I'm trying to execute the script using crontabs I get the following errors:

Permission denied

Got permission denied while trying to connect to the Docker daemon

This is my bash script:

...

ANSWER

Answered 2021-Nov-24 at 16:42

I assume your are runing under user $USER

You should ensure /etc/sudoers allows your script to be run by the cron user without password (NOPASSWORD option), something like :

$USER ALL=NOPASSWD:/home/user/Desktop/Projects/example/remove-inactive-users.sh

alternatively, you could also give the right to that username to call docker directly (not with sudo) : sudo usermod -aG docker $USER && exec sg docker newgrp $(id -gn) && sudo systemctl restart docker

Source https://stackoverflow.com/questions/70099692

QUESTION

Fabric8 customResourceDefinitions test

Asked 2021-Nov-05 at 08:36

I am working on Fabric8 unit test, now I am trying to create a CRD against KubernetesServer.

...

ANSWER

Answered 2021-Nov-05 at 08:36

From the code which you shared, it looks like you're using Fabric8 Kubernetes Mock Server in expectations mode. Expectations mode requires the user to set the REST API expectations. So the code shown below is setting some expectations from Mock Server viewpoint.

Source https://stackoverflow.com/questions/69830821

QUESTION

Cron script doesn't work unless called by sh command

Asked 2021-Oct-24 at 19:14

I have a script saved in file named file.sh It is executed by command

...

ANSWER

Answered 2021-Oct-24 at 19:14

The problem is your printf statement ... I'm fairly certain that you should also see error messages from rm in root's mail to the effect that e.g.: 1634986839.0000000000 Sun 24 Oct 2021 12:00:39 AM UTC /var/log/syslog.2.gz doesn't exist.

Source https://stackoverflow.com/questions/69699788

QUESTION

remove cron jobs along with their comment, environment which were created by Puppet by awk/sed

Asked 2021-Sep-13 at 21:58

Is there a way to remove/delete cron jobs created by Puppet by using awk/sed? I know that we can edit by crontab -e command manually, but this is a question for scripting. Example root cron is a file in /var/spool/cron/crontabs/root. I want to remove lines below.

...

ANSWER

Answered 2021-Sep-13 at 21:58

You would be well advised to use Puppet to remove the crontab entries that were created by Puppet.

If you have to do it via a manual-ish shell command, however, then you can do it via this sed command:

Source https://stackoverflow.com/questions/69162047

QUESTION

Docker cron scheduled job not running

Asked 2021-Aug-01 at 02:40

I am trying to use a docker container based on an Alpine image to run a scheduled cron job, following this tutorial, but after printing the statement in my startup script, the container just exits, without running my other script.

My docker-compose service is configured as follows:

...

ANSWER

Answered 2021-Aug-01 at 02:40

In the docker compose file you have

Source https://stackoverflow.com/questions/68606617

QUESTION

Reason for separate Volume Container

Asked 2021-Jun-09 at 10:30

I've found following docker composition:

...

ANSWER

Answered 2021-Jun-09 at 10:30

On modern Docker I'd never use this pattern, and in particular I'd avoid volumes_from:.

volumes_from: has the two problems of not being clear of what exactly it's mounting and not having any control over where it gets mounted. If the image for your backup had a VOLUME declaration in its Dockerfile, for example, that volume would get mounted in your cron container at the exact same path as in the backup container, even though it's not listed in this docker-compose.yml anywhere. That can lead to surprising outcomes.

Docker didn't always have named volumes. Before there were named volumes, the way to get persistent sharable storage was to create a data volume container that created an anonymous volume, and then run other containers with docker run --volumes-from ... to attach that storage. Now that named volumes exist, there's not a need to do that any more.

Source https://stackoverflow.com/questions/67898889

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install crontabs

You can install using 'pip install crontabs' or download it from GitHub, PyPI.
You can use crontabs like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: