Thefrank

Results 127 comments of Thefrank

```sh root@freebsd:~/pwsh # uname -a FreeBSD freebsd 13.2-RELEASE-p4 FreeBSD 13.2-RELEASE-p4 GENERIC amd64 ``` ```pwsh root@freebsd:~/pwsh # ./pwsh PowerShell 7.2.8 Copyright (c) Microsoft Corporation. https://aka.ms/powershell Type 'help' to get help. A...

Using a named pipe in Hyper-V, I was able to reproduce the issue. I am unsure the cause of it but will continue to look into it when I get...

Even more strange, using `-Command` work fine but output is looks like its for the wrong terminal emulation: ![image](https://github.com/Thefrank/freebsd-port-sooners/assets/1910378/b5bb2f03-abdb-46fa-a5bb-2f11244e3c8c) vs ![image](https://github.com/Thefrank/freebsd-port-sooners/assets/1910378/0ca5d26e-1d21-4c94-a51b-68c529408c34) EDIT: setting NO_COLOR=1 fixes some of it ![image](https://github.com/Thefrank/freebsd-port-sooners/assets/1910378/09e992f2-d633-4077-9050-61f5a0905d49)

@DNS the shell error is likely a hard-coded usage of a login shell that I made long before FreeBSD 14 was -Release ready. This should be simple to correct but...

@SteveL-MSFT is there still a plan on removing this as dependency? If not, I have some FreeBSD related fixes I would like to make.

Does restarting the jail solve issue? Does the issue return some point after restarting jail? If the answer is "yes" to both, then try turning off file monitoring in jellyfin...

> That being said how to disable the file monitoring? Disable the automatic scans? From your profile menu select "Dashboard" under "Administration". Click Libraries. On each library click the triple...

#35 does seem related if not exactly the issue at hand here. I assume you are upgrading from an older version to a newer one? As for jellyfin's handling of...

Very strange. I can not reproduce this with `iocage`. ``` iocage create -n jellytest vnet="on" dhcp="on" allow_mlock="1" defaultrouter=192.168.0.1/24 -r 13.2-RELEASE iocage start jellytest iocage exec jellytest "pkg install jellyfin" iocage...

~how is PATH set in `/etc/login.conf` for the "default" class?~ ~edit: and "daemon"~ These should not matter anyways does making a sym link for ffmpeg into `/usr/bin` resolve the issue...