Remind me again how this is Red Hats fault when Red Hat does not provide any MongoDB packages at all? If you want to run MongoDB on Red Hat you have to download a rpm from MongoDB:s third party repository so any unit or script included there is all done by MongoDB and not Red Hat.
Why do you anti systemd trolls keep lying when it's so easy to prove you wrong? All one have to do is look at the File List of the mongodb-server package in Ubuntu 16.04LTS: http://packages.ubuntu.com/xen... and what do we find there:
/lib/systemd/system/mongodb.service
Well I be damned, a systemd unit file, which you now have claimed in several articles does not exist even though it does. Interesting isn't it?
Please explain why the MongoDB binary built for trusty (Ubuntu 14.04LTS) which you choose to use in your example should contain a systemd unit file when systemd wasn't introduced until wily (Ubuntu 15.10)?
Sorry to rain on your parade but all database servers have this feature. PostgreSQL uses a master provess that restarts the backend processes if they crash. Microsoft SQL Server have a SQL Server Agent that does the very same thing and so on.
There are no bug reports where the "problem" with MySQL where fixed because there never where any bug reports that there where any problems in the first place. And this is because there is no problem with the MySQL unit file, and there never was, you just fell for a troll that have posted the same thread of posts to each Linux related article in the latest weeks.
Because System V init does not do process monitoring and service restart upon crash the MySQL people decided to write their own work around using shell scripts, this is why you can see a mysqld_safe process running as well as the regular mysqld on non systemd systems. mysqld_safe is a 1117 line bash script and/etc/init.d/mysql (the System V init script for MySQL) is a further 197 lines of bash:
Since this monitoring is done by a bash script it's not always 100% safe, I have on several occasions encountered situations where a "service mysql stop" returned with OK but that the mysqld_safe process refused to die, noticed that mysql where stopped and restarted it behind the scenes resulting in upgrades going to complete shit among other things.
Since all that shit is now instead handled properly by systemd due to i.e control groups the unit file for MySQL is extremely simply and straightforward:
# MySQL systemd service file
[Unit]
Description=MySQL Community Server
After=network.target
[Install]
WantedBy=multi-user.target
[Service]
User=mysql
Group=mysql
PermissionsStartOnly=true
ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
ExecStart=/usr/sbin/mysqld
ExecStartPost=/usr/share/mysql/mysql-systemd-start post
TimeoutSec=600
Restart=on-failure
RuntimeDirectory=mysqld
RuntimeDirectoryMode=755
No more mysqld_safe siliness and also everything down to a 20 line unit file that is a hell of a lot easier to parse manually than the old init scripts.
So I do hope that people will now see that the AC:s that keep posting these lies are in fact just lying trolls, not a single one of them have ever read the MySQL unit file and not a single one of them have ever run MySQL on a distribution using systemd.
One major disappointment is that the change Gnome did to xterm which fucked up tabs have now also been implemented in Gedit... First of all they spread the tabs over the entire width which makes it hard to actually see how many tabs you have opened but worse is that there is no real indicator for which tab is the active one. It might look prettier (not convinced there either) but productivity went out the window.
Well it was downmodded due to being an outright lie. There is no known problem with the MySQL unit file in Ubuntu 16.04 LTS, in fact it's very straight forward as compared with the horrible mess the System V init file for MySQL was.
The problem with this announcement is that Firefox where already available in the Ubuntu repositories practically at the same day that they released binaries for Windows and OS X. A long long time ago Firefox where frozen just like the rest of the software but since then you got the newest version even if you used 12.04LTS so this only means that Mozilla will now do what Ubuntu have been doing but with a snap instead of a.deb
Because with that amount of ifs there is no way that this could happen with System V init... Extra fun for example where one such old remote server where the OpenSSH script for some reason where run earlier than the "bring up the network with dhcp" script leading the OpenSSH script to just hang forever waiting for an ip address to show up that never would since dhcpcd where blocked due to the non parallel nature of System V init. For every horror story of systemd there are thousands for System V init.
Yeah the KEYDEFF stuff there is really hard core, however regarding your first issue you forgot to include the next line from man: "With no FILE, or when FILE is -, read standard input."
What? Patching/updating should never change the library version, if there is a patch/update for a library in Debian/Ubuntu it's backported to the version of the library that where installed to begin with. This should only be a problem when you move between versions of distributions, say from Ubuntu 15.10 to 16.04LTS. Either that or your experience comes from distributions who use rolling releases like Gentoo.
No, his problem is that he is a anti systemd troll that posts that to every Linux related story. Every one who have used MySQL on either Debian, Ubuntu, Red Hat and so on since they each switched to systemd knows that the unit files works just fine. Next up will surely be claims that it cannot log to the journal which also is very wrong (something that you most probably already know since you actually use this combination in contrast with the trolls who probably don't even know what Linux is).
svchost.exe has no counterpart in the Unix world. At some point in time, Microsoft decided to rewrite all their system services (init deamons) as dll:s instead of exe:s so they needed an exe that could load a dll and execute a specific set of functions in it and it became svchost.exe so ever system service written by Microsoft is seen as svchost.exe in Task Manager which for one thing made it into favourite nr 1 among malware/trojan writers.
Which is exactly what I said but you missed the big elephant in the room: When there is the next big security hole in say OpenSSL then you have to rebuild your Windows installer, distribute it and hope that all your customers install the new version, quite easy if we are only talking about one or two dependencies but some projects can draw in lots of dependencies and all of a sudden you have to play maintainer for all these dependencies.
Indeed and let's face it, if you where a terrorist would you ever be able to trust Telegram, Wire or other P2P solutions to 100%? The cost of being caught as a terrorist is quite high (life time in Guantanamo or killed by a drone) so the benefit of the solution (being able to communicate with your group) is simply not worth it.
I think more to the point is that 0 people have died in the US due to terrorists who where aided by encryption. No terrorists will ever use encryption because the benefit (easier communication) does not outweigh the cost (being arrested/killed before performing the act). If you are a terrorist or member of organized crime then you can never ever be 100% sure that NSA, FBI et al cannot spy on everything that you do and in that line of work you do need to be 100% sure.
For example here in Sweden the major organized crime faction is the bikers (Hells Angels and Bandidos) and they control big parts of drug distribution, prostitution and so on. We have learned from under cover cops that both of these groups have never ever trusted cell phones or the Internet, if they want to communicate they send a guy on a bike to deliver the message in person and cell phones are not even allowed to be brought in to meeting halls.
Of course but that is not Ubuntu specific which was my point, XFree86 to Xorg transition happened on all distributions. Myself I was burned several times with Gentoo when GCC changed their ABI in the 3.x series (or if it was in the 2.x series, don't really remember).
I agree wholeheartedly. As a developer, Linux distributions are a god send, you simply build debs and rpms for your application and send out to customers. With something like Windows (which mimics the approach that we see here kind of) you now have to keep track of each and every library that you use, and make sure that you fetch, compile and distribute to all your clients when there is a security hole in either one of them.
Well each to their own I suppose, myself I have upgraded numerous servers and desktops all the way from 8.04 to 14.04LTS (and 15.10 for the desktops) without any problems what so ever. Not claiming that you didn't experience problems, just that it's not universal. I bet that you can find installs where Debian could not be upgraded without problems or any other distribution for that matter.
Actually it does, even the package to 15.10 (Wiley) have a SysV script, an upstart script and a systemd unit file. And looking at the installed unit file it does not disable stderr so either GP is full of shit or it's mongodb itself that does not output to stderr.
I have a hard time believing that the CEO of Alphabet forced the CEO of Google to force the CEO of Nest to screw it's customer just so that they could be evil. Rather this is was a decision done by Nest itself. By ownership, Alphabet of course is the liable part but Nest is just some small subsidiary and Alphabet have tons of those so they are hardly micro managed by the owning company.
Slashdot Mirror
Remind me again how this is Red Hats fault when Red Hat does not provide any MongoDB packages at all? If you want to run MongoDB on Red Hat you have to download a rpm from MongoDB:s third party repository so any unit or script included there is all done by MongoDB and not Red Hat.
Why do you anti systemd trolls keep lying when it's so easy to prove you wrong? All one have to do is look at the File List of the mongodb-server package in Ubuntu 16.04LTS: http://packages.ubuntu.com/xen... and what do we find there:
/lib/systemd/system/mongodb.service
Well I be damned, a systemd unit file, which you now have claimed in several articles does not exist even though it does. Interesting isn't it?
Please explain why the MongoDB binary built for trusty (Ubuntu 14.04LTS) which you choose to use in your example should contain a systemd unit file when systemd wasn't introduced until wily (Ubuntu 15.10)?
Sorry to rain on your parade but all database servers have this feature. PostgreSQL uses a master provess that restarts the backend processes if they crash. Microsoft SQL Server have a SQL Server Agent that does the very same thing and so on.
There are no bug reports where the "problem" with MySQL where fixed because there never where any bug reports that there where any problems in the first place. And this is because there is no problem with the MySQL unit file, and there never was, you just fell for a troll that have posted the same thread of posts to each Linux related article in the latest weeks.
Because System V init does not do process monitoring and service restart upon crash the MySQL people decided to write their own work around using shell scripts, this is why you can see a mysqld_safe process running as well as the regular mysqld on non systemd systems. mysqld_safe is a 1117 line bash script and /etc/init.d/mysql (the System V init script for MySQL) is a further 197 lines of bash:
root@sql:~# wc /usr/bin/mysqld_safe /usr/bin/mysqld_safe /etc/init.d/mysql /etc/init.d/mysql
1117 4059 31801
root@sql:~# wc
197 777 5742
Since this monitoring is done by a bash script it's not always 100% safe, I have on several occasions encountered situations where a "service mysql stop" returned with OK but that the mysqld_safe process refused to die, noticed that mysql where stopped and restarted it behind the scenes resulting in upgrades going to complete shit among other things.
Since all that shit is now instead handled properly by systemd due to i.e control groups the unit file for MySQL is extremely simply and straightforward:
# MySQL systemd service file
[Unit]
Description=MySQL Community Server
After=network.target
[Install]
WantedBy=multi-user.target
[Service]
User=mysql
Group=mysql
PermissionsStartOnly=true
ExecStartPre=/usr/share/mysql/mysql-systemd-start pre
ExecStart=/usr/sbin/mysqld
ExecStartPost=/usr/share/mysql/mysql-systemd-start post
TimeoutSec=600
Restart=on-failure
RuntimeDirectory=mysqld
RuntimeDirectoryMode=755
No more mysqld_safe siliness and also everything down to a 20 line unit file that is a hell of a lot easier to parse manually than the old init scripts.
So I do hope that people will now see that the AC:s that keep posting these lies are in fact just lying trolls, not a single one of them have ever read the MySQL unit file and not a single one of them have ever run MySQL on a distribution using systemd.
One major disappointment is that the change Gnome did to xterm which fucked up tabs have now also been implemented in Gedit... First of all they spread the tabs over the entire width which makes it hard to actually see how many tabs you have opened but worse is that there is no real indicator for which tab is the active one. It might look prettier (not convinced there either) but productivity went out the window.
Well it was downmodded due to being an outright lie. There is no known problem with the MySQL unit file in Ubuntu 16.04 LTS, in fact it's very straight forward as compared with the horrible mess the System V init file for MySQL was.
The problem with this announcement is that Firefox where already available in the Ubuntu repositories practically at the same day that they released binaries for Windows and OS X. A long long time ago Firefox where frozen just like the rest of the software but since then you got the newest version even if you used 12.04LTS so this only means that Mozilla will now do what Ubuntu have been doing but with a snap instead of a .deb
If you decide to bring dependency hell upon yourself then there is nothing any one else can do to help you but yourself.
Because with that amount of ifs there is no way that this could happen with System V init... Extra fun for example where one such old remote server where the OpenSSH script for some reason where run earlier than the "bring up the network with dhcp" script leading the OpenSSH script to just hang forever waiting for an ip address to show up that never would since dhcpcd where blocked due to the non parallel nature of System V init. For every horror story of systemd there are thousands for System V init.
Yeah the KEYDEFF stuff there is really hard core, however regarding your first issue you forgot to include the next line from man: "With no FILE, or when FILE is -, read standard input."
What? Patching/updating should never change the library version, if there is a patch/update for a library in Debian/Ubuntu it's backported to the version of the library that where installed to begin with. This should only be a problem when you move between versions of distributions, say from Ubuntu 15.10 to 16.04LTS. Either that or your experience comes from distributions who use rolling releases like Gentoo.
No, his problem is that he is a anti systemd troll that posts that to every Linux related story. Every one who have used MySQL on either Debian, Ubuntu, Red Hat and so on since they each switched to systemd knows that the unit files works just fine. Next up will surely be claims that it cannot log to the journal which also is very wrong (something that you most probably already know since you actually use this combination in contrast with the trolls who probably don't even know what Linux is).
svchost.exe has no counterpart in the Unix world. At some point in time, Microsoft decided to rewrite all their system services (init deamons) as dll:s instead of exe:s so they needed an exe that could load a dll and execute a specific set of functions in it and it became svchost.exe so ever system service written by Microsoft is seen as svchost.exe in Task Manager which for one thing made it into favourite nr 1 among malware/trojan writers.
Which is exactly what I said but you missed the big elephant in the room: When there is the next big security hole in say OpenSSL then you have to rebuild your Windows installer, distribute it and hope that all your customers install the new version, quite easy if we are only talking about one or two dependencies but some projects can draw in lots of dependencies and all of a sudden you have to play maintainer for all these dependencies.
Indeed and let's face it, if you where a terrorist would you ever be able to trust Telegram, Wire or other P2P solutions to 100%? The cost of being caught as a terrorist is quite high (life time in Guantanamo or killed by a drone) so the benefit of the solution (being able to communicate with your group) is simply not worth it.
I think more to the point is that 0 people have died in the US due to terrorists who where aided by encryption. No terrorists will ever use encryption because the benefit (easier communication) does not outweigh the cost (being arrested/killed before performing the act). If you are a terrorist or member of organized crime then you can never ever be 100% sure that NSA, FBI et al cannot spy on everything that you do and in that line of work you do need to be 100% sure.
For example here in Sweden the major organized crime faction is the bikers (Hells Angels and Bandidos) and they control big parts of drug distribution, prostitution and so on. We have learned from under cover cops that both of these groups have never ever trusted cell phones or the Internet, if they want to communicate they send a guy on a bike to deliver the message in person and cell phones are not even allowed to be brought in to meeting halls.
Of course but that is not Ubuntu specific which was my point, XFree86 to Xorg transition happened on all distributions. Myself I was burned several times with Gentoo when GCC changed their ABI in the 3.x series (or if it was in the 2.x series, don't really remember).
So you don't know that svchost.exe or systemd does but still made a post.
I agree wholeheartedly. As a developer, Linux distributions are a god send, you simply build debs and rpms for your application and send out to customers. With something like Windows (which mimics the approach that we see here kind of) you now have to keep track of each and every library that you use, and make sure that you fetch, compile and distribute to all your clients when there is a security hole in either one of them.
Well each to their own I suppose, myself I have upgraded numerous servers and desktops all the way from 8.04 to 14.04LTS (and 15.10 for the desktops) without any problems what so ever. Not claiming that you didn't experience problems, just that it's not universal. I bet that you can find installs where Debian could not be upgraded without problems or any other distribution for that matter.
He really smelled that bad huh?
Actually it does, even the package to 15.10 (Wiley) have a SysV script, an upstart script and a systemd unit file. And looking at the installed unit file it does not disable stderr so either GP is full of shit or it's mongodb itself that does not output to stderr.
This is the included unit file on Wiley:
[Unit]
/etc/mongodb.conf
Description=An object/document-oriented database
Documentation=man:mongod(1)
[Service]
User=mongodb
ExecStart=/usr/bin/mongod --config
[Install]
WantedBy=multi-user.target
I have a hard time believing that the CEO of Alphabet forced the CEO of Google to force the CEO of Nest to screw it's customer just so that they could be evil. Rather this is was a decision done by Nest itself. By ownership, Alphabet of course is the liable part but Nest is just some small subsidiary and Alphabet have tons of those so they are hardly micro managed by the owning company.