LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-22-2019, 06:08 AM   #1
Barx
Member
 
Registered: Jun 2004
Location: Italy
Distribution: Slack x64 current
Posts: 141

Rep: Reputation: 26
Cool great uptime on my Slackware server - THANK YOU ALL!


Hi all

I'm proud to share this uptime achieved on the Slackware that I'm using in my office.

I take advantage of this post to thank Patrick and the entire Slackware staff to the great job they are doing, maintaining this ROCK SOLID Linux distro

Anyway, I have to emphasize the fact that the server was absolutely NOT created to reach record uptimes. This is a small server in my (smallest) office, built with desktop hardware; in fact, it's a normal desktop PC used as a server.

The uptime is due first of all to the fact that I never had long blackouts (and that the UPS worked good in the small blackouts I've got), than to the good luck with the hardware chosen, and of course to the great stability of Slackware!

None of my friends and colleagues uses Slackware on their servers, and none of them reaches uptimes greater then some hundreds days :-)

So, I'm happy to thank you all one more time

Kind regards

Alessandro Barisone
Attached Thumbnails
Click image for larger version

Name:	2006.png
Views:	293
Size:	91.9 KB
ID:	30935  
 
Old 07-22-2019, 06:27 AM   #2
dc.901
Member
 
Registered: Aug 2018
Location: Atlanta, GA - USA
Distribution: CentOS/RHEL, openSuSE/SLES, Ubuntu
Posts: 896

Rep: Reputation: 296Reputation: 296Reputation: 296
Wow! I think closest I had was about 900 days.
I'm curious, in over 5-years, no updates that required a reboot?
 
Old 07-22-2019, 06:31 AM   #3
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Ubuntu, Debian, Slackware
Posts: 2,142
Blog Entries: 6

Rep: Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412
Beats my current uptime of 1 and a half days...

But OP, congratulations. That's a seriously impressive uptime. What version of Slackware is that?

[If anyone's interested in the maths, OP's uptime is exactly five and a half years and the server was last turned on/rebooted around 22nd January 2014].

EDIT: version has to be 14.0 looking at the kernel.

Last edited by Lysander666; 07-22-2019 at 10:22 AM.
 
1 members found this post helpful.
Old 07-22-2019, 08:01 AM   #4
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,872

Rep: Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425
Don't you ever upgrade the kernel?
 
Old 07-22-2019, 08:54 AM   #5
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,582

Rep: Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158
Methinks you skate on thin ice with ssh enabled for login by root with a password and the 3.2.45 kernel.
 
2 members found this post helpful.
Old 07-22-2019, 08:57 AM   #6
ehartman
Senior Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 1,674

Rep: Reputation: 885Reputation: 885Reputation: 885Reputation: 885Reputation: 885Reputation: 885Reputation: 885
Quote:
Originally Posted by Lysander666 View Post
Beats my current uptime of 1 and a half days...
And mine, of 27 days (we had a power failure about a month ago during which the internet was down for several hours).
 
Old 07-22-2019, 09:21 AM   #7
hitest
Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, Debian, OpenBSD
Posts: 6,583

Rep: Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805
One day of uptime here. There was a new kernel in -current yesterday.

Code:
bash-5.0$ uname -rpm
4.19.60 x86_64 Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
That's impressive uptime! However, I share the concern that others have mentioned. A server should be patched with security updates in my opinion.

Code:
Mon Jul 22 03:05:48 UTC 2019
patches/packages/linux-4.4.182/*:  Upgraded.
  These updates fix various bugs and many minor security issues.
  Be sure to upgrade your initrd after upgrading the kernel packages.
  If you use lilo to boot your machine, be sure lilo.conf points to the correct
  kernel and initrd and run lilo as root to update the bootloader.
  If you use elilo to boot your machine, you should run eliloconfig to copy the
  kernel and initrd to the EFI System Partition.
  For more information, see:
    Fixed in 4.4.183:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11599
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3892
    Fixed in 4.4.185:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13272
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16597
    Fixed in 4.4.186:
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10126
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3846
  (* Security fix *)
+--------------------------+

Last edited by hitest; 07-22-2019 at 09:26 AM. Reason: Addition- security update for 14.2
 
Old 07-22-2019, 10:16 AM   #8
cwizardone
LQ Veteran
 
Registered: Feb 2007
Distribution: Slackware64-current with "True Multilib."
Posts: 6,469
Blog Entries: 1

Rep: Reputation: 3809Reputation: 3809Reputation: 3809Reputation: 3809Reputation: 3809Reputation: 3809Reputation: 3809Reputation: 3809Reputation: 3809Reputation: 3809Reputation: 3809
Barx,
Impressive. Very impressive!

Last edited by cwizardone; 07-22-2019 at 11:20 AM.
 
Old 07-22-2019, 10:26 AM   #9
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Ubuntu, Debian, Slackware
Posts: 2,142
Blog Entries: 6

Rep: Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412
Quote:
Originally Posted by allend View Post
Methinks you skate on thin ice with ssh enabled for login by root with a password and the 3.2.45 kernel.
14.0 is not EOL but the 3.2.x kernel is. I don't understand how that works.
 
Old 07-22-2019, 10:29 AM   #10
hitest
Guru
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, Debian, OpenBSD
Posts: 6,583

Rep: Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805Reputation: 2805
Quote:
Originally Posted by Lysander666 View Post
14.0 is not EOL but the 3.2.x kernel is. I don't understand how that works.
That means that the 3.2x kernel will not receive patches for known or new security vulnerabilities. Not a good situation for a server.
 
Old 07-22-2019, 10:42 AM   #11
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Ubuntu, Debian, Slackware
Posts: 2,142
Blog Entries: 6

Rep: Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412
Quote:
Originally Posted by hitest View Post
That means that the 3.2x kernel will not receive patches for known or new security vulnerabilities. Not a good situation for a server.
Indeed, but in that case why would 14.0 continue to receive updates?
 
Old 07-22-2019, 10:51 AM   #12
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,872

Rep: Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425Reputation: 1425
Quote:
Originally Posted by Lysander666 View Post
Indeed, but in that case why would 14.0 continue to receive updates?
Other software continues to be patched. The admin is responsible for upgrading the kernel or leaving it insecure.
 
Old 07-22-2019, 10:56 AM   #13
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Ubuntu, Debian, Slackware
Posts: 2,142
Blog Entries: 6

Rep: Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412Reputation: 2412
Quote:
Originally Posted by montagdude View Post
Other software continues to be patched. The admin is responsible for upgrading the kernel or leaving it insecure.
Ah I see, thank you.
 
Old 07-22-2019, 11:04 AM   #14
Barx
Member
 
Registered: Jun 2004
Location: Italy
Distribution: Slack x64 current
Posts: 141

Original Poster
Rep: Reputation: 26
I'm aware of what implies to keep using an old (unpatched) kernel, but after the first year of uptime the willing to beat the record won on the patches, so I moved security on the network perimeter. And I'm aware that this isn't an optimal solution.

The server is used internal on my network only for PHP develop and as file server; the SSH port is mapped on a non standard port, and ports opens on firewall only after a port knock; the server is not faced on the internet without successful knocking

The server runs Slackware 14.0 (the one available in January 2014), and was never rebooted (assembled, installed, booted first time, never rebooted)
 
8 members found this post helpful.
Old 07-22-2019, 11:12 AM   #15
dc.901
Member
 
Registered: Aug 2018
Location: Atlanta, GA - USA
Distribution: CentOS/RHEL, openSuSE/SLES, Ubuntu
Posts: 896

Rep: Reputation: 296Reputation: 296Reputation: 296
Quote:
Originally Posted by Barx View Post
The server runs Slackware 14.0 (the one available in January 2014), and was never rebooted (assembled, installed, booted first time, never rebooted)
Very Impressive!
 
  


Reply

Tags
record, uptime


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Thank you, thank you, thank you. Hatman KZN Linux - Newbie 5 04-02-2016 07:51 AM
init uptime longer than system uptime? m4rtin Linux - Server 1 09-15-2010 07:45 AM
Slackware 10 Developement Team - Thank You! Thank You! and Thank you! perry Slackware 5 07-21-2004 11:21 AM
Thank You Thank You Thank You ETC... Frank_Drebin LinuxQuestions.org Member Intro 7 02-24-2004 04:21 PM
Thank You Thank You Thank You Atrocity General 15 11-18-2002 04:11 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 12:36 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration