3 ms·
Unless you are linking statically (and I don't really understand why you would) you update glibc and that's it. This question had me feeling kind of old. Does
by asveikau 11y ago
Unless you are linking statically (and I don't really understand why you would) you update glibc and that's it.
This question had me feeling kind of old. Does nobody learn what shared libraries are anymore?
- mentat 11y agoThat isn't it, see siblings here. You have to restart all processes that load glibc and interact with the affected services.
- w8rbt 11y agoDebian does this automatically and alerts the user what services are being restarted.
- muppetman 11y agoI updated this morning and nothing got restarted. Shouldn't pretty much every network service I have gotten a restart? sshd, postfix, apache, icecast2, dovecot None of them restarted. So I restarted them all myself...
- drummer32 11y agoIt doesnt't. There's the needsrestart package that does this though.
- cdelsolar 11y agoGo?
- rspeer 11y agoWell, now, a lot of people are making containers, which are static linking turned up to 11. I bet this bug will live on forever in people's Docker stacks.
- yxhuvud 11y agoDoes libc even support static linking?
- steveklabnik 11y agoglibc is generally not statically linked. MUSL libc generaly is. You _can_ statically link glibc, but then you lose some stuff. https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked_programs_need_some_shared_libraries_which_is_not_acceptable_for_me.__What_can_I_do.3F https://sourceware.org/glibc/wiki/FAQ#Even_statically_linked...
- strictfp 11y agoNope, the pendulum is at it's other extreme. Go is going all in on static builds, docker containers freeze ALL THE THINGS \@/ and "immutable" package managers like Nix which in effect is like static linking without the speed benefits.
- strictfp 11y agoNope, the pendulum is at it's other extreme. Go is going all in on static builds, docker containers freeze ALL THE THINGS \@/ and "immutable" package managers like Nix which in effect is like static linking without the speed benefits.
- peterwwillis 11y agoThe past four years of modern development practices have run screaming from the concept. Learning why the systems used to work they way they did was, like, super hard, so they reinvented the wheel and are running into the same problems that caused us to make shared libraries/COW/etc in the first place.
- XorNot 11y agoYou've pretty fundamentally misunderstood them if you think immutable practices in anyway damage the ability to deploy fixes. Years of shared library hell is what causes things like this to go unfixed.
- peterwwillis 11y agoImmutability in software development & deployment is, for the vast majority of use cases, completely unnecessary. The only reason people talk about it now is everyone has a fetish over using simple software rather than designing software that works well. And 'immutable practices' don't damage anything - they simply make things take longer, duplicate effort, make inefficient use of resources, and make everything generally more inflexible. The only benefit seems to be high level abstraction at the cost of everything else.