search

Benjamin-Loison / termux-app

Termux - a terminal emulator application for Android OS extendible by variety of packages.
https://f-droid.org/en/packages/com.termux
Other
0 stars 0 forks source link

[Bug]: Crontab does not work since `lineage-21.0-20240217-nightly-FP4` update #13

Closed Benjamin-Loison closed 6 months ago

Benjamin-Loison commented 6 months ago

bens_folder/termux/os.txt:

...
Sat Feb 17 00:00:00 CET 2024
20.0-20240207-NIGHTLY-FP4
Sun Feb 18 00:00:00 CET 2024
20.0-20240207-NIGHTLY-FP4

bens_folder/termux/memAvailable.txt:

...
Sun Feb 18 00:25:00 CET 2024
MemAvailable:    5355964 kB
Sun Feb 18 00:26:00 CET 2024
MemAvailable:    5454744 kB
history
...
73613  18/02/24 00:25:07 awk '{print $1}' < ~/.android/adbkey.pub | base64 --decode | md5sum
73614  18/02/24 00:26:27 adb -d reboot sideload
...
73617  18/02/24 00:27:04 adb -d sideload lineage-21.0-20240217-nightly-FP4-signed.zip
...
tree $PREFIX/var/service/crond/
/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.

Problem description

Probably related to #12.

Steps to reproduce the behavior.

Not read.

What is the expected behavior?

No response

System information