Cron job keeps inserting new lines
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
Research direction
Start with root/usr/local/bin/init.sh at line 8 and inspect how the cron entry is added when the container starts. Recreate a container startup or restart and verify that the cron job is present only once, without duplicate lines.
Written by the indexing model from the issue text.
Description
Since plex-sync-job is not part of the new job added ($CRON_SCHEDULE /usr/local/bin/job.sh >> /var/log/cron.log 2>&1), every time the container starts up, it adds a new job.
- Dominant language
- Shell
- Stars
- 5
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Fmstrat/plex-sync
All issues in Fmstrat/plex-sync
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
huggingface/Repo2RLEnv#163 · 1 comment ·
-
setup tools wizard offers no GitHub auth path, and setup summary doesn't recognize `gh` CLI auth Openarea/auth comp/cli P3 tool/skills type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
NousResearch/hermes-agent#121131 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
bradcypert/plum#53 ·
-
tmp_watchgod.sh exceeds the 1000-line cap; the Zone A guard helpers are a clean extraction seam Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
WingedGuardian/GENesis-AGI#2301 ·