Language Selection

English French German Italian Portuguese Spanish

Site news - keepin' ya posted

Filed under
Site News

If you've noticed the lack of reviews and slower than usual performance of tuxmachines, there is a good reason. I'm working on an off-site hosting vps in hopes of moving tuxmachines to a faster server and/or larger pipe.

Not that I've entirely neglected my reviewing interests, as Sunday I did test 3 distros. I afraid I didn't have much luck. Two of them were from Distrowatch's waiting list and didn't complete the boot (or into gui) process and the other was DSL 2.4.

DSL 2.4 was released and I wanted to write an article on it, except after booting I found all improvements were under the hood. I just couldn't get a full length article out of it. So, I ended up scraping that idea.

But back to the new server. I've rented a vps from tektonic and started with a debian 3.1 install. It was a fairly easy dist-upgrade to etch and moving my site was a no-brainer as well.

I had tried a vps out of Europe last month, I forget the name right now, but ssh response time was agonizing slow and whenever I tried to import drupal's database - mysql would disconnect. They didn't answer my email about it, so I'm test driving tektonic right now.

So far tektonic seems fine except it's slow for me. I've had a few friends from around the world test it and I am getting some positive feedback. So hopefully, it'll just be slow for me. Big Grin

I've been uploading my site which consists of about 1.5 gigs of data. This has been eating up some of my already limited bandwidth making tuxmachines even slower than normal. But hopefully most of the uploading will be finished in a few hours and I will only need to get a newer snapshot of the database when the time comes for further testing.

I will be soliciting testers and opinions in a few days on the speed of the new site. We might experience a bit of bumpy road if we decide to move there permanently with dns and such, but hopefully it will end up providing a more pleasant experience for my regulars and be able to handle more traffic if needed.

Thanks.

Oh, ps.: A monthly printed Linux publication asked for permission to re-print my SUSE article in their magazine with a link to the site, so hopefully that'll bring in some new visitors as well. I hope we complete the move before it's published! Big Grin

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Questions on bandwidth, operating system and tectonic hardwa

atang1 wrote:

It seems about the same speed when guests approach 150 on any bandwidth? Guests around 60 is plenty fast.

Well, I'd hoped a bigger pipe wouldn't bog down as soon as mine seems to when a story hits the "big" sites. I don't know how it's gonna work out, nor do I know the norm. This will be my first attempt at using a hosting service. There are fast drupal sites out there - it must be possible. Big Grin

atang1 wrote:

Is the operating system finetuned to their server cpu(platform)?

Naw, I don't think so. Like I said, our started out a Debian 3.1. It's built for like 386s ain't it?

I'm not a big Debian expert, but my other choices were centos, fedora 4, or suse 10.0. I figured debian to be my best bet for server. I love Gentoo, but it's inconvenient for a server.

Re: Tectonic people must be able to advise you ?

atang1 wrote:

I noticed you do not yet have a batch processing cron job established between the two repositories. I think you only have to have minutes delay until it gets really busy to have within seconds any accuracy?

This experience may give us some idea if it is indeed bandwidth or operating system slow down?

Well, if you mean rsync'in between them, then nope. I looked into it and html files would be easy enough. a php database is another subject altogether. I first toyed with the idea of "load balancing" between the two, but there is no good way I've found to updated one database from the other. Unless you know of a good way?

I mean I could have one use the database of the other, but I think that would slow things down more than it'd help. WDYT?

More in Tux Machines

Leftovers: OSS

Security Leftovers

  • Security updates for Thursday
  • OpenSSL patches two high-severity flaws
    OpenSSL has released versions 1.0.2h and 1.0.1t of its open source cryptographic library, fixing multiple security vulnerabilities that can lead to traffic being decrypted, denial-of-service attacks, and arbitrary code execution. One of the high-severity vulnerabilities is actually a hybrid of two low-risk bugs and can cause OpenSSL to crash.
  • Linux Foundation Advances Security Efforts via Badging Program
    The Linux Foundation Core Infrastructure Initiative's badging program matures, as the first projects to achieve security badges are announced.
  • Linux Foundation tackles open source security with new badge program
  • WordPress Plugin ‘Ninja Forms’ Security Vulnerability
    FOSS Force has just learned from Wordfence, a security company that focuses on the open source WordPress content management platform, that a popular plugin used by over 500,000 sites, Ninja Forms, contains serious security vulnerabilities.
  • Preparing Your Network for the IoT Revolution
    While there is no denying that IP-based connectivity continues to become more and more pervasive, this is not a fundamentally new thing. What is new is the target audience is changing and connectivity is becoming much more personal. It’s no longer limited to high end technology consumers (watches and drones) but rather, it is showing up in nearly everything from children’s toys to kitchen appliances (yes again) and media devices. The purchasers of these new technology-enabled products are far from security experts, or even security aware. Their primary purchasing requirements are ease of use.
  • regarding embargoes
    Yesterday I jumped the gun committing some patches to LibreSSL. We receive advance copies of the advisory and patches so that when the new OpenSSL ships, we’re ready to ship as well. Between the time we receive advance notice and the public release, we’re supposed to keep this information confidential. This is the embargo. During the embargo time we get patches lined up and a source tree for each cvs branch in a precommit state. Then we wait with our fingers on the trigger. What happened yesterday was I woke up to a couple OpenBSD developers talking about the EBCDIC CVE. Oh, it’s public already? Check the OpenSSL git repo and sure enough, there are a bunch of commits for embargoed issues. Pull the trigger! Pull the trigger! Launch the missiles! Alas, we didn’t look closely enough at the exact issues fixed and had missed the fact that only low severity issues had been made public. The high severity issues were still secret. We were too hasty.
  • Medical Equipment Crashes During Heart Procedure Because of Antivirus Scan [Ed: Windows]
    A critical medical equipment crashed during a heart procedure due to a timely scan triggered by the antivirus software installed on the PC to which the said device was sending data for logging and monitoring.
  • Hotel sector faces cybercrime surge as data breaches start to bite
    Since 2014, things have become a lot more serious with a cross section of mostly US hotels suffering major breaches during Point-of-Sale (POS) terminals. Panda Security lists a string of attacks on big brands including on Trump Hotels, Hilton Worldwide, Hyatt, Starwood, Rosen Hotels & Resorts as well two separate attacks on hotel management outfit White Lodging and another on non-US hotel Mandarin Oriental.

Android Leftovers

today's howtos