Search the Community

EMC Corporation ha annunciato i risultati dell'ultimo studio sull'universo digitale dei dati, realizzato da IDC e sponsorizzato da EMC, dal titolo "Big Data, Bigger and Biggest*Growth Digital Shadows... Continua a leggere, clicca qui.

CloudSigma, un importante cloud provider IaaS svizzero, ha annunciato martedì il rilascio di un white paper scritto per promuovere il public cloud IaaS di Cloud Sigma, cofrontando la sua flessibilit... Continua a leggere, clicca qui.

Amazon Web Services*è la piattaforma maggiormente utilizzata dagli sviluppatori, mentre Windows Azure sta mostrando una crescita considerevole, secondo un'indagine condotta da Forrester Research di ... Continua a leggere, clicca qui.

Non capita spesso di vedere uno studio accademico di respiro internazionale in cui accanto a stati tecnologicamente avanzati quali gli USA, la Germania e il Regno Unito sia presa in considerazione anc... Continua a leggere, clicca qui.

SIRMI ha rilasciato i dati relativi all’andamento del terzo trimestre 2012*del mercato della Digital Technology nei suoi diversi comparti.*I dati di analisi mostrano nell'ultimo trimestre un Merca... Continua a leggere, clicca qui.

Una serie di indagini svolte recentemente sul cloud sembra indicare una fiorente adozione di servizi cloud da parte delle aziende.*Una ricerca condotta da HP mostra dei risultati in cui la maggioranz... Continua a leggere, clicca qui.

La recessione economica in Italia non risparmia neanche il settore informatico, è così che Assintel rivela i dati negativi riscontrati nel decorso di questo 2012. Se nel primo trimestre 2012 il fatt... Continua a leggere, clicca qui.

Gartner ha annunciato il suo magic quadrant annuale per il settore cloud Infrastructure-as-a-Service. La lista è stata compilata dagli analisti di Gartner Lydia Leong, Douglas Toombs, Bob Gill, Grego... Continua a leggere, clicca qui.

DiViNetworks, un provider di ottimizzazioni di banda IP di traffico per operatori di rete e service provider, è in una posizione di mercato ideale per studiare le caratteristiche ed i trend del fluss... Continua a leggere, clicca qui.

OpenNebula, il cloud open source utilizzato anche dall'agenzia spaziale europea e dal CERN, sembra stia facendo buoni numeri, sia nelle aziende private che fuori dall'Europa. Secondo una recente indag... Continua a leggere, clicca qui.

Avanade, compagnia di servizi IT, ha pubblicato i risultati di una ricerca mondiale condotta sull'argomento Big Data, commissionata ad aprile a Wakefield Research, e dal titolo “Is Big Data producin... Continua a leggere, clicca qui.

E' stata recentemente svolta una ricerca dal titolo “The IAB Mobile Phone Shopping Diaries”, che mostra le abitudini di interazione dei consumatori con gli smartphone, ed in particolare rivela che... Continua a leggere, clicca qui.

Ma i social network sono davvero una roba per perditempo e fannulloni o possono davvero essere una fonte primaria di sviluppo e aiuto alle imprese? Millward Brown ha recentemente condotto uno studi... Continua a leggere, clicca qui.

Una recente ricerca ha rilevato che Apple rimane dominante nel mercato tablet enterprise, con oltre il 97 per cento di attivazioni di tablet in azienda attribuibili ad iPad, relative al primo trimestr... Continua a leggere, clicca qui.

Microsoft ha realizzato un nuovo report dal titolo “SMB Cloud Adoption Study 2011” lo scorso mese, il quale esplora le attitudini delle piccole e medie aziende riguardo all'adozione di servizi clo... Continua a leggere, clicca qui.

Le moderne aziende stanno diventando sempre più dipendenti dal cloud, ed a sua volta il cloud stesso richiede un ambiente nel quale esistere. I colocation center offrono alle aziende ed ai fornitori ... Continua a leggere, clicca qui.

Una nuova ricerca portata a termine da Campos Research & Analysis per conto di Digital Realty Trust, una società immobiliare di data center, ha pubblicato alcuni dati riguardanti il mercato nord ... Continua a leggere, clicca qui.

salve ragazzi, non capisco il motivo ma improvvisamente il mio vps ha smesso di funzionare. le pagine html le apre correttamente, ma appena vado nel forum si pianta dandomi errore, come se ci fosse un problema con il database mysql. poi mi sono accorto che non mi si collegava più nemmeno all'ftp, poi dopo un po senza spiegazione si è collegato. da virtuozzo non mi fa entrare in filemanager. ho riavviato diverse volte il vps, provato a fare lo spegnimento e l'accensione. niente da fare... da plesk guardando i servizi attivi, vedo il servizio qmail stoppato, ma non riesco ad avviarlo!! ho controllato l'error_log di apache e questo è il risultato.. come posso rimediare? grazie [sun Dec 21 04:35:51 2008] [notice] Digest: generating secret for digest authentication ... [sun Dec 21 04:35:51 2008] [notice] Digest: done [sun Dec 21 04:35:52 2008] [notice] mod_python: Creating 4 session mutexes based on 10 max processes and 0 max threads. [sun Dec 21 04:35:52 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sun Dec 21 04:35:52 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sun Dec 21 04:35:52 2008] [warn] Init: SSL server IP/port conflict: default-89-188-130-52:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:80) vs. webmail:443 ($ [sun Dec 21 04:35:52 2008] [warn] Init: SSL server IP/port conflict: nokiasymbian.it:443 (/var/www/vhosts/nokiasymbian.it/conf/httpd.include:12) vs. webmail$ [sun Dec 21 04:35:52 2008] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!! [sun Dec 21 04:35:52 2008] [warn] WARNING: Attempt to change ServerLimit ignored during restart [sun Dec 21 04:35:52 2008] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) [Wed Dec 24 02:00:58 2008] [notice] caught SIGTERM, shutting down [Wed Dec 24 02:01:36 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Wed Dec 24 02:01:37 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Wed Dec 24 02:01:37 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Wed Dec 24 02:01:37 2008] [warn] Init: SSL server IP/port conflict: default-89-188-130-52:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:80) vs. webmail:443 ($ [Wed Dec 24 02:01:37 2008] [warn] Init: SSL server IP/port conflict: nokiasymbian.it:443 (/var/www/vhosts/nokiasymbian.it/conf/httpd.include:12) vs. webmail$ [Wed Dec 24 02:01:37 2008] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!! [Wed Dec 24 02:01:37 2008] [notice] Digest: generating secret for digest authentication ... [Wed Dec 24 02:01:37 2008] [notice] Digest: done [Wed Dec 24 02:01:37 2008] [notice] mod_python: Creating 4 session mutexes based on 10 max processes and 0 max threads. [Wed Dec 24 02:01:38 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Wed Dec 24 02:01:38 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [Wed Dec 24 02:01:38 2008] [warn] Init: SSL server IP/port conflict: default-89-188-130-52:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:80) vs. webmail:443 ($ [Wed Dec 24 02:01:38 2008] [warn] Init: SSL server IP/port conflict: nokiasymbian.it:443 (/var/www/vhosts/nokiasymbian.it/conf/httpd.include:12) vs. webmail$ [Wed Dec 24 02:01:38 2008] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!! [Wed Dec 24 02:01:38 2008] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations [Wed Dec 24 02:05:43 2008] [error] server reached MaxClients setting, consider raising the MaxClients setting [sat Dec 27 11:17:57 2008] [notice] caught SIGTERM, shutting down [sat Dec 27 11:18:36 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [sat Dec 27 11:18:36 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:18:36 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:18:36 2008] [warn] Init: SSL server IP/port conflict: default-89-188-130-52:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:80) vs. webmail:443 ($ [sat Dec 27 11:18:36 2008] [warn] Init: SSL server IP/port conflict: nokiasymbian.it:443 (/var/www/vhosts/nokiasymbian.it/conf/httpd.include:12) vs. webmail$ [sat Dec 27 11:18:36 2008] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!! [sat Dec 27 11:18:36 2008] [notice] Digest: generating secret for digest authentication ... [sat Dec 27 11:18:36 2008] [notice] Digest: done [sat Dec 27 11:18:37 2008] [notice] mod_python: Creating 4 session mutexes based on 10 max processes and 0 max threads. [sat Dec 27 11:18:37 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:18:37 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:18:37 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:18:37 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:18:37 2008] [warn] Init: SSL server IP/port conflict: default-89-188-130-52:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:80) vs. webmail:443 ($ [sat Dec 27 11:18:37 2008] [warn] Init: SSL server IP/port conflict: nokiasymbian.it:443 (/var/www/vhosts/nokiasymbian.it/conf/httpd.include:12) vs. webmail$ [sat Dec 27 11:18:37 2008] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!! [sat Dec 27 11:18:37 2008] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: qq read error (#4.3.0) [sat Dec 27 11:52:31 2008] [notice] caught SIGTERM, shutting down [sat Dec 27 11:54:07 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [sat Dec 27 11:54:07 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:54:07 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:54:07 2008] [warn] Init: SSL server IP/port conflict: default-89-188-130-52:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:80) vs. webmail:443 ($ [sat Dec 27 11:54:07 2008] [warn] Init: SSL server IP/port conflict: nokiasymbian.it:443 (/var/www/vhosts/nokiasymbian.it/conf/httpd.include:12) vs. webmail$ [sat Dec 27 11:54:07 2008] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!! [sat Dec 27 11:54:07 2008] [notice] Digest: generating secret for digest authentication ... [sat Dec 27 11:54:07 2008] [notice] Digest: done [sat Dec 27 11:54:07 2008] [notice] mod_python: Creating 4 session mutexes based on 10 max processes and 0 max threads. [sat Dec 27 11:54:07 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:54:07 2008] [notice] mod_python: Creating 4 session mutexes based on 10 max processes and 0 max threads. [sat Dec 27 11:54:07 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:54:07 2008] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!? [sat Dec 27 11:54:07 2008] [warn] Init: SSL server IP/port conflict: default-89-188-130-52:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:80) vs. webmail:443 ($ [sat Dec 27 11:54:07 2008] [warn] Init: SSL server IP/port conflict: nokiasymbian.it:443 (/var/www/vhosts/nokiasymbian.it/conf/httpd.include:12) vs. webmail$ [sat Dec 27 11:54:07 2008] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!! [sat Dec 27 11:54:07 2008] [notice] Apache/2.2.3 (CentOS) configured -- resuming normal operations qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) [sat Dec 27 11:55:36 2008] [error] server reached MaxClients setting, consider raising the MaxClients setting qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: qq read error (#4.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0) qmail-inject: fatal: mail server permanently rejected message (#5.3.0)

Symantec presenta i risultati dello studio "Green Data Center" sull'attuale implementazione di nuove tecnologie e strutture per il risparmio energetico. La scelta di hardware moderno rimane l'elemento principale per raggiungere gli obbiettivi come datacenter "green" Leggi la News

Ho un problema vorrei passare dalla visualizzazione da report statici a report dinamici, ma non so come fare. Il tutto su un Server Virtuali Aruba VPS linux. grazie in anticipo

Ciao ragazzi , volevo farvi una domanda....esistono dei programmi free che si interfacciano con una vps linux , o piu sensatamente dei programmi da installare , che una volta creato un account mandino via email del cliente creato tutto il report , come quelli che fanno i veri hoster al momento dell'attivzione di un dominio?:emoticons_dent2020: La vps per un altro mese è linux aruba , dopo seflow rulez :approved: :sbav: