Closed GliderGeek closed 4 years ago
Yes it did. In your test, did you remove the service first?
Yes it did. In your test, did you remove the service first?
I did.
[evan@blackbox remarkable_news] ssh root@10.11.99.1
reMarkable
╺━┓┏━╸┏━┓┏━┓ ┏━╸┏━┓┏━┓╻ ╻╻╺┳╸┏━┓┏━┓
┏━┛┣╸ ┣┳┛┃ ┃ ┃╺┓┣┳┛┣━┫┃┏┛┃ ┃ ┣━┫┗━┓
┗━╸┗━╸╹┗╸┗━┛ ┗━┛╹┗╸╹ ╹┗┛ ╹ ╹ ╹ ╹┗━┛
[root@remarkable ~] rm /etc/systemd/system/renews.service
[root@remarkable ~] systemctl stop renews
Warning: The unit file, source configuration file or drop-ins of renews.service changed on disk. Run 'systemctl daemon-reload' to reload units.
[root@remarkable ~] systemctl daemon-reload
[root@remarkable ~] logout
Connection to 10.11.99.1 closed.
[evan@blackbox remarkable_news] make install_nyt
Enter passphrase for /home/evan/.ssh/id_rsa:
Identity added: /home/evan/.ssh/id_rsa (/home/evan/.ssh/id_rsa)
Failed to stop renews.service: Unit renews.service not loaded.
renews.arm 100% 11MB 5.9MB/s 00:01
renews.service 100% 340 372.3KB/s 00:00
Pseudo-terminal will not be allocated because stdin is not a terminal.
[evan@blackbox remarkable_news] ssh root@10.11.99.1
reMarkable
╺━┓┏━╸┏━┓┏━┓ ┏━╸┏━┓┏━┓╻ ╻╻╺┳╸┏━┓┏━┓
┏━┛┣╸ ┣┳┛┃ ┃ ┃╺┓┣┳┛┣━┫┃┏┛┃ ┃ ┣━┫┗━┓
┗━╸┗━╸╹┗╸┗━┛ ┗━┛╹┗╸╹ ╹┗┛ ╹ ╹ ╹ ╹┗━┛
[root@remarkable ~] systemctl status renews
● renews.service - New York Times
Loaded: loaded (/etc/systemd/system/renews.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2020-05-01 20:53:19 UTC; 15s ago
Main PID: 378 (renews.arm)
CGroup: /system.slice/renews.service
└─378 /home/root/renews.arm -output /usr/share/remarkable/suspended.png -verbose -ti>
May 01 20:53:19 remarkable systemd[1]: Started New York Times.
i think i might have reacted to quickly on the question "Did this actually stop your installation?". i am not so sure anymore. will try again
So what's the news?
If there's still a problem, let me know.
This was a problem for me too
Did this actually stop your installation? I tested it on my machine and it continued on.