| Git Clone URL: | https://aur.archlinux.org/mongodb-bin.git (read-only, click to copy) |
|---|---|
| Package Base: | mongodb-bin |
| Description: | A high-performance, open source, schema-free document-oriented database |
| Upstream URL: | https://www.mongodb.com/ |
| Keywords: | database document-oriented mongo mongod mongodb mongos |
| Licenses: | SSPL-1.0 |
| Conflicts: | mongodb, mongodb-shell-bin |
| Provides: | mongodb |
| Submitter: | ali.molaei |
| Maintainer: | ali.molaei (rafaelff) |
| Last Packager: | ali.molaei |
| Votes: | 91 |
| Popularity: | 2.45 |
| First Submitted: | 2019-01-28 09:01 (UTC) |
| Last Updated: | 2024-04-29 09:14 (UTC) |
My main reason for not using /run is that it's strictly forbidden for packages, according to https://wiki.archlinux.org/title/Arch_package_guidelines. Asked a Arch Developer the reason for this rule, and he told me "retro-compatibility" because "other distros use pacman as well".
Besides, It seems the downloaded tarball has already /var/run set so I might remove this sed line.
Actually, /var/run is the legacy path as I understand it. The motivation behind introducing /run was to be able to mount it early before /var is available. The commit you point to says:
"Optionally rewrites lines referencing /var/run/, to use /run/ instead."
/var/run is currently a symlink that resolves to /run on my system, and on other distros too as far as I know.
See also https://lwn.net/Articles/436012/
@snale systemd considers /run a legacy tmpfile path and recomends /var/run. See warning implemented for systemd 239 in https://github.com/systemd/systemd/commit/a2d1fb882c4308bc10362d971f333c5031d60069
Hey, I was wondering, wouldn't it be better to use /run instead of /var for the systemd service PID file? /var/run is a tmpfs originally too whereas /var is not, I think.
Updated to 6.0.0. Those willing to stick with 5.x versions, check mongodb50-bin
@flying-sheep can you provide it?
Hi, I don’t want mongodb to start until I need it. Is it possible to add a mongodb.socket file for systemd?
@iib: That's the option made by MongoDB, and there's nothing the package maintainers can do about it. You could use mongodb44-bin, which aims to provide the latest release from 4.4.x series.
I am getting core dump, my processor is celeron n4100. Avx and f16c are not supported for me, and now I can not use the program? This is just a mockery because my cpu is not that old!
anyone else get a fun
mongo: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory
error?
Pinned Comments
ali.molaei commented on 2021-07-28 14:29 (UTC)
If you get core dumps on version 5, read this: https://jira.mongodb.org/browse/SERVER-58648