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

lib will not work when used in a deamon/service #18

Open
ChriD opened this issue Nov 5, 2019 · 4 comments · May be fixed by #19
Open

lib will not work when used in a deamon/service #18

ChriD opened this issue Nov 5, 2019 · 4 comments · May be fixed by #19

Comments

@ChriD
Copy link

ChriD commented Nov 5, 2019

Hi,

The lib wont work on a DietPi linux distro when used in a deamon / service
The logger you use tries to write/open a file and does not have the permisisons to do that.
An uncaught error occurred: Error: ENOENT: no such file or directory, open '/logs/all.log

I do not want to give the service i create any writable access to the filesystem

If i remove the logger instance from the lib it works fine.
I see the lib is in development and it would be nice if you consider to allow disableing the logging to file.

Thanks & Have a nice day

@margau margau linked a pull request Nov 7, 2019 that will close this issue
@margau
Copy link
Owner

margau commented Nov 7, 2019

Hi,
could you test against #19 with

log: {
    files: false
}

in the dmxnet-constructor?

Will merge and publish if successfull.
Best regards
margau

@ChriD
Copy link
Author

ChriD commented Nov 7, 2019

hi,
Did not have much time to test but it seems it does not work.
I'll check whats the problem and will get in touch later.

@she11sh0cked
Copy link
Contributor

Hi,
could you test against #19 with

log: {
    files: false
}

in the dmxnet-constructor?

Will merge and publish if successfull.
Best regards
margau

I also tried it. It still creates empty log files. Seems to be a problem in the logging library.

@ghost
Copy link

ghost commented Oct 3, 2021

@ChriD @she11sh0cked
Could both of you confirm that this issue is fixed and can be closed?

#EveryClosedIssueIsAGoodIssue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants