A web server is supposed to retrieve data from database, run application
logic, write back to database if needed, write an HTML document or JSON
object to output, and wait for the next request. Ideally, it's stateless
between requests.
A desktop application, on the other hand, is more likely to
@mdeslaur: Thank you for your reply! Does that mean that it is supposed
to happen on an Ubuntu server system?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/244250
Title:
@khaled-blah: yes, on a server, it should do the usual and add a reboot
required blurb to the motd.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/244250
Title:
Spurious
@mdeslaur: Again, thank you for your reply! Pardon my ignorance but I've
never quite understood why that is - why is an update of libssl
different from an update of other libs where you can simply restart the
depending applications/daemons? And why is it different on a desktop?
Maybe these
On Ubuntu 14.04 this bug still persists. Is there any reason why libssl
would require different treatment than other libraries? I.e. why
wouldn't it suffice to restart services depending on libssl or
libcrypto?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
@khaled-blah: please file a new bug, you are not supposed to see reboot
notifications when openssl gets upgraded on a desktop system.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
6 matches
Mail list logo
