/data/data/com.termux/files/usr/var/service/crond/
├── log
│ ├── run
│ └── supervise
│ ├── control
│ ├── lock
│ ├── ok
│ ├── pid
│ ├── stat
│ └── status
├── run
└── supervise
├── control
├── lock
├── ok
├── pid
├── stat
└── status
4 directories, 14 files
while HTTP server works:
tree $PREFIX/var/service/httpd/
/data/data/com.termux/files/usr/var/service/httpd/
├── log
│ ├── run
│ └── supervise
│ ├── control
│ ├── lock
│ ├── ok
│ ├── pid
│ ├── stat
│ └── status
├── run
└── supervise
├── control
├── lock
├── ok
├── pid
├── stat
└── status
4 directories, 14 files
the identical file structure (verified with ctrl + f) should demonstrate that crontab works.
Let us test the specific crontab shell and afterwards clear crontab content to ease its execution
Well LemnosLife VPS matrix-commander lock (the lock file was blocking) was the issue it seems.
Using absolute path in crontab for SHELL and the shebang were also necessary it seems.
bens_folder/termux/os.txt
:bens_folder/termux/memAvailable.txt
:while HTTP server works:
the identical file structure (verified with ctrl + f) should demonstrate that crontab works.
Let us test the specific crontab shell and afterwards clear crontab content to ease its execution
Well LemnosLife VPS matrix-commander lock (the lock file was blocking) was the issue it seems.
Using absolute path in
crontab
forSHELL
and the shebang were also necessary it seems.Problem description
Probably related to #12.
Steps to reproduce the behavior.
Not read.
What is the expected behavior?
No response
System information