@ilkkachu originally there was no process associated with the script itself according to ps auwx. When running through bash I got an additional process named bash ./script_name. It seemed to make sense to me, but I could be wrong.
My understanding has to be incomplete, because I thought non-disowned child processes die when the parent does, which was not the case (I closed ssh where I ran the script but the script kept going)
@FaheemMitha avoid messing with system python as much as possible. Consider using a virtualenv and pip install everything (or at least pip install --user)
@ilkkachu I tend to flag non-trivial chat stuff on main to be able to see flag progress
@AndrasDeak great. So the persistence of comments turns completely upside down when they're moved to chat. Turn from persistent until manually deleted into (might) get automatically deleted, but cannot be manually deleted. sheesh.
@AndrasDeak I didn't touch Python 3. Just upgraded some Python 3 libraries.
@AndrasDeak I didn't follow this.
@AndrasDeak Having multiple versions of a library has its own problems. Unless you are suggesting replacing some Debian binary packages with pip installed packages.
@FaheemMitha the "good" news is that you can have only one version of a package per python env. If you have an active virtualenv you'll take packages from there. If you have --user installed packages those should shadow your system python packages. My point was that it's usually suggested to keep the packages you as a user want to use separately from what the system uses.
Otherwise things might happen (for instance you upgrading a package that system python depends on, inadvertently breaking something)
so it's good practice to only non-root pip install (NEVER sudo pip install!) packages, and best practice to do this with virtualenvs
@FaheemMitha as for this, imagine this script_name.sh: for k in $(seq 21); do echo "iteration $k"; sleep 3; done
if I make this executable and run ./script_name.sh, I don't see an associated process in ps that I can kill, only the spawned sleep processes one by one. If I kill one the next iteration continues.
Whereas running bash script_name.sh will put a bash process with this exact name in ps which I can find and kill, stopping the loop
I mostly see RAM use building up when I browse imgur. Probably that infinite scrolling and lots of images even in comments. But that happens on a weekly time scale. I restart firefox when I'm running out of memory, but I only have to do that every few weeks.
@AndrasDeak Do you watch a lot of video? That's definitely part of the problem for me? I watch Amazon Prime Video and something called Hotstar, which is now owned by Disney.
Internal evidence suggests they both handle memory rather badly.
I thought it would be a nice idea if we could have a question thread where everyone posts an answer where they introduce themselves, talk about themselves a little bit, and tell the community their motivation for participating on this site.
Some SE sites don't have much of a community (in the se...
@AndrasDeak Ok, so not that long then. What did you use before Ubuntu?
This is clearly a reference to something, but nothing comes to mind.
First you need to know, whether they use their hair dryer inside a container. In that case you should furthermore ask whether that container is located on a ship being half of steel and half of a smiling whale. — famemanApr 22 '19 at 10:14
@FaheemMitha multiple reasons. The main ones are that I've learned to think that SO/MSO is not a social network and I'm instinctively extending that to SE, and that I don't actually spend time on unix.SE so I'm not really the target audience of your question.
I see that (surprisingly) you have no activity on U&L at all.
@AndrasDeak But this isn't a social network thing (whatever that means). It's about community. The original reason I wrote that question is so that regular site members could get to know each other a little better.
Presumably you've at least read the question.
@AndrasDeak I think you're right.
@AndrasDeak I started in 1998, as documented in my "getting to know you" answer.
But I bet most high-rep users have rough ideas about how OSes work, for instance. I know nothing.
I could answer some bash/regex questions, but I don't like bash or regex very much. They are useful tools for solving some problems but not entertaining for me.
I've seen many on-topic discussions here and they are all above my head
@AndrasDeak It's not really rocket science. I'm actually not particularly a Unix person (I have no particular fondness for classical Unix tools) but Unix is currently where the house where free software lives. Perhaps in part of historical reasons.
Once upon a time I regarded Unix as quite glamorous (in the 1990s, for example), but I've largely got over it.
@AndrasDeak Fair enough.
It's modestly useful to know something about the internals of our contemporary Linux-based systems, because they are quite powerful and flexible. And they're more useful if you understand what makes them tick. And they're also quite accessible. And free, of course.