It sources (includes) any file found in ~/.bashrc.d/ so check that directory.
It sources (includes) any file found in ~/.bashrc.d/ so check that directory.
You’re right ofcourse.
Check that you actually have persistent storage enabled. (See man journald.conf
and search for Storage
)
Read up on the numerous parameters to journalctl. (man journalctl
)
journalctl --boot -2
will show logs from previous boot.
journalctl --since "-2 weeks" --unit=sshd
last two weeks worth of sshd logs.
No, he’s not!
Offtopic, but my son is also named Bort.
The container sees each volume as a seperate filesystem, regardless of your underlying disk setup and you cannot hardlink across filesystems.
This has huge potential. What I personally look for in a podcast solution is:
For now, I’m using Pocketcasts which pretty much does what I need, except for handling the backlog, which I do with a homemade python-script that adds backlog episodes to my playlist whenever it has less than 4 hours of playtime left, using Pocketcast’s web player REST API. The result is an endless playlist where newly released episodes are played within a few hours and older episodes are sprinkled on with no real need for micro-managing episodes in the playlist.
It looks like web/desktop players and sync is already in scope, but are there any “advanced” podcast organization features on your roadmap?
That is not correct. Prowlarr also searches Newznab-compatible providers (i.e. most nzb-indexers).
And the world is a slightly better place, momentarily.
Then it does nothing.