NoShell | C++ library to easily start subprocesses and pipelines | Runtime Evironment library

The primary difference between htop and ps aux is that htop shows each individual thread belonging to a process rather than the process only - this is similar to ps auxm. Using the htop interactive command H, you can hide threads to get to a list that more closely corresponds to ps aux.

In terms of memory usage, those additional entries representing individual threads do not affect the actual memory usage total because threads share the address space of the associated process.

RSS (resident set size) in general is problematic because it does not adequately represent shared pages (due to shared memory or copy-on-write) for your purpose - the sum can be higher than expected in those cases. You can use smem -t to get a better picture with the PSS (proportional set size) column. Based on the facts you provided, that is not your issue, though.

In your case, it might make sense to dig deeper via smem -tw to get a memory usage breakdown that includes (non-cache) kernel resources. /proc/meminfo provides further details.

The process that runs the -s exits with normal when it has no more code to execute. The supervisor receives that signal and since it's from its parent, it exits (regardless of it being normal), as explained in gen_server:terminate/2 (supervisors are gen_servers with trap_exit active):

Even if the gen_server process is not part of a supervision tree, this function is called if it receives an 'EXIT' message from its parent. Reason is the same as in the 'EXIT' message.

I haven't tested your code, but if you add a process_flag(trap_exit, true) to your gen_server, you'll surely replicate this behaviour.

I had Erlang 23 and RabbitMQ Server 3.8.2 (they are not fully compatible so I decided to upgrade RabbitMQ Server to 3.8.9 because I had some problems running my app)

I have a cluster with one node on AWS EC2 instance of Ubuntu 20.04 (unconfigured yet properly as RabbitMQ advises via plugin - I plan to do it later).

What I did and it worked for me (following commands executed under sudo or root sudo su):

1. It's important to shutdown not just stop_app as Erlang also needs to be stopped and stop_app only stops RabbitMQ Server leaving Erlang on which would later might give you error while starting new version of the RabbitMQ Server - for port 25672 being busy with another app:

   rabbitmqctl shutdown

2. Change in rabbitmq file from old version (I had for some strange reason 3.8.8 instead of 3.8.2 which I run) to a new one - in my case 3.8.9:

   vim /etc/apt/preferences.d/rabbitmq

3. Recheck if dependencies are installed:

   apt-get -y install socat logrotate init-system-helpers adduser

4. Install wget if you don't have it:

   apt-get -y install wget

5. Download latest .deb package of server installation file:

   wget https://github.com/rabbitmq/rabbitmq-server/releases/download/v3.8.9/rabbitmq-server_3.8.9-1_all.deb

6. Install it:

   dpkg -i rabbitmq-server_3.8.9-1_all.deb

7. Remove distro:

   rm rabbitmq-server_3.8.9-1_all.deb

8. Check if server stopped (may be redundant command):

   service rabbitmq-server stop

9. Restart server:

   service rabbitmq-server restart

10. Check server status:

    rabbitmq-server status

11. If it gives you an error BOOT FAILED. Distribution port 25672 is in use by another node, check who uses that port it may be that Erlang uses that port:

    lsof -i :25672

12. Start RabbitMQ app:

    rabbitmqctl start_app

13. Check status of node:

    rabbitmqctl status

You should see upgraded RabbitMQ Server version (in my case 3.8.9) along with you recent Erlang version (in my case 23)

For some reason, the C compiler ends up not understanding code following the C99 standard; in particular it doesn't permit variable declarations after the first statement in a function.

Since bcrypt_elixir has a Makefile.win file, suggesting that it has compiled successfully on Windows before, I don't quite understand why this is happening, but in any case you should be able to fix this by modifying bcrypt_nif.c, changing this:

Your do_merge returns ok always (the base recursion case).

Here you have two solutions, the first one is more readable, but I'd go with the second one

From the docs:

-s Mod [Func [Arg1, Arg2, ...]](init flag)
Makes init call the specified function. Func defaults to start. If no arguments are provided, the function is assumed to be of arity 0. Otherwise it is assumed to be of arity 1, taking the list [Arg1,Arg2,...] as argument. All arguments are passed as atoms. See init(3).

1. Because of this line:

   If no arguments are provided, the function is assumed to be of arity 0. Otherwise it is assumed to be of arity 1, taking the list [Arg1,Arg2,...] as argument.

   your function is going to receive a list as the sole argument.

2. Because of this line:

   All arguments are passed as atoms.

   all the arguments in the list are going to be atoms.

Therefore, you need to pick out the head of the list to get the sole argument, and then you have to convert the atom to an integer in order to use the == comparison with another integer. Like this: