Hi, Cateva impresii si poze de la FOSDEM din acest an (6-7 Februarie). Tabara *BSD a fost prezenta cu un track separat in care au predominat sesiunile legate de FreeBSD. http://daemonscorner.blogspot.com/2010/02/fosdem-2010.html http://www.fosdem.org/2010/schedule/rooms/aw1.126 Toate cele bune, Adrian Penisoara. ________________________________________________________ To unsubscribe send a mail to rofug+unsubscribe@...
Hi, Acum ca tot a iesit oficial 8.0 [*], am o curiozitate: s-a jucat cineva cu FreeBSD in Xen-DomU ? Any tips ? Ati intalnit probleme majore cu 8.0 (prerelease sau release) pina acum ? [*] http://www.freebsd.org/releases/8.0R/announce.html http://www.rofug.ro/article.php/fbsd_8.0_released Regards, Adrian. ________________________________________________________ To unsubscribe send a mail to rofug+unsubscribe@...
Salutare,
Am o problema cu un sistem FAMP care functioneaza cu Apache 2.2 + mod_fcgi si foloseste APC pentru cache opcode PHP. Isi creeaza mai multe semafoare care am impresia ca raman deschise in memorie pe o perioada nelimitata. Nu am folosit semafoare in programare, deci nu stiu sigur cum ar trebui sa le tratez, dar presupun ca ar trebui sa se inchida la un moment dat din aplicatie. In cazul de fata raman deschise mult dupa ce scriptul folosit a fost interpretat - ex. sunt semafoare care imi arata ca au fost create in urma cu mai bine de 10 minute.
Stiti vreo metoda prin care pot pune un timeout pe semafoare? Eu am gasit momentan o solutie mai putin eleganta. Am marit numarul de semafoare la 1000 ca sa nu mai apara erori de tipul 500 si am facut un script care verifica rezultatul de la `ipcs -as` si sterge cu ipcrm semafoarele care sunt deschise de mai mult de 5 minute.
--
Message made from 100% recycled electrons.
http://www.lamp.ro
http://www.regex.ro
http://www.nethelp.ro
Salut, Bucuresti Linux Users Group organizeaza pe data de 12 decembrie 2009 conferinta BLUG*OS*CON. Daca un utilizator experimentat de FreeBSD doreste sa tina o prezentare la sectiunea pentru avansati, il rog sa ma contacteze cu detalii. M-as bucura foarte mult sa avem si FreeBSD in program. Programul (inca nedefinitivat) al conferintei il gasiti la: http://blug.ro/noutati/blugoscon-call-for-papers/ Alte informatii despre conferinta: http://blug.ro/blugoscon/ Multumesc, -Dan Serban (dserban01 => gmail) ________________________________________________________ To unsubscribe send a mail to rofug+unsubscribe@...
Hi,
Pentru cei interesati, poze de la conferinta si dimprejurul
Cambridge-ului -- bonus niscaiva slide-uri de la prezentari.
http://daemonscorner.blogspot.com/2009/09/photos-from-eurobsdcon-2009.html
Regards,
Adrian
________________________________________________________
To unsubscribe send a mail to rofug+unsubscribe@...
Salutare,
Am o mica problema cu placa de retea. O ia razna din cand in cand iar in /var/log/messages apar urmatoarele linii:
Sep 22 11:19:20 lamp kernel: xl0: transmission error: 90
Sep 22 11:19:20 lamp kernel: xl0: tx underrun, increasing tx start threshold to 180 bytes
Sep 22 11:20:37 lamp kernel: xl0: transmission error: 90
Sep 22 11:20:37 lamp kernel: xl0: tx underrun, increasing tx start threshold to 240 bytes
Sep 22 11:39:19 lamp kernel: xl0: transmission error: 90
Sep 22 11:39:19 lamp kernel: xl0: tx underrun, increasing tx start threshold to 300 bytes
Sep 22 12:37:45 lamp kernel: pid 5059 (httpd), uid 80: exited on signal 11
Sep 22 15:24:54 lamp kernel: pid 8024 (httpd), uid 80: exited on signal 11
Presupun ca problema e la placa de retea si ar trebui schimbata. Am de gand sa schimb serverul in vreo doua saptamani, dar pana atunci as vrea sa linistesc putin situatia. De fiecare data cand apar mesajele astea cad majoritatea serviciilor - Apache, SSH, Pure-FTPD. Aveti vreo idee de "carpeala" care sa imi rezolve caderile pana atunci?
--
Message made from 100% recycled electrons.
http://www.lamp.ro
http://www.regex.ro
http://www.nethelp.ro
Hi, Impresii din ultima zi la EuroBSDCon: http://daemonscorner.blogspot.com/2009/09/eurobsdcon-2009-is-over.html Anul viitor se va tine in Octombrie in Karlsruhe, Germania (din nou, dupa 5 ani)... Regards, Adrian. ________________________________________________________ To unsubscribe send a mail to rofug+unsubscribe@...
Hi, Pe scurt, prima zi la EnterpriseBSDCon: http://daemonscorner.blogspot.com/2009/09/full-first-day-at-eurobsdcon-2009.html Regards, Adrian. ________________________________________________________ To unsubscribe send a mail to rofug+unsubscribe@...
Buna, Ma gandeam sa mai fac o versiune rofreesbie. Intrucat acum e la moda sa fie facute update-uri la pachete ma gandeam sa compilez zilnic pachetele modificate din porturi iar cine vrea sa le copieze si instaleze cu un package manager grafic sau chiar din consola. Problema care va apare consta ca tot facand update la pachete nu vor mai fi satisfacute dependentele. Pentru a rezolva problema asta sunt mai multe posibiltati: 1) Folosire portupgrade cu baza de date externa pkgdb pentru a fi rezolvate dependentele. Cu timpul baza de date devine corupta si un user normal nu are rabdare sa dea fix. 2) Folosire unelte standard porturile...... si recompilarea tuturor pachetelor ( metoda nu prea avantajoasa deoarece necesita prea mult timp la ce harb de computer am eu) 3) Folosire alt program indicat de voi 4) Recompilarea doar a pachetelor noi cat se poate de des si reimpachetarea vechilor programe care folosesc pachetul updatat pentru a folosi versiunea acestuia. Eu am folosit metoda 1 , 2 si lucrez la teste pentru 4. Cateva idei/presupuneri legate de metoda 4: 1) Daca se face update zilnic nu cred ca vor apare diferente majore intre versiunile dependentelor si sper ca programele vor putea lucra. Teoretic ar trebui ca progrmele ce depind de pachetul updatat sa se comporte ca si cand ar fi fost updatate cu portupdate. 2) Probabil ca dupa reimpachetare ar putea fi folosit un nfs server pentru a instala pachetele. 3) Teoretic daca reimpachetez programele care depind de portul updatat ar trebui sa mearga si o instalare/reinstalare pe curat ( fara complainuri nu gasesc ... ) a pachetelor din consola. Ce program recomandati la punctul 3? Ce parere aveti de metoda 4 ? Va multumesc ________________________________________________________ To unsubscribe send a mail to rofug+unsubscribe@...
Hi,
Salut,
Poti incerca sa verifici permanent conexiunea cu LCP echo messages.
Parametrii sunt in pagina de manual de la pppd:
Salut Pana la urma am aplcat varianta asta si vad ca merge enable lqr echo set lqrperiod 7 Problema e ca lqrperiod e de fapt 7*5 adica 35 de secunde (la 35 de secunde imi inchide procesul). Am lasat asa deocamdata cu 10 useri de test. Nu stiu insa cum se va comporta daca ii mai bag inca vreo 200 de useri pe gat. Cu siguranta ca va trimite mesaje echo intr-una. Nu stiu in ce masura imi va afecta asta incarcarea (procesor/banda). ce-i drept man-ul de la ppp l-am frunzarit destul de superficial dar am sa dau atentie si sugestiilor tale. O zi buna in continuare. On Monday 24 August 2009 12:42:39 Ciprian BADESCU wrote: > Salut, > > Poti incerca sa verifici permanent conexiunea cu LCP echo messages. > Parametrii sunt in pagina de manual de la pppd: > > lcp-echo-failure n > If this option is given, pppd will presume the peer to be > dead if n LCP echo-requests are sent without receiving a valid LCP > echo-reply. If this happens, pppd will terminate the connec- tion. Use > of this option requires a non-zero value for the lcp- echo-interval > parameter. This option can be used to enable pppd to terminate after > the physical connection has been broken (e.g., the modem has hung up) in > situations where no hardware modem control lines are available. > > lcp-echo-interval n > If this option is given, pppd will send an LCP > echo-request frame to the peer every n seconds. Normally the peer > should respond to the echo-request by sending an echo-reply. This > option can be used with the lcp-echo-failure option to detect that the > peer is no longer connected. > > Spor, > Ciprian > > 2009/8/13 Tarabuta Radu <radu.tarabuta@...>: > > Salut la toata lumea: > > N-a mers combinatia asta. > > Aveam activat lqr dar nu era setata perioada la 10 sec. > > Am dat toata lumea afara si m-am conectat cu un singur calculator. > > Daca ma deconectez normal totul e ok. > > Daca insa scot cablul de retea din spate si incerc sa me deconectez din > > nou imi apare aceeasi eroare (am pus o bucata mai mare de log) iar > > procesul cu pid-ul 16565 imi sta bine mersi fara sa-l inchida cineva. > > > > Mai aveti vreo varianta castigatoare? > > O zi faina la toata lumea. > > > > # ps ax | grep ppp > > 16558 ?? Ss 0:00.01 /usr/libexec/pppoed -d -P /var/run/pppoed.pid > > -a serverPPPoE -l default -p * em1 > > 16565 ?? Ss 0:00.03 /usr/sbin/ppp -direct default > > 16624 p1 RL+ 0:00.00 grep ppp > > 37615 p7 I+ 0:00.12 tail -f /var/log/ppp.log > > > > > > > > Aug 13 09:47:28 master ppp[16569]: Phase: deflink: Created in closed > > state Aug 13 09:47:28 master ppp[16569]: Command: default: enable chap > > Aug 13 09:47:28 master ppp[16569]: Command: default: enable proxy Aug 13 > > 09:47:28 master ppp[16569]: Command: default: disable ipv6cp Aug 13 > > 09:47:28 master ppp[16569]: Command: default: set mru 1492 Aug 13 > > 09:47:28 master ppp[16569]: Command: default: set mtu 1492 Aug 13 > > 09:47:28 master ppp[16569]: Command: default: set ifaddr 86.127.56.0/24 > > 86.127.56.1-86.127.56.250 > > Aug 13 09:47:28 master ppp[16569]: Command: default: set speed sync > > Aug 13 09:47:28 master ppp[16569]: Command: default: set timeout 0 > > Aug 13 09:47:28 master ppp[16569]: Command: default: set dns 82.79.225.1 > > 82.79.225.2 > > Aug 13 09:47:28 master ppp[16569]: Command: default: enable lqr > > Aug 13 09:47:28 master ppp[16569]: Command: default: set lqrperiod 10 > > Aug 13 09:47:28 master ppp[16569]: Command: default: accept dns > > Aug 13 09:47:28 master ppp[16569]: Command: default: set > > radius /etc/ppp/radius.conf > > Aug 13 09:47:28 master ppp[16569]: Command: default: set log Chat Command > > Phase > > Aug 13 09:47:28 master ppp[16569]: Command: default: enable chap > > Aug 13 09:47:28 master ppp[16569]: Command: default: enable proxy > > Aug 13 09:47:28 master ppp[16569]: Command: default: disable ipv6cp > > Aug 13 09:47:28 master ppp[16569]: Command: default: set mru 1492 > > Aug 13 09:47:28 master ppp[16569]: Command: default: set mtu 1492 > > Aug 13 09:47:28 master ppp[16569]: Command: default: set ifaddr > > 86.127.56.0/24 86.127.56.1-86.127.56.250 > > Aug 13 09:47:28 master ppp[16569]: Command: default: set speed sync > > Aug 13 09:47:28 master ppp[16569]: Command: default: set timeout 0 > > Aug 13 09:47:28 master ppp[16569]: Command: default: set dns > > 213.164.255.21 83.103.150.21 > > Aug 13 09:47:28 master ppp[16569]: Command: default: enable lqr > > Aug 13 09:47:28 master ppp[16569]: Command: default: set lqrperiod 10 > > Aug 13 09:47:28 master ppp[16569]: Command: default: accept dns > > Aug 13 09:47:28 master ppp[16569]: Command: default: set > > radius /etc/ppp/radius.conf > > Aug 13 09:47:28 master ppp[16569]: Phase: PPP Started (direct mode). > > Aug 13 09:47:28 master ppp[16569]: Phase: bundle: Establish > > Aug 13 09:47:28 master ppp[16569]: Phase: deflink: closed -> opening > > Aug 13 09:47:28 master ppp[16569]: Phase: deflink: Link is a netgraph > > node Aug 13 09:47:28 master ppp[16569]: Phase: deflink: Connected! > > Aug 13 09:47:28 master ppp[16569]: Phase: deflink: opening -> carrier > > Aug 13 09:47:28 master ppp[16569]: Phase: deflink: carrier -> lcp > > Aug 13 09:47:28 master ppp[16569]: Phase: bundle: Authenticate > > Aug 13 09:47:28 master ppp[16569]: Phase: deflink: his = none, mine = > > CHAP 0x05 > > Aug 13 09:47:28 master ppp[16569]: Phase: Chap Output: CHALLENGE > > Aug 13 09:47:28 master ppp[16569]: Phase: Chap Input: RESPONSE (16 bytes > > from alexei) > > Aug 13 09:47:28 master ppp[16569]: Phase: Radius: Request sent > > > > Aug 13 09:47:28 master ppp[16569]: Phase: Radius(auth): ACCEPT received > > Aug 13 09:47:28 master ppp[16569]: Phase: IP 86.127.52.2 > > Aug 13 09:47:28 master ppp[16569]: Phase: Netmask 255.255.255.0 > > Aug 13 09:47:28 master ppp[16569]: Phase: MTU 1500 > > Aug 13 09:47:28 master ppp[16569]: Phase: VJ enabled > > Aug 13 09:47:28 master ppp[16569]: Phase: Chap Output: SUCCESS > > > > Si acu din nou aceeasi problema: > > ================================================ > > > > Aug 13 09:47:28 master ppp[16569]: Warning: iface add: ioctl(SIOCAIFADDR, > > 86.127.52.0 -> 86.127.52.2): File exists > > Aug 13 09:47:28 master ppp[16569]: Phase: deflink: lcp -> open > > Aug 13 09:47:28 master ppp[16569]: Phase: bundle: Network > > Aug 13 09:47:28 master ppp[16569]: Warning: iface add: ioctl(SIOCAIFADDR, > > 86.127.52.0 -> 86.127.52.2): File exists > > Aug 13 09:47:28 master ppp[16569]: Error: ipcp_InterfaceUp: unable to set > > ip address > > > > On Monday 10 August 2009 20:58:31 Adrian Penisoara wrote: > >> Hi, > >> > >> 2009/8/10 Tarabuta Radu <radu.tarabuta@...> > >> > >> > Salut la toata lumea. > >> > NU prea obisnuiesc sa pun intrebari pe rofug ca ma descurc singur in > >> > general > >> > dar acu cred ca imi scapa ceva. > >> > > >> > Vreau sa fac un server de pppoe cu raddius. > >> > > >> > Am adaugat in kernel > >> > options NETGRAPH > >> > options NETGRAPH_PPPOE > >> > options NETGRAPH_ETHER > >> > > >> > ppp.conf l-am pus mai jos. > >> > > >> > Totul e fain si frumos. merge ok, insa la fiecare conexiune ma trezesc > >> > ca-mi > >> > deschide un proces. Evident cand dau acolo un ps am sute de procese de > >> > la fiecare conexiune in parte. > >> > > >> > Problema n-ar fi asa mare dar in momentul cand cineva scoate mufa de > >> > la placa > >> > de retea, o baga din nou si vrea sa se conecteze nu mai poate. > >> > > >> > In loguri imi da urmatorul mesaj: > >> > Warning: iface add: ioctl(SIOCAIFADDR, 86.127.52.0 -> 86.127.52.100): > >> > File exists. > >> > Cu siguranta ca el nu-mi inchide procesul conexiunii respective. > >> > Evident dupa ce ii inchid procesul clientul reuseste sa se conecteze. > >> > > >> > Cum as putea sa fac toata treaba din kernel (sa nu-mi mai deschida > >> > procesele > >> > alea externe) si sa nu mai am problema cu ip-urile. > >> > >> Din cate tin minte flow-ul PPPoE este ca procesul pppoed asculta in > >> promiscous direct pe interfata Ethernet si pentru fiecare request client > >> deschide cate un proces (user) ppp. Nu cred ca exista scheme alternative > >> pentru asa ceva si ma indoiesc ca merge sa cuplezi pppd (kernel PPP). > >> > >> Ca sa poti determina procesele PPP ele insele sa recunoasca starea > >> deconectata ar trebui sa activezi LQR (Link Quality Req) pentru a > >> monitoriza starea conexiunii. Ceva de genul: > >> > >> enable lqr > >> set lqrperiod 10 > >> > >> Eu am pe partea client un PPPoE si folosesc cu succes setarea asta. > >> Eventual pui o valoare cat mai mica pentru lqrperiod (in sec.). > >> > >> Sa ne spui si noua ce rezultate/solutie obtii. > >> > >> Regards, > >> Adrian. > > > > -- > > Tarabuta Radu > > > > > > UPC Romania PL Suceava > > Str. Petru Rares Nr 19 > > Suceava > > > > T +40 330 100 301 > > M +40 745 386 444 > > www.upc.ro > > > > Chiar ai nevoie sa printezi acest email? Padurile noastre sunt in > > pericol... > > > > ________________________________________________________ > > To unsubscribe send a mail to rofug+unsubscribe@... > > ________________________________________________________ > To unsubscribe send a mail to rofug+unsubscribe@... -- -- Tarabuta Radu Senior Network Administrator UPC Romania PL Suceava Str. Petru Rares Nr 19 Suceava T +40 330 100 301 M +40 745 386 444 www.upc.ro Chiar ai nevoie sa printezi acest email? Padurile noastre sunt in pericol... ________________________________________________________ To unsubscribe send a mail to rofug+unsubscribe@...
 |
|
|
|
|
|
|
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 7 | 8 | 9 | 10 | 11 | 12 | 13 |
| 14 | 15 | 16 | 17 | 18 | 19 | 20 |
| 21 | 22 | 23 | 24 | 25 | 26 | 27 |
| 28 | 29 | 30 | 31 |
RSS Feed1 | |
|---|---|
1 | |
1 | |
14 | |
13 | |
22 | |
5 | |
11 | |
13 | |
21 | |
25 | |
6 | |
19 | |
7 | |
8 | |
7 | |
15 | |
45 | |
29 | |
12 | |
9 | |
2 | |
1 | |
6 | |
12 | |
48 | |
35 | |
31 | |
9 | |
13 | |
15 | |
56 | |
41 | |
39 | |
57 | |
47 | |
60 | |
122 | |
106 | |
52 | |
22 | |
78 | |
213 | |
111 | |
169 | |
194 | |
99 | |
62 | |
93 | |
79 | |
146 | |
81 | |
154 | |
102 | |
69 | |
23 | |
112 | |
162 | |
166 | |
164 | |
19 |