Can you enable SSH, and then try SSH into the box once it hangs?
Any OOMKiller messages in dmesg/journalctl? Do you have swap space?
Nothing in the logs jumped out at me, hopefully someone else can help you.
Can you enable SSH, and then try SSH into the box once it hangs?
Any OOMKiller messages in dmesg/journalctl? Do you have swap space?
Nothing in the logs jumped out at me, hopefully someone else can help you.
Looks like you need to use [
on friendica? ]
~~Take a photo of the output? First few lines are most important, but ideally all would be good. ~~
Edit: actually, dont want to crowd the kitchen, good luck!
Yup, didn’t read your comment properly, but that will also work.
Give the output of route
, maybe there is a left over route.
You use a console? Noob… Magnetised needle is where the real productivity is at.
Still a bit open ended. Web browser finger printing is probably going to be quite specific, unless you have a browser that avoids fingerprinting.
There is a trust issue, you need to trust the userland packagers to not build in any additional tracking, but its pretty unlikely that they’ll do that given its a tiny project.
Privacy is also multifaceted, and its never going to be as simple as “use this distro”. The techniques for online tracking are changing and evolving all the time.
This is a bit of a “how long is a piece of string” question, security is multifaceted.
From what I understand, it uses your phones kernel, so if its out of date or vulnerable, that might be a problem, and you may not be able to fix that.
Conversely, its running inside android, so the android hardening might make it more secure.
What are you specifically concerned about? Firewall? Zero days? Antimalware?
/etc/passwd
: you may be able to get to this from the GUI file manager.
If not, open a terminal and type: cat /etc/passwd
. Copy the relevant lines.
To test the login, from a terminal, type su otheruser
, replace otheruser with the username from /etc/passwd
. It should ask for a password, put that in and it should log you in. Type whoami
and make sure its the same username as you expected. Paste any errors here.
I think that was meant to be a reply to me, so I’ll respond.
Technically, /etc/passwd
can have encrypted passwords in it, but as far as I’m aware, no distro has done that in decades, so realistically its not that risky. It does expose the user names though.
Can you share the lines from /etc/passwd
for your user and the user your adding? Despite its name, there are no passwords here, that is in /etc/shadow
Edit: can you su
to login as the user?
I think it perfectly highlights what can happen when the risk/severity is blown out of proportion. People will latch on to that and waste precious time and energy defending that.
If the original guy had just published “CUPS has a RCE, firewall it if you haven’t already”, the issue would have been patched in the next release, and the world would have kept turning.
It was a really cool bug, and a great find, it didn’t need the hype
Didn’t know that, but makes sense.
if you are from Russia, it is impossible to convince the US that you are not a part of a state-sponsored entity
This quote from your article does nail the problem on the head though.
Excellent, thanks for the update!
Russians can still contribute, they just can’t be direct maintainers.
Nothing will likely change in the short term.
Can you make your docker service start after the NFS Mount to rule that out?
A restart policy only takes effect after a container starts successfully. In this case, starting successfully means that the container is up for at least 10 seconds and Docker has started monitoring it. This prevents a container which doesn’t start at all from going into a restart loop.
https://docs.docker.com/engine/containers/start-containers-automatically/#restart-policy-details
If your containers are crashing before the 10 timeout, then they won’t restart.
His wife was a little less impressed /s
Hans Reiser was convicted of murdering his wife. He is (was?) in jail.
Linux distros are getting mature
I think this is exactly it. Back in the early days of Fedora and Ubuntu a new release often meant major bug fixes, new software, and possibly a significant qol/usability changes and performance changes. Now, its all new versions of stable software, which all behave roughly the same. Which is exactly what you want in a daily driver OS. Stability.
There are android clients, probably one for iOS as well. If you are getting OOM killed, you need to work out what is using all your memory. The OOM killer is pretty indiscriminate, and will murder processes randomly.
Maybe keep system monitor up and keep an eye on memory usage?