Originally Posted by
rupesh3
Any operating system like windows Fedora Debian Arch Linux etc., shutdown immediately when we press shutdown button present in the cabinet.
This is not happening in the current Ubuntu Linux. It is asking for confirmation.
So, there's no way for a shutdown to be clean is it happens immediately. I can only guess those other systems are really doing the equivalent of "shutdown -h now", which isn't a clean shutdown. At best, it might sync the files and close the file systems. It certainly isn't cleanly shutting down the hundreds of little processes that Ubuntu desktop's run. Have you timed "immediately"? If it is under 10 seconds, I have doubts. The amount of processes and the number and types of added hardware (internal and external) will lengthen the time required.
BTW, I have a similar system.
Code:
$ inxi -bz
System: Kernel: 5.15.0-119-generic x86_64 bits: 64 Desktop: FVWM2 2.6.8 Distro: Ubuntu 20.04.6 LTS (Focal Fossa)
Machine: Type: Desktop Mobo: ASUSTeK model: ROG STRIX B450-F GAMING v: Rev 1.xx serial: <filter>
UEFI: American Megatrends v: 5003 date: 02/03/2023
CPU: 6-Core: AMD Ryzen 5 5600G with Radeon Graphics type: MT MCP speed: 4200 MHz min/max: 1400/4200 MHz
Graphics: Device-1: Advanced Micro Devices [AMD/ATI] driver: amdgpu v: kernel
Display: server: X.Org 1.20.13 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa
resolution: 1920x1200~60Hz
OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.15.0-119-generic LLVM 12.0.0) v: 4.6 Mesa 21.2.6
Network: Device-1: Intel I211 Gigabit Network driver: igb
Drives: Local Storage: total: 19.10 TiB used: 3.36 TiB (17.6%)
Info: Processes: 444 Uptime: 12d 23h 01m Memory: 30.71 GiB used: 7.63 GiB (24.8%) Shell: bash inxi: 3.0.38
# Not using lots of RAM currently,
$ free -hm
total used free shared buff/cache available
Mem: 30Gi 6.7Gi 7.7Gi 71Mi 16Gi 23Gi
Swap: 4.1Gi 1.3Gi 2.8Gi
But a very busy computer right now for a 6-CPU system:
$ uptime
10:51:46 up 12 days, 23:02, 4 users, load average: 13.69, 14.49, 14.46
As you can see, I have lots of connected storage. It is all internal, using SATA connections on the motherboard. No USB involved at all.
Anyway, it needs to be rebooted (I've put that off since Saturday), so I'll do that when some long-running processes can be cleanly cancelled in the next hour and post the time to shutdown. Can't do it now, or I'll lose to much of the work that's already been done. Looks like 38 minutes will be a good time to shutdown.
I hope I'm wrong for how long it takes to shutdown. Most people worry about startup times, not shutdown. We are always seeing startup times.
Code:
$ systemd-analyze
Startup finished in 13.524s (firmware) + 2.459s (loader) + 6.349s (kernel) + 14.855s (userspace) = 37.189s
graphical.target reached after 14.513s in userspace
Before you ask, on the same system, it is about 40 seconds. Most of that is related to periodic fscks on 16 different file systems it uses. I force an fsck every 30 days - well, the boot after 30 days, so it isn't exactly 30 days. I tend to reboot about every 2-4 weeks, depending on the patches applied.
Bookmarks