2 more picked off:
6. Add update for postgrey_whitelist_clients
13. One-click push default gateway for OpenVPN

Mansoor wrote:

Adding a search/lookup box at the top of menu column to quickly find an entry without navigating the menu.

I was thinking we could have a favorites topbar, something we could choose the links we want to show, perhaps even custom external links

Adding a search/lookup box at the top of menu column to quickly find an entry without navigating the menu.

When integrating an external SMTP server (Relay Host), the SMTP Server app could be improved to allow entering all required settings directly in the UI instead of using postconf program or editing /etc/postfix/main.cf

Dave Loper wrote:

I've talked with Tyler and will coordinate with Shad to see if we can get a testing repo as a sort of mirror for the latest updates. That way we can simply push any patches from Kopano that don't break things. I need to get approval from Kopano to do this though because this isn't open source and I cannot simply distribute without their approval. I'll update you Tuesday or after once I have a few days to work through some of the contacting and logistics.

Dave,

I'll post my commands in the other thread, so this threads keeps a little bit clean

Hi,

I'm trying to setup a new install but can not install Kopano trough marketplace or ssh

Exception: Test Transaction Errors: file /usr/lib64/libxapian.so.22 conflicts between attempted installs of xapian-core-libs-1.2.22-1.el7.x86_64 and libxapian22-1.2.17-30.2.x86_64

Nick; be aware that the upgrade of Nextcloud to v16 requires the addition of a number of additional db indices. They can be installed via an occ command.
RE: the 4-byte utf-8 issue; it probably depends on what the original version of Nextcloud used in the (original) app is. The message shows up in the admin page of Nexcloud - it works without the table setting, but if the table doesn't have the capability, you just get a warning to say that emojis won't be supported - probably not important as is appears to be in the email part of Nextcloud, but I personally like to get rid of as many warning as possible. There's also a warning that a recommended php module (imagick) is missing, but I've not looked into that ATM.

@Patrick, thanks for the extra input. All your hand edits would have to be scripted somehow and the database updated automatically. From the message about the database it looks pretty trivial to script that - just add the command to a postinstall script in app-kopano. Have you tried running the `kopano-dbadm usmp` command?

@Eric, there is an update prepared for nextcloud to v15 which I have used and helped Tyler prepare and it does not indicate this error message. How did you do you upgrade? Unfortunately they have just released 16.... Did you manually do yours from 13? What we did is patch their upgrade script to allow an upgrade directly from 13 > 15. I have installed this upgrade and I don't see the "4-byte utf-8" issue. Where are you seeing it? The upgrade is sitting in contribs-testing at the moment but there is an issue stopping us from releasing. The issue is that, once updated, the first person to log into Nextcloud will be greeted with the upgrade message and have to kick it off. This could be anyone in the organisation and will scare most people. We have a patch for this in app-nextcloud which needs to be released, but this leads to the next issue. You can try the nextcloud update without the app-nextcloud update with no problems if you do it manually, as you can kick off the upgrade in the nextcloud console yourself there and then. We just don't think it suitable for general release.

@Patrick & Eric,
The final piece in the jigsaw for Nextcloud and it also affects all paid apps, is the migration to the new marketplace. This is blocking updates to all paid apps. This is the issue in the weekly releases thread which is blocking the Dynamic VPN and another couple of other apps.

Nick Howitt wrote:

Hi Patrick,

Is there something missing from your post about /etc/kopano/ldap.cfg?

There was indeed something missing. I've added the lines for ldap.


I'm still testing with this and will come back with some review.
One thing i noticed yesterday is een issue with some mailboxes.
A few were not accessible any more. It has something to do with --store and i looking into this the coming days.
Also trying to setup up a clean installation, to see how this works. My installation still has the upgrade from Zarafa to Kopano and is having still some dependencies with Zarafa repos Ido not know why this is still)

RE: the message about 4-byte utf-8 .. if that's what I think it is, it's also common to the later versions of Nextcoud .. the MariaDB tables for Nextcloud (and, I suspect, kopano) require the 4-byte capability to support emojis. It only applies to those tables and is easy to put in place and it's a one-time conversion - I've got the latest version of Nextcloud living in its own virtual web subdomain running php 7.2 (on a COS7 server using the 7.2 option of the php-engine app).

I've talked with Tyler and will coordinate with Shad to see if we can get a testing repo as a sort of mirror for the latest updates. That way we can simply push any patches from Kopano that don't break things. I need to get approval from Kopano to do this though because this isn't open source and I cannot simply distribute without their approval. I'll update you Tuesday or after once I have a few days to work through some of the contacting and logistics.

Hi Patrick,

Is there something missing from your post about /etc/kopano/ldap.cfg?

Your post is not particularly good news either as it will take developer control. A developer will have to monitor the app updates, and concoct a suitable upgrade script to tweak the parameters and sort the database out. This is the sort of issue I was alluding to earlier.

FWIW, it is possible to test incoming e-mails a bit. If you give your VM mailserver subdomain, e.g. my domain is howitts.co.uk. My testbox is microserver.howitts.co.uk. Also add this to your main server SMTP Settings > Mail Forwarding. Then you can send test e-mails to your VM e.g test@microserver.howitts.co.uk. If you can sort out your external DNS you can even receive e-mails externally. I would have to add an MX record for microserver.howitts.co.uk pointing to my WAN IP. You can do the same with your VM's poweredbyclear.com DDNS. You may get away without and MX record if you have an A record instead (which the poweredbyclear.com DDNS has)

Dave, Nick

I've updates Kopano-core on a VM installation to 8.7.3 using the yum repos from Kopano.

Dependencies Resolved



==================================================================================================================

 Package                      Arch      Version                 Repository                                    Size

==================================================================================================================

Installing:

 kopano-common                x86_64    8.7.3.0-3.1             Kopano-core                                   40 k

     replacing  libkchl0.x86_64 8.4.5.0-33.1

     replacing  libkcmapi0.x86_64 8.4.5.0-33.1

     replacing  libkcssl0.x86_64 8.4.5.0-33.1

     replacing  libkcsync0.x86_64 8.4.5.0-33.1

 python2-kopano               x86_64    8.7.3.0-3.1             Kopano-core                                  271 k

     replacing  python-kopano.x86_64 8.4.5.0-33.1

 python2-mapi                 x86_64    8.7.3.0-3.1             Kopano-core                                  397 k

     replacing  python-mapi.x86_64 8.4.5.0-33.1

Updating:

 kopano-backup                x86_64    8.7.3.0-3.1             Kopano-core                                   51 k

 kopano-client                x86_64    8.7.3.0-3.1             Kopano-core                                  442 k

 kopano-contacts              x86_64    8.7.3.0-3.1             Kopano-core                                   57 k

 kopano-dagent                x86_64    8.7.3.0-3.1             Kopano-core                                  136 k

 kopano-gateway               x86_64    8.7.3.0-3.1             Kopano-core                                  157 k

 kopano-ical                  x86_64    8.7.3.0-3.1             Kopano-core                                  153 k

 kopano-lang                  x86_64    8.7.3.0-3.1             Kopano-core                                   80 k

 kopano-monitor               x86_64    8.7.3.0-3.1             Kopano-core                                   73 k

 kopano-presence              x86_64    8.7.3.0-3.1             Kopano-core                                   33 k

 kopano-search                x86_64    8.7.3.0-3.1             Kopano-core                                   62 k

 kopano-server                x86_64    8.7.3.0-3.1             Kopano-core                                  325 k

 kopano-server-packages       x86_64    8.7.3.0-3.1             Kopano-core                                   20 k

 kopano-spooler               x86_64    8.7.3.0-3.1             Kopano-core                                   96 k

 kopano-utils                 x86_64    8.7.3.0-3.1             Kopano-core                                  298 k

 libkcarchiver0               x86_64    8.7.3.0-3.1             Kopano-core                                  121 k

 libkcarchivercore0           x86_64    8.7.3.0-3.1             Kopano-core                                  127 k

 libkcfreebusy0               x86_64    8.7.3.0-3.1             Kopano-core                                   68 k

 libkcicalmapi0               x86_64    8.7.3.0-3.1             Kopano-core                                  133 k

 libkcinetmapi0               x86_64    8.7.3.0-3.1             Kopano-core                                  230 k

 libkcserver0                 x86_64    8.7.3.0-3.1             Kopano-core                                  737 k

 libkcsoap0                   x86_64    8.7.3.0-3.1             Kopano-core                                  276 k

 libkcutil0                   x86_64    8.7.3.0-3.1             Kopano-core                                  223 k

 libmapi1                     x86_64    8.7.3.0-3.1             Kopano-core                                  215 k

 libs3-4                      x86_64    4.1.git257-2.3          Kopano-core                                   41 k

 libtcmalloc4                 x86_64    2.5-34.10               Kopano-core                                  258 k

 php-mapi                     x86_64    8.7.3.0-3.1             Kopano-core                                  212 k

 php-mapi-webapp              noarch    0-1.7                   Kopano-core                                  2.9 k

 python-Flask                 x86_64    0.10.1-2.9              Kopano-core                                  201 k

 python-Jinja2                noarch    2.7.3-1.9               Kopano-core                                  336 k

 python-MarkupSafe            x86_64    0.23-1.8                Kopano-core                                   32 k

 python-Werkzeug              noarch    0.10.4-1.8              Kopano-core                                  421 k

 python-itsdangerous          noarch    0.24-1.8                Kopano-core                                   23 k

 python-tlslite               noarch    0.4.6-1.9               Kopano-core                                  165 k

 xapian-core                  x86_64    1.2.22-1.1              Kopano-core                                  127 k

 xapian-core-libs             x86_64    1.2.22-1.1              Kopano-core                                  773 k

Installing for dependencies:

 app-zarafa-extension-core    noarch    1:2.5.0-1.v7            clearos-contribs                             8.2 k

 kopano-dagent-pytils         x86_64    8.7.3.0-3.1             Kopano-core                                   58 k

 kopano-python-utils          x86_64    8.7.3.0-3.1             Kopano-core                                   73 k

 libHX                        x86_64    3.22-9.el7              clearos-epel-verified                         64 k

 libgsoap-kopano-2_8_84       x86_64    2.8.84-3.1              Kopano-core                                  292 k

 libjsoncpp19                 x86_64    1.8.4-3.8               Kopano-core                                   85 k

 libkcoidc0                   x86_64    0.4.4-1.3               Kopano-core                                  1.6 M

 libkcpyplug0                 x86_64    8.7.3.0-3.1             Kopano-core                                   34 k

 libkcrosie0                  x86_64    8.7.3.0-3.1             Kopano-core                                   34 k

 libtidy                      x86_64    5.4.0-1.el7             clearos-epel-verified                        174 k

 libvmime-kopano2             x86_64    0.9.2.85-6.1            Kopano-core                                  783 k

 openjpeg-libs                x86_64    1.5.1-18.el7            clearos-centos-verified                       86 k

 poppler                      x86_64    0.26.5-20.el7           clearos-centos-verified                      784 k

 poppler-data                 noarch    0.4.6-3.el7             clearos-centos-verified                      2.2 M

 poppler-utils                x86_64    0.26.5-20.el7           clearos-centos-verified                      166 k

 python-sleekxmpp             noarch    1.1.11-4.2              private-clearcenter-zarafa-community         539 k



Transaction Summary

==================================================================================================================

Install   3 Packages (+16 Dependent packages)

Upgrade  35 Packages



Total download size: 14 M

After the update you need to change /etc/kopano/server.cfg
Add # to these lines

# Accept normal TCP connections (not recommended to disable)

#server_tcp_enabled	= yes



# Port to bind to

#server_tcp_port		= 236





#  SSL SETTINGS



# enable SSL support in server

#server_ssl_enabled	= no



# Listen for SSL connections on this port

#server_ssl_port		= 237



# Maximum SOAP keep_alive value

# default: 100

#server_max_keep_alive_requests	=	100

After installation restart the kopano server

kopano-condrestart

/etc/kopano/ldap.cfg

Add # to these lines

# LDAP host name/IP address

# Optional, default = localhost

#ldap_host = localhost



# LDAP port

# Optional, default = 389

# Use 636 for ldaps

#ldap_port = 389



# LDAP protocol

# Optional, default = ldap

# use 'ldaps' for SSL encryption. Make sure /etc/ldap/ldap.conf is

# configured correctly with TLS_CACERT

#ldap_protocol = ldap

This message was in the log file

Wed Jul 17 20:44:21 2019: [warning] K-1244: Your database does not support storing 4-byte UTF-8! The content of some mails may be truncated. The DB should be upgraded with `kopano-dbadm usmp` and kopano-server be restarted.

I've tested it on my VM, but i can not test the incoming email etc... Outgoing is working.
Let me know if you want some extra information.

<moderator>
Edited to save real estate
</moderator>

Hi Dave,

Appreciate your reply, and maybe it is the minor communication that is given the impression that there is no movement with COS
That is why I was very happy Nick started this thread, but then I remained a little bit silent.


Regarding your question about Kopano.
Please check my post on the forum : https://www.clearos.com/clearfoundation/social/community/update-webapp-and-z-push

Just let me know if i can give more support.
Definitely will attend a meeting shortly !

Nick is often very conservative about tooting his own horn but there has been quite a lot that has happened over the past few months. Of course he is always looking forward and onward to the next issue which but I will recap some of the things we have accomplished this last quarter specifically with the community wish list. Bear in mind that Nick and I have specific priorities and obligations to ClearCenter and her customers that can preempt our time on things we get to do for the community. Some of these tasks indirectly resolve outstanding community issues as well, and sometimes it may appear like we are ignoring the needs but we are obligated in our jobs to fulfill Business user requests and features which dialog is not often apparent to the community.

Outside of the 50+ hours a week I'm putting in for ClearCenter, I often get the opportunity to work on some community things. This always includes the Saturday morning community conference call (volunteered time) as well as some development.


-Training. We have been giving training to members in the community that have shown up to the meetings on Saturday that enables them to commit code and understand how our process is working.
-Merge Requests. The most fast-tracked feature requests are those that are accompanied by a merge request. We actually have several that are related to the network stack that are in the process of being merged. Kudos to Todd!!!
-Translation. Along the same lines, we have been improving localization for Dutch from the work of Marcel!!
-Antivirus. This is one where Nick has not tooted his own horn but we just had a great update to the antivirus stack from his work. This was non-trivial and we are excited by how much Nick was able to do to get this done for all of us.
-Logs. Another feature request that Nick fixed was some logging issues.
-Flexshare. Here is another quite one that didn't get filed as a proper bug but Nick fixed it anyway in app-flexshare-2.4.14. The enables are working now per your request .


While not on this thread, the addition of the code to the app-storage has been a lingering task for years that is finally being addressed. This will allow for better control over disks that are attached and aid in the provisioning of disks. We fully anticipate MORE feature requests around this app to improve functionality and look forward to any merge requests from intrepid community members that want to improve the app.

On the Kopano front, we are in the last stages of migrating some of the marketplace process flow and update mechanisms from an older system. For us this is an obvious barrier to anything Kopano related items that has prevented engagement. That being said, your (Patrick) foraging into using the Kopano repos is actually a brilliant innovation that can be leveraged greatly to solve the maintenance issues with Kopano. I will discuss this with Shad when I see him next but if you can detail all the steps you did to set it up and anything you do to maintain it the way you have it will be quite useful moving forward.

Nick Howitt wrote:

Please don't underestimate the effort required to maintain Kopano. It is non-trivial and is not just a question of recompiling their code. It has unfortunately not been written on maintained in such a way as to be easily integrated into ClearOS. I tried compiling z-push a couple of months ago and the sources have massively changed how they are packaged so I failed - but then I am not good at compiling.

Z-push and webapp can easily being update with the kopano-repos.
I'm doing this now for a few months and no problems at all. No recompiling needed, may for new installs this is needed

Nick Howitt wrote:
Have you considered popping into one of the Saturday Community meetings? You are welcome to come along and give your opinions.

Yes. I considered it and will do this again ;-)
I'm not a programmer or IT, but just a long time user

Please don't underestimate the effort required to maintain Kopano. It is non-trivial and is not just a question of recompiling their code. It has unfortunately not been written on maintained in such a way as to be easily integrated into ClearOS. I tried compiling z-push a couple of months ago and the sources have massively changed how they are packaged so I failed - but then I am not good at compiling.

Have you considered popping into one of the Saturday Community meetings? You are welcome to come along and give your opinions.

Hi Nick,

No offence and I appreciate the support you are given. We are now more the 2 months away from the first post.
The updates from ClearOS are not very fast in general and to my opinion some updates (especially the paid packages) could have been more up-to-date.
For example Kopano. This is a paid packaged and beside the core package you can easily update with the repos from Kopano.
You can push these packages into the COS repos easily. The core packages is already very old, v8.5.8.2 April 2018 vs v8.7.5.0

The change of the kopano-app for the of location of the backup, shouldn't be very hard to change

I just checked recently and it seems that i'm a user from 2003 of CC and then COS and appreciate the effort of the team, but it is moving slow.
again, this is my opinion and not trying to offend any one.

Difficult one. You can see the ones I've done. The devs got pulled off to do some website stuff for the last two weeks, but are back again. They are trying to finish off the Storage Manager and did a lot of commits today but not enough to build a new version. Dave was talking about updating the OpenVPN app as there is a lot we can do with it relatively easily (I think). Personally there is a big blocker, app-certificate-manager which is in the middle of a rewrite and work on it has stopped. I think it needs to be completed first but it will take a lot of development effort to get anywhere with it. It is not my call.

Also there is a code merge request from the community. If that can be merged, I can change PPPoE connections to use kernel mode which is way more resource efficient and can support high speed connections. I know it is not on the list but it keeps popping up with paying customers and on the community. I am waiting for the code merge.

I'll try and get an update from Dave.

Nick,

Can you give some feedback on the development of the listed features.
Any progress report is very welcome.

Expand the APC UPS Backup Manager app to allow for at least network connectivity to an APC Network Management Card. Not just USB.

Sandbo Chang wrote:

Also, could we change the port used by OpenVPN from the GUI?
While not being completely useful against deep packet inspection, it still helps in some cases where other ports are blocked (1194).

Hmm. That would be a little more complicated as you have to change the configured port in the downloadable .ovpn file as well.

Also, could we change the port used by OpenVPN from the GUI?
While not being completely useful against deep packet inspection, it still helps in some cases where other ports are blocked (1194).

@Patrick,
Unfortunately that has been put down for ClearOS 8 - Gitlab issue #5

Hi Nick,

A new feature request.
Is it possible to add a button in de fail2bin app to unban a blocked IP. (see attachment)
Now you need to do this in the console

fail2ban-client set {jail-name} unbanip {IP_to_unblock}

This can be much easier.;-)

Nick Howitt wrote:

@Patrick, the flexshare issue is a hangup from Clearos6.x and must have been overlooked. Try changing line 86 in /usr/clearos/apps/flexshare/views/summary.php to:

($share['ShareEnabled'] ? '<span class="fa fa-check"></span>' : '')

I'll ask Dave if he is happy with the possible change.

`
I sa w a new version in test repo. This solved the issue

@Patrick, the flexshare issue is a hangup from Clearos6.x and must have been overlooked. Try changing line 86 in /usr/clearos/apps/flexshare/views/summary.php to:

($share['ShareEnabled'] ? '<span class="fa fa-check"></span>' : '')

I'll ask Dave if he is happy with the possible change.

As far as I can see, the issue is with the CSS on the line in question. If you remove it and just leave the bit at the beginning, the Webconfig displays a 1 or 0.

Nick Howitt wrote:

@Patrick, I can see the line that is wrong (86 in /usr/clearos/apps/flexshare/views/summary.php) but I have no idea how to fix it and I can't find another panel with disabled/enabled in a table to crib off. I'll file a bug.

Nick,

maybe this app "php_engines" helps : /app/php_engines

@Patrick, I can see the line that is wrong (86 in /usr/clearos/apps/flexshare/views/summary.php) but I have no idea how to fix it and I can't find another panel with disabled/enabled in a table to crib off. I'll file a bug.

Hi,

I think there is a small bug in the app-flexshare.
At the main screen of flexshare the colomn "Enable" remains empty. (see attachment)

@Richard George,
I've done a quick update to app-bmbackup and it is sync'ing the testing repo. It should be in all repos within 2 hours. You can install it with:

yum update app-bmbackup --enablerepo=clearos-contribs-testing

I am not an app-bmbackup user normally, but I'll see if I can test it as well.

If it fails, you can revert with a:

yum downgrade app-bmbackup app-bmbackup-core

The update is to switch to using /usr/clearos/apps/configuration_backup/deploy/backup.conf instead of /etc/clearos/bmbackup.d/backup.conf as its source of files to be backed up.

Richard George wrote:

Nick; a little more on the Baremetal Backup ..

I've been comparing the configuration file with the equivalent one in configuration_backup - it's clear that as the format is exactly the same, that the BMB version started life as the 'built-in' backup version - but it now lags behind .. as obviously things have moved on.

Can I suggest that as a quick fix, the BMB version is updated to match the configuration_backup version, and moving forward, that perhaps BMB is undated to use the 'parent' instead? That way both versions of the backup mechanisms are 'singing from the same hymn sheet'.

I think that is a good idea. I've had a little look at the programs. App-configuration-backup is installed by default and we could make app-bmbackup depend on it, then switch app-bmbackup to read the file from app-configuration-backup. I may even have enough c&p skills to do that (I am not a php programmer).

FWIW the list in app-configuration-backup is also well out of date, not keeping up with new programs. It has not even kept up with the new layout of the web-proxy configuration files. There is an issue on GitLab raised to cover this.

[edit]
I've done one backup with the updated app and it appears to have worked in that the original /etc/clearos/bmbackup.d/backup.conf file is no longer there and it still backed up and has more configs backed up.

I've also updated a the list of files being backed up in app-configuration-backup. You can install the updated app with:

yum update app-configuration-backup --enablerepo=clearos-updates-testing

If you want any more items backed up, please post to the Gitlab Issue #5. I am currently working on the principle that backed up files should not really include your manual tweaks so I've had to leave a few of my personal favourites out. I would need to discuss it with the devs if people want other files with manual tweaks backing up.
[/edit]

Nick; a little more on the Baremetal Backup ..

I've been comparing the configuration file with the equivalent one in configuration_backup - it's clear that as the format is exactly the same, that the BMB version started life as the 'built-in' backup version - but it now lags behind .. as obviously things have moved on.

Can I suggest that as a quick fix, the BMB version is updated to match the configuration_backup version, and moving forward, that perhaps BMB is undated to use the 'parent' instead? That way both versions of the backup mechanisms are 'singing from the same hymnsheet'.

Sandbo Chang wrote:

Nick Howitt wrote:

@Sandbo, how do you do that? I know you can make /var/lib/openvpn/ipp.txt read-only and manually maintain it but OpenVPN does not always honour the entries. Normally it tries to reuse the information in that file so IP's should be pretty static, unless you run out of them.

Hi Nick,

I am not really familiar, just saw some tutorials mentioning it:
https://www.itsfullofstars.de/2018/09/openvpn-assign-static-ip-to-client/

In my case, as you mentioned, the IP is pretty much static, but for one time, after reconnecting one client somehow changed to use another IP and screwed up the network drive connection on another system. So I just wonder if this can become a handy option on GUI.

Be a little careful of this but it does work. ClearOS uses the default topology of "net30". Please see this reference. It means that IP addresses are used in blocks of four. If you look in /var/lib/openvpn/ipp.txt, you see the base address for each user. The remote device will get the remote address of base address +2 and the server address will be base address +1. This means your line in the file in the ccd folder should read:

ifconfig-push {remote_address} {server_address}

Could we add an easy way to change the MAC address of the WAN interface?
This is a commonly available option on off-the-shelf routers, and it is a convenient way to acquire a different IP address from the ISP in case it is needed, e.g. to renew the IP of the VPN when it gets block by a certain service.

Nick Howitt wrote:

@Sandbo, how do you do that? I know you can make /var/lib/openvpn/ipp.txt read-only and manually maintain it but OpenVPN does not always honour the entries. Normally it tries to reuse the information in that file so IP's should be pretty static, unless you run out of them.

Hi Nick,

I am not really familiar, just saw some tutorials mentioning it:
https://www.itsfullofstars.de/2018/09/openvpn-assign-static-ip-to-client/

In my case, as you mentioned, the IP is pretty much static, but for one time, after reconnecting one client somehow changed to use another IP and screwed up the network drive connection on another system. So I just wonder if this can become a handy option on GUI.

@Sandbo, how do you do that? I know you can make /var/lib/openvpn/ipp.txt read-only and manually maintain it but OpenVPN does not always honour the entries. Normally it tries to reuse the information in that file so IP's should be pretty static, unless you run out of them.

Lately after using OpenVPN more, I think one feature can be very helpful if on GUI, that is,
make it available to assign a fixed IP for a specific client from the server side.

While this can be done by editing the server config, it will be great if we can do it using GUI.

Yeah, it's not cheap true!

I have a rack at home. I think I'm a bit addicted with everything what has to do with server stuff. I use the power of a six persons household.