Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question]: nginx log location #7146

Closed
skrashevich opened this issue Jul 13, 2023 · 6 comments
Closed

[Question]: nginx log location #7146

skrashevich opened this issue Jul 13, 2023 · 6 comments
Labels
question Further information is requested stale

Comments

@skrashevich
Copy link
Contributor

Describe the problem you are having

Is there any serious reason to save the nginx (and other like go2rtc) logs in /dev/shm instead of, for example, /tmp?

Version

0.13-dev latest

Frigate config file

logger:
  default: warning
go2rtc:
  #log: isn't set


### Relevant log output

```shell
``

FFprobe output from your camera

``

Frigate stats

No response

Operating system

UNRAID

Install method

Docker CLI

Coral version

USB

Network connection

Wired

Camera make and model

``

Any other information that may be helpful

No response

@NickM-27 NickM-27 added question Further information is requested and removed support triage labels Jul 13, 2023
@NickM-27
Copy link
Collaborator

The original PR is here: #4587

I believe it had to do with permission issues with S6 and /tmp.

@NickM-27
Copy link
Collaborator

@felipecrs do you remember the specific reason?

@felipecrs
Copy link
Contributor

Yes, it's to avoid writing data to the sdcard in Raspberry Pis. This writes to RAM.

@skrashevich
Copy link
Contributor Author

why not tmpfs?

@felipecrs
Copy link
Contributor

AFAIK /dev/shm is tmpfs.

But that's to not require an additional mount (which is not supported by HA add-on, I think).

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Aug 13, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested stale
Projects
None yet
Development

No branches or pull requests

3 participants