aelius

O scula buna pentru a face traceroute remote utilizand route servers rtracert.c #include <stdio.h> #include <netdb.h> #include <sys/types.h> #include <sys/socket.h> #include <netinet/in.h> #include <arpa/inet.h> #include <stdlib.h> #include <string.h> #include <unistd.h> #include <sys/stat.h> #include <fcntl.h> #include <sys/timeb.h> #include <ctype.h> #define TCP_PORT 23 int main(int argc, char *argv[]) { int sockfd; int i; struct sockaddr_in serv_addr; char buff[32]; struct hostent *he; if(argc != 3) { puts("!PARM"); exit(1); } if(!(he = gethostbyname(argv[1]))) { puts("Unrecognized host or address."); exit(2); } if( ( sockfd = socket(AF_INET, SOCK_STREAM, 0)) < 0) { puts("client: can't open socket."); exit(1); } bzero((char*)&serv_addr, sizeof(serv_addr)) ; serv_addr.sin_family = AF_INET ; memcpy(&serv_addr.sin_addr, he->h_addr, 4); serv_addr.sin_port = htons(TCP_PORT); if(connect(sockfd, (struct sockaddr*)&serv_addr, sizeof(serv_addr))<0) { puts("client: can't connect to server"); exit(1); } write(sockfd, "traceroute ", strlen("traceroute ")); write(sockfd, argv[2], strlen(argv[2])); write(sockfd, "\n", 1); while (1) { i = read(sockfd, buff, 1); if (buff[0] == '\n') break; } setvbuf(stdout, NULL, _IONBF, 0); while (read(sockfd, buff, 1)) { putchar(buff[0]); if (buff[0] == '>') break; } while (read(sockfd, buff, 1)) { putchar(buff[0]); if (buff[0] == '>') break; } puts(""); close(sockfd) ; exit(0) ; } Cum il utilizati ? Exemplu utilizare (dupa compilare) ./rtracert route_server ip_address Exemplu: marian@pluto:~$ cc rtracert.c -o rtracert marian@pluto:~$ ./rtracert route-server.gblx.net 8.8.8.8 ******************************* WARNING ******************************* This equipment is the property of Level 3 Communications. Unauthorized access is strictly prohibited. Any unauthorized access or tampering with this equipment will result in civil and/or criminal prosecution. ******************************* WARNING ******************************* route-server.phx1>traceroute 8.8.8.8 Type escape sequence to abort. Tracing the route to google-public-dns-a.google.com (8.8.8.8) 1 ge4-12-1000M.ar6.PHX1.gblx.net (67.16.148.37) 0 msec 0 msec 0 msec 2 72.14.197.161 8 msec 12 msec 72.14.196.50 8 msec 3 216.239.46.40 [AS 15169] 48 msec 8 msec 64.233.174.238 [AS 15169] 16 msec 4 64.233.174.192 [AS 15169] [MPLS: Label 619774 Exp 4] 12 msec 64.233.174.186 [AS 15169] [MPLS: Label 326035 Exp 4] 12 msec 72.14.238.2 [AS 15169] [MPLS: Label 604348 Exp 4] 36 msec 5 72.14.239.153 [AS 15169] [MPLS: Label 477699 Exp 4] 36 msec 40 msec 72.14.239.162 [AS 15169] [MPLS: Label 418401 Exp 4] 40 msec 6 216.239.48.167 [AS 15169] 36 msec 64.233.174.131 [AS 15169] 44 msec 40 msec Pentru mai mute route servers, cautati pe google, sunt o gramada publice. Tool-ul nu este facut de mine. E de prin 2001.

Salut, Nu poti face asta. Cel mai simplu este sa ceri o consola ipkvm la furnizor (inteleg ca e un server remote)

Cred ca ai omis sa iei in calcul faptul ca hostgator, cloudflare, etc ... nu sunt in Romania (nu au deloc echipamente in RO)

Poti determina extrem de usor daca folosesti Linux, Unix, Mac OS X .... :~# whatis file file (1) - determine file type Am redenumit aici cate ceva de test. Nu conteaza extensia (comanda file): macbook Downloads$ mv rstMailerSMTP.tar.gz test.zip macbook Downloads$ mv istumbler-99.zip istumbler.tgz macbook Downloads$ mv FusionInvoice-1.3.5-full.zip Fusion.tar.bz2 macbook Downloads$ mv magento-1.8.1.0.tar.gz magento.rar macbook Downloads$ file test.zip istumbler.tgz Fusion.tar.bz2 magento.rar test.zip: gzip compressed data, from Unix, last modified: Fri Feb 14 13:48:23 2014 istumbler.tgz: Zip archive data, at least v1.0 to extract Fusion.tar.bz2: Zip archive data, at least v2.0 to extract magento.rar: gzip compressed data, from Unix, last modified: Tue Nov 26 18:49:16 2013 macbook Downloads$ rm -rf test.zip istumbler.tgz Fusion.tar.bz2 magento.rar emulate-embedded.img.bz2: bzip2 compressed data, block size = 900k filehost_BBHH-Ultra DoS.exe: PE32 executable for MS Windows (GUI) Intel 80386 32-bit fromEmail.txt: ASCII text, with no line terminators set.eps: PostScript document text conforming DSC level 3.0, type EPS set.pdf: PDF document, version 1.3 tcp_syn_flood.doc: CDF V2 Document, Little Endian, Os: Windows, Version 5.1, Code page: 1252, Title: , Author: CPSE, Template: Normal.dot, Last Saved By: CPSE, Revision Number: 2, Name of Creating Application: Microsoft Word 10.0, Total Editing Time: 01:00, Last Printed: Wed Jun 1 21:23:00 2005, Create Time/Date: Wed Jun 1 21:24:00 2005, Last Saved Time/Date: Wed Jun 1 21:24:00 2005, Number of Pages: 1, Number of Words: 198, Number of Characters: 1129, Security: 0 untangle_1000_x64.iso: ISO 9660 CD-ROM filesystem data 'Debian 6.0 amd64 1 ' (bootable)

)))))))))))

Ma nene, copilul ala avea niste dureri extreme. Pe mine cand ma doare cate o masea ceva, as bate lumea pe strada. Cum vrei sa reactioneze, vrei sa rada copilul ala mic la durerile insuportabile. Daca mergi la dentist si iti e atins putin mai tare un nerv, "te pisi pe tine" de durere. Nu mai conteaza ca ai 6-8 sau 30 de ani. Sfat pentru cei mai tineri: Cand veti avea copil, sa nu faceti gresala sa-i aplicati acelasi program de corectie care probabil v-a fost aplicat voua. Nu-l cresteti cu teama/frica. Trebuie educati de mici pentru a se dezvolta normal. Ordine cu parul de face intre ciori sau in jungla, nu intr-o familie de oameni calumea.

Eu am un baiat de 6 ani. Nu i-am dat niciodata o palma sau sa strig la el. Chiar nu ma astept sa inteleaga unii care au 17-20 de ani.

Salut, Poti utiliza asta: http://iplogger.org/

@Nicotin: pe centos ai range (iti autoconfigureaza el alias-uri) Pentru ip range pe Centos: cd /etc/sysconfig/network-scripts cat >> ifcfg-eth0-range0 << EOF TYPE="Ethernet" IPADDR_START=10.0.0.2 IPADDR_END=10.0.0.200 IPV6INIT=no EOF chmod 755 ifcfg-eth0-range0 Note: - Asta o sa-ti faca alias-uri cu eth0:0, eth0:1 ..... pentru toate adresele ip de la 10.0.0.2 la 10.0.0.200 - Nu adaugati in rc.local; Se initializeaza ultimul (dupa ce au pornit toate serviciile), caz in care serviciile ce se listeaza pe adresele ip configurate in rc.local, nu o sa porneasca. Pentru a implementa scriptul 'ipaddr' prezentat mai sus, poti arunca o privire aici: How to run a startup script automatically after a network interface is up on CentOS - Linux FAQ

Pai sunt doua optiuni acolo: 1. Site-ul ce vrei sa-l pui e praf. 2. Nu stii sa-l configurezi. Eu vreau sa te ajut, dar mi-e imposibil sa iti dau mai multe hint-uri pentru ca nu pot decat sa-mi imaginez ce e acolo. Daca doresti ajutor direct sa-l faci, te sfatuiesc sa contactezi un om de pe aici care se ocupa cu programarea php. Iti recomand pe @eusimplu ; Eu am altele pe cap.

Sterge linia si pune asa: include(dirname(__FILE__) . '/conf/db_settings.php'); Sau asa: include($_SERVER['DOCUMENT_ROOT']."/conf/db_settings.php"); Dupa informatiile tale, fisierul 'db_settings' se afla in directorul 'conf/'

Sa nu fie editate mai exact. Informatia trebuie sa fie vazuta asa cum a fost postata. (in afara de cazurile specificate)

Gata bre, hoooo Multumim pentru tutorial @.darky

A scris bre omul, sa nu fim rai. A scris mai sus, gresise doar in imagine: https://www.dropbox.com/s/lwj7bld8ypf88hi/Screenshot%202014-03-09%2017.03.20.png

Mai lupta-te cu ea. Daca nu reusesti pana deseara, dai un semn si te ajut eu.

La tine problema sunt inregistrarile nu tabelele. mysql> create table `phpjob_cronjobs` ( -> `cron_type` enum('jobmail','resumemail','expire') NOT NULL DEFAULT 'jobmail', -> `cron_date` datetime NOT NULL DEFAULT '0000-00-00 00:00:00', -> `cron_start` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, -> `cron_status` enum('done','running') NOT NULL DEFAULT 'done', -> `cron_priority` tinyint(4) NOT NULL DEFAULT '0'); Query OK, 0 rows affected (0.14 sec) mysql> describe phpjob_cronjobs; +---------------+---------------------------------------+------+-----+---------------------+-----------------------------+ | Field | Type | Null | Key | Default | Extra | +---------------+---------------------------------------+------+-----+---------------------+-----------------------------+ | cron_type | enum('jobmail','resumemail','expire') | NO | | jobmail | | | cron_date | datetime | NO | | 0000-00-00 00:00:00 | | | cron_start | timestamp | NO | | CURRENT_TIMESTAMP | on update CURRENT_TIMESTAMP | | cron_status | enum('done','running') | NO | | done | | | cron_priority | tinyint(4) | NO | | 0 | | +---------------+---------------------------------------+------+-----+---------------------+-----------------------------+ 5 rows in set (0.00 sec) mysql> CREATE TABLE `phpjob_crossnetwork` ( -> `cross_id` int(5) NOT NULL auto_increment, -> `cross_name` varchar(80) NOT NULL default '', -> `cross_specialids` text NOT NULL, -> `cross_type` varchar(20) NOT NULL default '', -> `cross_output` enum('js','iframe','rss') NOT NULL default 'js', -> `cross_language` varchar(40) NOT NULL default '', -> `cross_display` int(5) NOT NULL default '0', -> `cross_header` text NOT NULL, -> `cross_main` text NOT NULL, -> `cross_footer` text NOT NULL, -> `cross_noresult` text NOT NULL, -> `cross_date` date NOT NULL default '0000-00-00', -> `cross_active` enum('yes','no') NOT NULL default 'yes', -> `cross_visit` bigint(11) NOT NULL default '0', -> `cross_extratype` varchar(30) NOT NULL default '', -> `cross_extraids` text NOT NULL, -> PRIMARY KEY (`cross_id`) -> ); Query OK, 0 rows affected (0.19 sec) mysql> describe phpjob_crossnetwork; +------------------+---------------------------+------+-----+------------+----------------+ | Field | Type | Null | Key | Default | Extra | +------------------+---------------------------+------+-----+------------+----------------+ | cross_id | int(5) | NO | PRI | NULL | auto_increment | | cross_name | varchar(80) | NO | | | | | cross_specialids | text | NO | | NULL | | | cross_type | varchar(20) | NO | | | | | cross_output | enum('js','iframe','rss') | NO | | js | | | cross_language | varchar(40) | NO | | | | | cross_display | int(5) | NO | | 0 | | | cross_header | text | NO | | NULL | | | cross_main | text | NO | | NULL | | | cross_footer | text | NO | | NULL | | | cross_noresult | text | NO | | NULL | | | cross_date | date | NO | | 0000-00-00 | | | cross_active | enum('yes','no') | NO | | yes | | | cross_visit | bigint(11) | NO | | 0 | | | cross_extratype | varchar(30) | NO | | | | | cross_extraids | text | NO | | NULL | | +------------------+---------------------------+------+-----+------------+----------------+ Solutia: - Editezi dump-ul (fisierul pe care vrei sa-l importi) si adaugi al fiecare insert 'ignore'. Exemplu Din asta al tau: INSERT INTO `phpjob_crossnetwork` In asta: INSERT IGNORE INTO `phpjob_crossnetwork` Si aici avem un manual dragalas: https://dev.mysql.com/doc/refman/5.5/en/insert.html

Ma scuzati ca ma bag peste voi, dar POST este un 'http request method' nu un protocol Posted by .darky Ai scris defapt ce este ala si cu ce se mananca, dar e scris gresit in imagine

Salut, Asta te coafeaza ? https://publib.boulder.ibm.com/infocenter/iseries/v5r3/index.jsp?topic=%2Frzab6%2Frzab6xnonblock.htm @MrGrj esti sigur ca este non-blocking exemplul ?

Stiu ca toti sunteti tentati sa faceti alias-uri, insa in cazul in care aveti sa spunem 200 de adrese ip de configurat pe un server, nu cred ca veti sta sa scrieti cele 200 de linii intr-un script de init. Mai mult, la comanda 'ifconfig -a' or sa fie afisate ca alias-uri (adica, mai pe romaneste, o sa vomite prima interfata de retea + 200 de alias-uri ale acesteia in CLI). Exemplu standard: root@rst:~# ifconfig eth0:1 10.0.0.2 netmask 255.255.255.0 root@rst:~# ifconfig eth0:2 10.0.0.3 netmask 255.255.255.0 root@rst:~# ifconfig eth0:3 10.0.0.4 netmask 255.255.255.0 root@rst:~# ifconfig eth0:4 10.0.0.5 netmask 255.255.255.0 root@rst:~# ifconfig eth0 Link encap:Ethernet HWaddr 08:00:27:02:c0:f1 inet addr:192.168.0.77 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe02:c0f1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2014 errors:0 dropped:0 overruns:0 frame:0 TX packets:1105 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:181623 (177.3 KiB) TX bytes:157231 (153.5 KiB) eth0:1 Link encap:Ethernet HWaddr 08:00:27:02:c0:f1 inet addr:10.0.0.2 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 eth0:2 Link encap:Ethernet HWaddr 08:00:27:02:c0:f1 inet addr:10.0.0.3 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 eth0:3 Link encap:Ethernet HWaddr 08:00:27:02:c0:f1 inet addr:10.0.0.4 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 eth0:4 Link encap:Ethernet HWaddr 08:00:27:02:c0:f1 inet addr:10.0.0.5 Bcast:10.0.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 TX bytes:0 (0.0 root@rst:~# Idee: root@rst:~# for i in {2..30} ; do ip addr add 10.0.0.$i broadcast 10.0.0.255 dev eth0 ; done root@rst:~# ifconfig -a eth0 Link encap:Ethernet HWaddr 08:00:27:02:c0:f1 inet addr:192.168.0.77 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe02:c0f1/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2522 errors:0 dropped:0 overruns:0 frame:0 TX packets:1405 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:225333 (220.0 KiB) TX bytes:204095 (199.3 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 TX bytes:0 (0.0 root@rst:~# ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 08:00:27:02:c0:f1 brd ff:ff:ff:ff:ff:ff inet 192.168.0.77/24 brd 192.168.0.255 scope global eth0 inet 10.0.0.2/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.3/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.4/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.5/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.6/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.7/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.8/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.9/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.10/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.11/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.12/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.13/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.14/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.15/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.16/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.17/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.18/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.19/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.20/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.21/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.22/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.23/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.24/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.25/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.26/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.27/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.28/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.29/32 brd 10.0.0.255 scope global eth0 inet 10.0.0.30/32 brd 10.0.0.255 scope global eth0 inet6 fe80::a00:27ff:fe02:c0f1/64 scope link valid_lft forever preferred_lft forever root@rst:~# Din cate vedeti, la ifconfig imi este afisata o singura adresa ip. No alias, no shits. Cum ar arata fisierul de configuratie al retelei in cazul in care utilizati alias-uri pe eth0 si aveti o gramada de adrese ip ? auto eth0 allow-hotplug eth0 iface eth0 inet static address 192.168.0.42 netmask 255.255.255.0 gateway 192.168.1.1 auto eth0:0 allow-hotplug eth0:0 iface eth0:0 inet static address 192.168.0.43 netmask 255.255.255.0 auto eth0:1 allow-hotplug eth0:1 iface eth0:1 inet static address 192.168.0.44 netmask 255.255.255.0 ....................... ....................... Pentru a face permanente modificarile (sa se configureze adresele ip la restart): root@rst:~# cat >> /etc/ipaddr << EOF > #!/bin/bash > for i in {2..30} ; do ip addr add 10.0.0.\$i broadcast 10.0.0.255 dev eth0 ; done > EOF root@rst:~# chmod 711 /etc/ipaddr In fisierul '/etc/network/interfaces' adaugati: post-up /etc/ipaddr Exemplu: # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet static address 192.168.0.77 netmask 255.255.255.0 gateway 192.168.0.1 post-up /etc/ipaddr Note: - Testele au fost facute pe Debian. Functioneaza pe Debian si orice distributie derivata din aceasta. - Comanda 'ip addr' functioneaza pe orice distributie linux. Face parte din pachetul iproute2 - Tema, daca aveti fetishuri cu cititul: http://www.policyrouting.org/iproute2.doc.html

[B]cat >> lista << EOF [/B]attachment.html bbcode.html breadcrumbs.html ca_config.html ca_scripts.js captcha_default.html captcha_qa.html captcha_recaptcha.html confirm_body.html custom_profile_fields.html editor.js faq_body.html forumlist_body.html index.htm index_body.html jumpbox.html login_body.html login_forum.html mcp_approve.html mcp_ban.html mcp_footer.html mcp_forum.html mcp_front.html mcp_header.html mcp_jumpbox.html mcp_logs.html mcp_message.html mcp_move.html mcp_notes_front.html mcp_notes_user.html mcp_post.html mcp_queue.html mcp_reports.html mcp_topic.html mcp_viewlogs.html mcp_warn_front.html mcp_warn_list.html mcp_warn_post.html mcp_warn_user.html mcp_whois.html memberlist_body.html memberlist_email.html memberlist_group.html memberlist_im.html memberlist_leaders.html memberlist_search.html memberlist_view.html message_body.html overall_footer.html overall_header.html pagination.html posting_attach_body.html posting_body.html posting_buttons.html posting_poll_body.html posting_preview.html posting_progress_bar.html posting_review.html posting_smilies.html posting_topic_review.html quickreply_editor.html report_body.html search_body.html search_results.html searchbox.html simple_footer.html simple_header.html template.cfg ucp_agreement.html ucp_attachments.html ucp_footer.html ucp_groups_manage.html ucp_groups_membership.html ucp_header.html ucp_main_bookmarks.html ucp_main_drafts.html ucp_main_front.html ucp_main_subscribed.html ucp_pm_history.html ucp_pm_message_footer.html ucp_pm_message_header.html ucp_pm_options.html ucp_pm_popup.html ucp_pm_viewfolder.html ucp_pm_viewmessage.html ucp_pm_viewmessage_print.html ucp_prefs_personal.html ucp_prefs_post.html ucp_prefs_view.html ucp_profile_avatar.html ucp_profile_profile_info.html ucp_profile_reg_details.html ucp_profile_signature.html ucp_register.html ucp_remind.html ucp_resend.html ucp_zebra_foes.html ucp_zebra_friends.html viewforum_body.html viewonline_body.html viewonline_whois.html viewtopic_body.html viewtopic_print.html [B]EOF[/B] [B]mkdir tema[/B] [B]for i in `cat lista` ; do wget http://phpbb.ro/styles/Tharsis/template/$i -O tema/$i ; done [/B] Imi aduc aminte ca au mai fost threaduri de gen: "Cum sa furi la cantar la carrefour, cum sa furi haine din magazine", asta acum e cum sa furi teme. Ce cacat bre, toata treaba e pe furaciune acum ?

In legatura cu pastrarea de loguri. Chiar daca nu se face packet sniffing, toti pastreaza MINIM urmatoarele date: - Data de conectare - Adresa IP remote Si toti ofera aceste informatii autoritatilor in caz de probleme. Voi ce ati face ? Ati renunta la business si v-ati pune pielea-n batz pentru un ratat ce va plateste 5 euro ? Cititi si pe aici cate ceva: http://en.wikipedia.org/wiki/Telecommunications_data_retention Singura tara din Europa in care legea nu te obliga sa pastrezi date este Germania.

Eu lucrez cam tot ce se mananca cu linux. Am lucrat la cateva companii apoi am ajuns la concluzia ca nu renteaza in domeniul asta sa lucrezi pentru altcineva. Daca esti bun si stii sa-ti vinzi munca, este totul ok. Anul asta prin iunie fac 18 ani decand ma joc prin linux. Au fost perioade in care uitam de tot si stateam chiar si 4 zile nedormit pentru a reusi sa fac ceva. Multe multumiri celui care a inventat sfanta cafea. Skills: - TCP/IP, firewalls, network design, DNS, security - Linux & FreeBSD - Security policy & hardening (Linux & FreeBSD) - Antispam Solutions - High end web servers. (dual strat, clusters, content caching & high speed delivery) - Internet Support & Management - DDoS Protection, Advanced DDoS mitigation techniques - Databases (mysql & postgresql) - ................ Si oarece business management pentru ca degeaba ai produse bune daca nu stii sa le vinzi.

Ba nene. Cand vrei sa fi ajutat poti da mai multe detalii. Nu trebuie sa muncim noi sa scoatem informatiile pentru a te ajuta. Exemplu: - Am un VPS la x furnizor de servicii. - VPS-ul ruleaza Linux Debian/Fedora/Ubuntu ... sau ce distributie ruleaza el acolo. - Am instalat pe el postfix/qmail/sendmail/exim si am testat sa vad daca ruleaza (se observa procesul la ps aux, portul 25 este open, s.a.m.d) - Vreau sa instalez X aplicatie web cu ajutorul careia sa trimit newslettere sau vreau sa trimit email-uri din CLI cu oarece scripturi php.

Pai daca nici cu sursa in fata nu te pricepi, mergi frate si uita-te la TV pe Antena 1

What is HTCondor? HTCondor is a specialized workload management system for compute-intensive jobs. Like other full-featured batch systems, HTCondor provides a job queueing mechanism, scheduling policy, priority scheme, resource monitoring, and resource management. Users submit their serial or parallel jobs to HTCondor, HTCondor places them into a queue, chooses when and where to run the jobs based upon a policy, carefully monitors their progress, and ultimately informs the user upon completion. While providing functionality similar to that of a more traditional batch queueing system, HTCondor's novel architecture allows it to succeed in areas where traditional scheduling systems fail. HTCondor can be used to manage a cluster of dedicated compute nodes (such as a "Beowulf" cluster). In addition, unique mechanisms enable HTCondor to effectively harness wasted CPU power from otherwise idle desktop workstations. For instance, HTCondor can be configured to only use desktop machines where the keyboard and mouse are idle. Should HTCondor detect that a machine is no longer available (such as a key press detected), in many circumstances HTCondor is able to transparently produce a checkpoint and migrate a job to a different machine which would otherwise be idle. HTCondor does not require a shared file system across machines - if no shared file system is available, HTCondor can transfer the job's data files on behalf of the user, or HTCondor may be able to transparently redirect all the job's I/O requests back to the submit machine. As a result, HTCondor can be used to seamlessly combine all of an organization's computational power into one resource. The ClassAd mechanism in HTCondor provides an extremely flexible and expressive framework for matching resource requests (jobs) with resource offers (machines). Jobs can easily state both job requirements and job preferences. Likewise, machines can specify requirements and preferences about the jobs they are willing to run. These requirements and preferences can be described in powerful expressions, resulting in HTCondor's adaptation to nearly any desired policy. HTCondor can be used to build Grid-style computing environments that cross administrative boundaries. HTCondor's "flocking" technology allows multiple HTCondor compute installations to work together. HTCondor incorporates many of the emerging Grid and Cloud-based computing methodologies and protocols. For instance, HTCondor-G is fully interoperable with resources managed by Globus. HTCondor is the product of years of research by the Center for High Throughput Computing in the Department of Computer Sciences at the University of Wisconsin-Madison (UW-Madison), and it was first installed as a production system in the UW-Madison Department of Computer Sciences over 15 years ago. This HTCondor installation has since served as a major source of computing cycles to UW-Madison faculty and students. Additional HTCondor installations have been established over the years across our campus and the world. Hundreds of organizations in industry, government, and academia have used HTCondor to establish compute installations ranging in size from a handful to many thousands of workstations. The HTCondor software, source code, and complete documentation are freely available under an open source license. Linux, MacOS, and Windows platforms are supported. Website: HTCondor - Home Read the fucking manual: HTCondor - HTCondor Manuals