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

Process name #35

Closed
GregTheGreek opened this issue Jul 27, 2022 · 4 comments
Closed

Process name #35

GregTheGreek opened this issue Jul 27, 2022 · 4 comments

Comments

@GregTheGreek
Copy link

After the remarkable goes to sleep Im finding the process gets a bit funky, and i can't connect to it.

ps aux doens't seem to work within the remarkable, any idea what the process might be for me to kill it manually?

@owulveryck
Copy link
Owner

owulveryck commented Jul 28, 2022

I usually launch the process with a nohup, and I have no problem connecting to it after a sleep period.
There is also a systemctl script you can install that will launch it and monitor it, but as it disappear after an update I did not document it. Besides, there is an ugly sleep in this script that slows the startup of the device (an issue it opened to fix this, see #21)
I think that a pkill command could do the trick as well.

I cannot tell you more right now because I do not have the device with me this week.

Hope it helps anyway.

@GregTheGreek
Copy link
Author

Thanks I ended up clearing up my issues witha restart! Also happened to use the wrong IP haha. This tool works amazingly well!

@2Belette
Copy link

@owulveryck thanks for the project !
I added this systemd unit :

goMarkableStream.service 
[Unit]
Description=goMarkableStream
Requires=xochitl.service
After=xochitl.service network.target

[Service]
Environment="RK_SERVER_BIND_ADDR=:443" "RK_SERVER_USERNAME=xxx" "RK_SERVER_PASSWORD=xxx"
ExecStart=/home/root/goMarkableStream
ExecStartPre=/bin/sleep 30
Restart=always

[Install]
WantedBy=multi-user.target

It is all working fine at boot, when the tablet is in light sleep, for a couple of minutes it is fine, but after that when I unlock the tablet, I got this :

2023 08 21 09 51 07

I know the connectivity is all fine (I am in ssh in //), refreshing is not solving, restarting the service is doing the trick.

Any idea?

@2Belette
Copy link

Seems to be solved with this version of the systemd unit

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

No branches or pull requests

3 participants