@thecreativeone91 said:

@scottalanmiller Native in windows

Oh, well that is to be expected. You are still basically virtualizing the application. You can't reasonably ask an app to run on a non-native platform with native performance.

Yup, pretty normal. Postgres is the database. Hashing never stops, baby.

Unitrends is constantly preparing itself for need to do an autosynth, and is working on the dedup and inline hashing and everything else all the time. It's pretty normal for postsgres to be pegged.

Those look so cool. I am glad to see that they were able to get the first shipment out the door. Hopefully these really take off.

So true. Elastix is now only on two gen old CentOS. Argh.

Hard to really be easier than the SysV system. All that was was running through a list of commands alphabetically. About as basic as it gets.

This has been speculated about for quite some time. Makes a lot of sense.

There we go, all set. Hopefully that will help some people get started with Chef since it is basically really simple but lacking a few specific things that you "just have to know" because Opscode does not document them (a gap in the Chef 12 documents) it is very hard for no reason.

http://www.itwire.com/business-it-news/open-source/66153-systemd-fallout-two-debian-technical-panel-members-resign

http://www.themukt.com/wp-content/uploads/2014/09/toshiba-chromebook-1-700x394.jpg

Looks pretty interesting, will have to try that out. Session sharing can be super useful for UNIX.

It looks like a sweet setup.

reading the About page triggers a voice in my head - is it safe / secure?

I know that question smacks of complete distrust and such, I'm not a real conspiracy nut; but i/m generally cautious of software....

Cool, thanks. I wish that it announced which ones were which. I can only identify a few.

Here is the additional log info:

#systemctl status pgateway.service pgateway.service - SYSV: The Pertino Client provides access to the Pertino Network. Loaded: loaded (/etc/init.d/pgateway) Active: failed (Result: exit-code) since Tue 2014-09-02 23:33:27 EDT; 3min 48s ago Process: 21792 ExecStart=/etc/init.d/pgateway start (code=exited, status=127) Sep 02 23:33:27 to-lnx-oc1 pgateway[21792]: /etc/init.d/pgateway: line 9: /etc/init.d/functions: No such file or directory Sep 02 23:33:27 to-lnx-oc1 pgateway[21792]: /etc/init.d/pgateway: line 12: .: /etc/sysconfig/network: is a directory Sep 02 23:33:27 to-lnx-oc1 pgateway[21792]: Starting pGateway: /etc/init.d/pgateway: line 25: daemon: command not found Sep 02 23:33:27 to-lnx-oc1 systemd[1]: pgateway.service: control process exited, code=exited status=127 Sep 02 23:33:27 to-lnx-oc1 systemd[1]: Failed to start SYSV: The Pertino Client provides access to the Pertino Network.. Sep 02 23:33:27 to-lnx-oc1 systemd[1]: Unit pgateway.service entered failed state.

That looks pretty much in line with the past bad design decisions from the Ubuntu camp.