DC-Users

dc-users@lists.duckcorp.org

1 participants
82 discussions

Frozen view of the present situation
by DuckCorp Admin Team 03 Sep '07

03 Sep '07

Coin, As announced, the last migration happened this we and few things were fixed today. This was quite a difficult task, and we had several extra problems... === The Mail === The mail routing with the new antispam software was a bit difficult to setup, so the mail was reopened sunday night. The software should have sent you a welcome with all important information about how to manage your custom antispam settings (or will do so when you receive your first mail on your new box). All previous mails were moved out of Orfeo, before it dies. Seem we are cursed, as the CPU or MB is not working properly anymore, and its future needs yet to be discussed. The box Finger provided to move the data had boot problems during the migration, and died a few hours later. The good news is : nothing is lost, everything was moved or is still available, as Orfeo's disks are alive. You should then find all your previous mails in your new box. The IMAPS/POP3S/Webmail/Webdesk access are still available and working. The automatic fetchmail process is also back since this afternoon. For the people still using direct mailbox access, it is right time to use maildirs for good now, as it is now the only delivery backend available now. The procmail rulez were translated to sieve, with only minor problems, are are working well, except for the ${n} regex replacements. We are working on this issue. A ManageSieve server is available using sieve.duckcorp.org, but it seems it is quite hard to make clients interoperate with our sieve implementation. Nevertheless, the Webdesk was reconfigure to use the sieve siltering rules ; it is working quite well, except for the "Show Active Script" action, which is not very important. The mailing-lists are working too, and are spam filtered since this afternoon. Special users are available for each virtual domain, so as to be able to setup custom antispam preferences, as any other mail user would. It may be possible to give per-list custom filtering access in the futur, but we do not believe this is a needed feature, so we won't work in this direction until user's requests say the contrary. === Shells === Only a few shell access were reopened. The new policy is not yet decided, but if you need back your access, we will consider reopening it gently. Thus, by asking explicit demands, we hope to close ununsed ressources. === Communication === Our Bitlbee server was migrated and upgraded, and is now available worldwide on the 6668 port as usual (on Ipv6 too). Ask us if you need an account. The new IRC Services are coming real soon now ; Nohar kindly prepared packages for us. So, i would surely have forgotten plenty of things, but it would be clearer when we get some sleep. Do not hesitate contacting us if you need assistance. -- Marc Dequènes (Duck)

1 0

Last Mass bombing. Ignition !!!
by DuckCorp Admin Team 29 Aug '07

29 Aug '07

Coin, The last big part of the migration is coming soon. Fasten your belt and pray god :-). === Mail === Friday evening, all your mailboxes are moving to the new server, and during the we all mail functions will follow. This is to say: you won't have any mail access during the we, starting from friday, in the middle of the afternoon. Incoming mails would then be stored on secondary MX servers. As soon as possible, mail delivery and IMAPS access are gonna be restored ; webmails and MLs access would follow. Then, send every important mail you need before Friday afternoon, stored messages you need to read using the offline mode of your mail client, and use an external email in case of emergency. Everything should be restored at the end of the we, but we cannot plan when exactly. For people using procmail rules, please help us convert your rules to a sieve script. === Web === Seems Everything went fine for the remaining sites. FTP access for modifying your site is work in progress and should be available soon. Shell accesses will be reexamined and reopened _later_ for people having real needs. Webstats are disabled for now ; we plan to reopen it, but this is not a first priority task. === Communication Services === Our new IRCd is behaving quite well. IRC Services should come soon, as a package is nearly ready, thanks to Nohar. The IRC Proxy, bip, is already working well since a few days, and logs available through the private part of the FTP server. Bitlbee is quite more of a problem to move, as a local access is currently necessary. Either we would give you back a shell account, either we would allow your IPs to connect to it. It should be moved during the we or in the following week. Our Jabber server is not moving yet, and perhaps not before Orfeo is back for real. Whatever, at least we plan to link it with our new database, so adding new account would be quite painless. This is gonna happen soon, during a night. We should be able to send a server-wide message to all users, or at least warn as many people as we can on IRC. === Homedirs and other data === For people having shell access, we are moving your homedirs in the same shot as mails. All shell accesses will be closed at least until the end of the we. Depending on your real needs, shell access may or may not be reopened ; this is still an open discussion between admins on how we should allow access to this service. Whatever, we won't leave you out with your data locked, but just thin about copying things you might need during the we. Missing FTP data are moving with mails and homedirs, and will be accessible quite quickly. === RCS === RCS data were moved, and we are working on giving you proper access to it. Arch (tla/baz) archives are already viewable throught archzoom, but this is all what is working at the moment. People whose shell access will be restored would be able to use it in read/write mode. This service may be interrupted while we need to make some tests, by making files unreachable, so this is not yet a reliable service. Ok, it should be enough for this time. Do not hesitate asking questions on #DuckCorp channel on IRC. Next checkup sunday or monday, by mail if everything went fine ;-). -- Marc Dequènes (Duck)

1 0

Checkup
by DuckCorp Admin Team 21 Aug '07

21 Aug '07

Coin, Sorry for not being talkative enough about the progress, but we were quite busy solving severals issues, and quite tired too. === Centralized Accounts === As we are now splitting services among multiple machines (in fact Elwing was also used to help Orfeo, but mostly for totaly separate services), the needed for account centralization was critical. Then we won't have to create accounts on all machines where each user needs services, and have to synchronize information (like passwords), as everything is gonna be spread automatically. This task is not fully complete : all accounts where created in the LDAP databse, but some information needs to be added for each reactivated service. This is partly why things are taking a bit longer than expected. === The Web === Webmail / Webdesk services were quickly put back only a few days ago, as a priority. And slowly other sites were switched on. As i said, many (lightweight) sites are now located on LeChat (RtpNet machine), so a database multi-master replication was necessary and a bit difficult to configure. Now this difficulty is over and we are switching on the other sites one by one. Don't worry about sql hostname modifications, either we are doing it for you, or we are contacting you for help. The web migration should be over in one or two days. == Databases == As said previously, MySQL is available on both Tōshirō and LeChat, meaning applications (not only websites) are easily relocatable to balance load. Recently a PostgreSQL database was installed on Tōshirō to provide access to a more serious database software. So you may ask for an account in a few days/weeks. No replication is planned yet, so applications outside Tōshirō won't be able to access the database yet. You may also ask for an LDAP database the same way. LDAP is being replicated on all MilkyPond hosts involded in user services. The phpMyAdmin tool is available again, with phpPgAdmin and phpLDAPadmin, on the following URL : https://db.duckcorp.org/ Beware experienced users ! The MilkyPond LDAP database is not yet ready for user access, as we are regenerating the content frequently. So any modification would be lost forever. Notice the sql.duckcorp.org DNS entry, and the corresponding website, are gonna disappear soon. More on new DNS hostnames later, they are still under discussion. == FTP storage == Both private and public data where moved from Orfeo, except for the HurdFr public data (which will be moved in the next data move). FTP profiles where activated, as it was on Orfeo. === Chat === A new IRCd software (with its services) are gonna be tested soon. Even without services ready, we would probably switch is everything is ok, so check your notices and reconnect if you find yourself alone in the channels. The (bip) IRC bouncer was moved to Tōshirō yesterday. Logs are available in the FTP storage. === Network === IPv6 is back online, with broker services. Our old broker IP range is now routed to Tōshirō, so you won't have to change your addresses and DNS entries, only the endpoint IPv4 address (using tb.duckcorp.org). Filtering rules have been strengthen a bit by the way. === Mail and homedirs === Another BIG move left, is moving mail to the new architecture. Fact is we were already working on improving the routing and processing capabilities, as well as anti-spamming methods, but we are now running short of time to have all this work together well. I won't talk about new features yet. But just give a word about the major change : the anti-spam system is being switched to the DSPAM software, which mean we would have to deal with plenty of spam until it is trained. The good news is : it should be much easier for users to manage and allow quite a lot of customizable features. It was also time to split our training database, to allow "per user" spam filtering, as we don't always agree on what is a spam or not. As soon as it is ready, we are planning a quick move, meaning you won't be able to access your mailbox during a short period of time. Incoming mails won't be lost, as they would be taken care of be our secondary MX. I just can advise you to watch your mails at least daily, or popup on IRC, to be informed when it is happening. We will surely target late night and/or we. Homedirs will be affected too, as we plan to move data at the same time. But this is not the only reason : Homedirs contains maildirs and sometimes mail routing configurations. We plan to : - replace procmail rules with sieve scripts - move fetchmail rules into the private section of the FTP storage and update the current script to use them, until a better solution is found If other changes/difficulties occur, we will inform you as soon as possible. For users having procmail rules, we would be very greatful if you could help us convert your rules to sieve. We don't want to deal with your personnal mailing stuff, and this could save us a lot of precious time. Sieve is a scripting langage for mail processing, with extended features compared to procmail capabilities. It is described here : http://en.wikipedia.org/wiki/Sieve_%28mail_filtering_language%29 The mail software we plan to use does not yet implement all the Sieve language ; it is able to understand the following features: - fileinto - reject - envelope - vacation - imapflags - notify - regex - subaddress - relational Do not hesitate to contact us if you have any problem. It is late and i may have dropped things through my strainer-memory, so i would complete this checkup in a futur post. Oyasumi nasai ! -- Marc Dequènes (Duck)

1 0

[DC-Admins] First Step towards back online
by DuckCorp Admin Team 13 Aug '07

13 Aug '07

Coin, === News === Tōshirō was prepared and successfully installed in its definitive location today, thanks to Yok, Nefou, and people from Hivane and Sivit. Moving critical services has started. Our NS and NTP have moved a few minutes ago. While this is transparent for NTP, you may have to do some changes in you zone settings (see the following chapter if you have such service). Mail and Web migrations are being prepared. Mails won't move until a few days, because a few architecture changes and improvements will take place, and because much testing is needed. You'll be warned when this is gonna happen. Web pages should be more easily configured on the new box, but because of the big amount of data, a solution needs to be found to avoid taking years with the ADSL upload limitations. So, please be patient. === NS Update === Tōshirō NS is available on two IPs: - ns1.duckcorp.org (replacing Orfeo) - ns2.duckcorp.org It then ensure a "piece of redundancy", for network failures only. You can ask for another NS (provided by Hivane) if you need full redundancy. When Orfeo is back in a datacenter, another NS would then be available. A) If you have a master zone hosted: A.1) for the master zone: /!\ It is no more possible to edit your zone via shell access. A new method would be available in the future, but this will have to wait after the situation is all back to normal. if you need any change, then ask us via mail or IRC. If your registrar is Gandi and you gave us technical rights on your zone, then everything was already made for you. Skip to B.2. If not, then you should add ns2.duckcorp.org to your NS list for better redundancy (in the registrar database only, the zone was already updated by DC admins). A.2) for the external slave zone(s): Please update the masters which are now : - 193.200.42.177 - 80.248.213.245 B) If you have a slave zone hosted: B.1) for the slave zone: There is nothing to do. B.2) for the external master zone: Please update the IP allowed for transfers with : - 193.200.42.177 - 80.248.213.245 Moreover, you should add ns2.duckcorp.org to your NS list for better redundancy (in the zone and in the registrar database). Beware ! For those who had the unwise idea to use this kind of configuration for their master zone: --- @ NS ns1.mydomain.tld. @ NS ns2.mydomain.tld. ns1.mydomain.tld. A 1.2.3.4 ns2.mydomain.tld. A 195.5.254.194 --- First, ns2.mydomain.tld. does not exists, then you'll have to change the server IP each time ns1.duckcorp.org moves. I agree this is a better name for your domain, but people reading this kind of technical information would soon understand you've got no real NS behind this name. Moreover, either you've added the corresponding glue record, and you are poluting important NS servers, either you didn't and you would surely experience strange behaviors or even your whole domain be unavailable. In either case, this is *WRONG*, correct it ! The right configuration is: --- @ NS ns1.mydomain.tld. @ NS ns1.duckcorp.org. @ NS ns2.duckcorp.org. ns1.mydomain.tld. A 1.2.3.4 --- === ... === If anything in this mail is unclear or if you need assitance for using our services while maintenance is in progress, ask us via mail or IRC. Stay tuned... -- Marc Dequènes (Duck) _______________________________________________ DC-Admins mailing list DC-Admins(a)lists.duckcorp.org https://lists.duckcorp.org/mailman/listinfo/dc-admins

1 0

The Road goes ever on and on...
by DuckCorp Admin Team 10 Aug '07

10 Aug '07

Coin, We are on the move. == The Plan == A new machine (Tōshirō), recently acquired, which was on the way to be installed for production, is going to be moved this very sunday into a datacenter. This was not the original plan, but we decided to haste things a bit, and happily found a hosting for it. Critical services are going to be "displaced" as fast as possible. A few others will be handled one by one during the following days, because a lot more configuration needs to be checked, and also lot's of data moved. == The First Step == As soon as general configuration and critical services are done, we are going to push the web online again. Then, for those still having access to their web content: please DO NOT modify or add anything starting from sunday, or it will probably be lost while we are copying data to the new server. == General Recommandations == Services may have unvolontary downtimes, please be patient. We are doing our best, but unexpected problems sometimes happen. Do not rely anymore on orfeo.duckcorp.org hostname, DO USE the proper service alias (smtp.duckcorp.org, imap.duckcorp.org, ...) or you will not be able to access services if they are moved to another machine. It should already be ok, as we advertised aliases quite a lot ; be warned we won't advertise any service relocation in the future if the admin team deem it necessary. If you don't know the proper alias to use, just ask us, via mail or IRC. Drink beer ! It helps forget problems, forgive bad people, and is a good social catalyst ;-). Stay tuned... -- Marc Dequènes (Duck)

1 0

Where we are, and where we go...
by DuckCorp Admin Team 09 Aug '07

09 Aug '07

Coin, = Where we are = This afternoon (2007-08-08T15:29:07), without any warning or delay, Nerim's boss decided to shutdown our main server, Orfeo. Thanks to Nerim's friends and Hivane[1], the box was recovered in the evening and our IPs routed to our HQ ADSL. Due to bandwidth limitations, it is no more possible to provide full services. Services unavailable : - Web (including chrooted SSH, Yoshi IRC Stats, and Wotomae) - FTP - Radio = Where we go = We are investigating possible relocation solutions. We currently believe it is a matter of days before a hosting solution is found. Moreover, a new machine was acquired recently. It is not yet ready for production, and the hosting infrastructure is still being worked on by our network sponsor Hivane[1], but it should be possible to improve services availability. More on this topic soon. = And what now ? = Now is time to go to bed, we are tired... [1] http://www.hivane.net/ -- Marc Dequènes (Duck)

1 0

Orfeo's crashes and News
by DuckCorp Admin Team 31 Jul '06

31 Jul '06

Coin, 1) Orfeo's crashes: A crash happened at 2006-06-29, due to an XFS Kernel bug [1]. This bug is currently unsolved and may cause further problems. The machine was restarted at 2006-07-14 before we loose control, a newer kernel was installed (with lot's of XFS fixes, but not the expected one) and /home repaired. Since now, things are working fine again, and we are following the issue closely. Due to another XFS bug [2] in the installed kernel, we'll have to update it again soon ; the exact date will be advertised on IRC. You should not have lost any data, but just in case you're into problems, we've got backups ; then do not hesitate to ask us if necessary. 2) PHP5 migration: As many applications are now switching to PHP5 only, it has been decided to switch to this new major version, as it is not possible to have both version 4 and 5 working at the same time. Around 2006-09-01, the switch will occur. Then you have a full month to check compatibility of your applications and modify your custom code accordingly. Packaged softwares will be handled by the Admin Team, so you should not have to care. 3) IPv6: Since yesterday, IPv6 connectivity is back. XS-26, our former provider, was slow to handle the switch to the new IP range (due to the complete removal of the experimental IP range 3ffe), and service quality was poor, so we were looking at other opportunities. Happily, Nerim made some upgrades recently, and native connectivity is now possible. Please inform us if you find any problem related to this change. Most services are IPv6 aware, and we are working at having them all work with Ipv6 properly. 4) Mail Filtering: Current issues are : - since a short while, our filtering system has been configured to use "defanging", meaning SPAMs not killed results in a mail report with the original Subject and From, and the problematic mail attached as a RFC 822 attachment. This gives a clearer result with more details, but it seems it is causing problems for mailboxes splitting, mostly because custom headers are not repeated in the report mail - filtering limits in the report differs from the custom field in the problematic mail attached, weird ! - filtering rules needs to be updated, because less SPAM is filtered since a few months, suggestions are welcome We are investigating and working on these issues. Thanks for your patience, and thank you for using <del>fre</del> DuckCorp ! ;-) [1] http://bugzilla.kernel.org/show_bug.cgi?id=5856 [2] http://oss.sgi.com/projects/xfs/faq.html#dir2 -- Marc Dequènes (Duck)

1 0

Mailing-lists problems and several changes
by DuckCorp Admin Team 13 Mar '06

13 Mar '06

Coin, Here are some news from the Pond. 1) Mailing-lists outage: A misconfiguration of our SMTP server was cause of mail subcription rejects. The applied fix was wrong and every mail between 2006-03-07 early in the morning and 2006-03-08 in the night were rejected (my bad !). This was worked out as soon as we realized what happened, and both problems are now fully solved. Apologies. 2) Backup: The new hard drive was installed in the backup server (whose hardware was upgraded in the same way). Old backups are safe, and new backups are now created. Total DC backups are now 67GB ; it was really time for upgrade ! Moreover, the old hard drive was installed on Elwing for private storage, but a check found it full of bad blocks ! 3) Security concerns about shell access: To avoid giving shell access to people having no real need for it, some adjustments were necessary to let you have the same level of service. a) Personnal web space: The personnal web spaces are now available through your FTP account into the 'www-perso-dc' directory. Ask for FTP access if you need. HurdFr users can access they personnal web spaces into the 'www-perso-hurdfr' directory the same exact way. The DC photo album upload space is in the same way accessible into the 'photos-perso-dc' directory. Please note this is only a convenient way to access ressources and a security improvement ; people having shell access may still manage their files with their account. For those who care about security, FTP is not less secure for 2 reasons: - first, catching the local password gives a relatively short range of priviledges, incomparable with having a shell account, whatever priviledges it may be granted. Look at SecurityFocus news to imagine how many local root exploits exists. - moreover, you can increase the security level by reading the next change below (Secure FTP). b) SQL administration: For those who fear about losing their shell access and be unable to manage their database, don't worry, a phpMyAdmin interface has been made public here: https://sql.duckcorp.org/ c) Shell access removal: The following users should contact us to look at their web space ACLs and dicuss about the needs that would not be fulfiled by the provided tools before their shell access is removed: - cedricburnay - js - marius - scop - valfor Note that a shell access may be reopened if necessary in the future ; this is not a punishment, but a security measure. 3) Secure FTP: You can now connect to our FTP server with a TLS-enabled client, this would secure your data transfers, and moreover, avoid any password disclosure, as the TLS mode is enabled before authentication. Don't forget to get the DC certificate here: https://www.duckcorp.org/dc/ca.crt and check the signature here: https://www.duckcorp.org/dc/ca.crt.asc (if you trust my key, of course) Free* tools supporting FTP+TLS: - on GNU/Linux and GNU/Hurd, the Netkit 'ftp-ssl' package - on Windows, FileZilla (http://filezilla.sourceforge.net/) - on Mac OS X, Cyberduck (http://cyberduck.ch/) * Free like in "free speech" see http://www.gnu.org/philosophy/free-sw.html (in french: http://www.gnu.org/philosophy/free-sw.fr.html) 4) Upgrades: a) mySQL: First, the database was cleaned, unuseful things were trashed, and a naming convention was established. If your name is Arnau, GuiHome, HurdFr or PikaPaf, then your DB users/db-names may have changed to match the convention ; don't worry, everything was renamed for you and your website is working as usual. Furthermore, the database was successfully upgraded from 4.1 to 5.0. Changelog says the most important new features are: - stored procedures - triggers - views - information schema - archive storage engine (for historical and audit data) If this software could stop crashing once and a while, it would be the best new feature ever dreamed of... By the way, don't forget to do some database management periodically to improve access to your data: - check if no indexes are missing - use ANALYSE to improve search capabilities - use OPTIMIZE to clean up unnecessary data phpMyAdmin can help you do this (with no more than 3 clicks ;-). b) BitlBee: BitlBee is an IM gateway through a nice IRC interface, you can only access it localy (if you have a shell account) at the moment, using port 6668 like you would do for any IRC server. The new 1.0.1 version was installed, fixing some nasty bugs (full changes here: http://bitlbee.org/main.php/changelog.html). The irssi scripts were upgraded too, allowing typing notification in the statusbar. You need to /reconnect to the server to benefit from these fixes. 5) Spam Learning system reminder (or not): To improve detection of spam and avoid false positives, 2 special mailboxes have been setup. You can send spams which where not detected to dc-ham(a)duckcorp.org and false positives (if not destroyed) to dc-ham(a)duckcorp.org to train the system and improve recognition. /!\ PLEASE TAKE CARE to use the "resend" function of your mailer and never use "forward", which would result in _yourself_ being considered as spam or ham /!\ This said, Have a Lot of Fun in the Pond ! -- Marc Dequènes (Duck)

1 0

Happy new year 2006 !
by DuckCorp Admin Team 17 Jan '06

17 Jan '06

Coin, First, wanted to wish you lot's of happiness for this new year :-) News follows: 1) Orfeo illness: On 2006-01-07 morning, Orfeo suffered from a major hard disk access problem, leading to most services being unusuable during most of the day. After some attempts to take back control, a move to the datacenter was scheduled. In the middle of the afternoon, Orfeo was up and ok again. Investigations revealed a bug in the XFS subsystem ; a bug is opened here: http://bugzilla.kernel.org/show_bug.cgi?id=5856 2) Short SPAM infestation: Due to a mistake i made on 2006-01-10 when upgrading amavid-new, the mailer system was working half a day without spam check. Sorry for the inconvenience. 3) Really available BW: Orfeo's bandwidth was meant to be 100Mbps in the new datacenter, but a configuration mistake in the network equipment prevented us from taking advantage of this nice upgrade. This was solved on 2006-01-16 morning. 4) Backup: Due to increase of important data to backup, it was obvious the current storage (60GB) was no more sufficient. Thanks to an anonymous donor, we have a brand new disk and can now store as much as 300GB. The old disk will move to Elwing, where the 8.4Go data hard disk was dead, providing space for services located on Elwing and private data storage. this is currently work in progress. May the CoinForce be with you this year ! -- Marc Dequènes (Duck)

1 0

This was a nice year...
by DuckCorp Admin Team 28 Dec '05

28 Dec '05

Coin, The year is (almost) over. We are happy services have worked quite well and hope you're happy with them. Feel free to report problems or leave comments. We wish you a Merry X-mas, nice meals and stuff :-) Here are the last news of the year: 1) Orfeo move: As you may have noticed, the move was a success. DC DNS zone was updated quickly and many services were back online quickly. No reboot was necessary and remaining services were working again during the night. All DNS zones should have been corrected now. Please remember to use CNAMEs for web vhosts instead of A records, to avoid delays for future changes. By the way, kernel was updated and PaX patch too, solving a w3m problem called "absurd stack bottom value". No other problems were reported, but similar behaviors with other programs should be solved too. 2) Web news: Certificates are now up to date now. Because we were not able to get an IP block, we are now using a wildcard certificate for each server, thus fixing browser complaints for all DC vhosts (but not for hosted projects' vhosts). Horde configuration was fixed (PHP configuration indeed), solving file uploads (so you can now import your keys to sign your mails in IMP for example). A PHP cache engine, with a good reputation (used to handle the scaring skyblogs), eAccelerator, was installed. This should improve latency a wee bit. Feel free to report / comment on it so we can decide if it is worth running it. A photo album dedicated to DC users and friends was setup here: http://photos.duckcorp.org/main.php Feel free to ask for an account. 3) Mail processing changes: We are now using the experimental amavisd-new package, as the unstable one was heavily outdated, fixing several problems, and allowing better stats and quarantine. The system now complains on bad headers without rejecting the mail completly, and is now storing intermediate scored mails depending on their badness (virus, bad header, spam, banned) during several days (final number would depend on available disk space). Do not hesitate contacting us if you suspect a good mail was trashed, quickly, so we can analyse the quarantine and changes settings if necessary. 4) Chat tools upgrade: Bitlbee 1.0 was out recently and fixed some issues (a security one, and several others ; even if no one in here reported problems). Most visible change is the channel renaming from #bitlbee to &bitlbee to avoid confusion with OFTC channel name. IRSSI 0.8.10 was out recently too and installed. If you are using it on Orfeo, please /UPGRADE now (to use the new binary without quitting). Many many leaks were fixed, and a recode engine is available, so pleaaaaaaaase don't use the so bad existing scripts anymore (/help recode). Beware some script may not behave correctly ; please report problems affecting system-installed scripts to us. 5) Memory problems: Recent memory problems are now solved. Services cleanup, tweaks, and fixes (mostly IRSSI leaks fixes) gave us back an acceptable amount of memory. This may improve services responsiveness (and thus jam PHP cache tests too). 6) FTP bandwidth limitations: As we are now on a bigger internet connection (100Mbps), rate limiting was removed, and should stay removed if it is not slowering other services. 7) DC standing against EUCD: As part of DC policy to react on important events, and after a vote of the board, DC officially stand against DADVSI (as you may have seen in the main news site). Useful links on the subject was given on the site, please read them for your own sake. -- Marc Dequènes (Duck)

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

DC-Users