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

Warning Error #109

Open
ProfessorManhattan opened this issue Aug 30, 2023 · 2 comments
Open

Warning Error #109

ProfessorManhattan opened this issue Aug 30, 2023 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@ProfessorManhattan
Copy link
Contributor

❔ What are you experiencing an issue with?

Latest Release

❔ Version

N/A

🐞 Description

I see the following warning message when setting up one of the system services on macOS:

 ○ Adding ~/.config/rclone/rcloneignore to /etc/rcloneignore
 ○ Adding ~/.config/rclone/system-rclone.conf to /etc/rclone.conf
 ○ Ensuring Rclone mount-on-reboot definitions are in place
 ○ Adding ~/Public as S3 bucket mount, enabled at boot
Warning: Expecting a LaunchAgents path since the command was ran as user. Got LaunchDaemons instead.
`launchctl bootstrap` is a recommended alternative.
✔  user launchctl load successful
 ○ Creating group and user rclone on macOS...
 ○ Group rclone already exists.
 ○ User rclone already exists
 ○ Group and user rclone created successfully on macOS

Add in logic that implements the recommended alternative.

⏺️ Steps To Reproduce

No response

📒 Relevant Log Output

No response

💡 Possible Solution

No response

@ProfessorManhattan ProfessorManhattan added the bug Something isn't working label Aug 30, 2023
@ilewin
Copy link

ilewin commented Nov 10, 2023

i'll give it a try

@ProfessorManhattan
Copy link
Contributor Author

Hey @ilewin - if you're going to fix this issue - I don't think it's a fatal error but its outputting the warning message Warning: Expecting a LaunchAgents path since the command was ran as user. Got LaunchDaemons instead. launchctl bootstrap is a recommended alternative. If there is a way of doing the same thing without getting the warning I'd like to do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants