NickTheGreek

για το τελευταιο εχεις και delete from defers;

ok, αλλά με InnoDB ειναι μια άλλη ιστορία ...! http://www.tocker.ca/2013/05/02/optimize-check-repair-analyze-table-innodb-edition.html OPTIMIZE/CHECK/REPAIR/ANALYZE TABLE InnoDB Edition I find a good interview question for a MySQL DBA position is to ask what the following commands actually do in InnoDB, which has been the default storage engine since MySQL 5.5. From my perspective there is a lot of miss-understanding what still applies. ANALYZE TABLE From the MySQL manual: ANALYZE TABLE analyzes and stores the key distribution for a table. During the analysis, the table is locked with a read lock for InnoDB and MyISAM. What this means is, as part of query optimization MySQL will often have to decide which is the best index if there are multiple candidates, which indexes should be avoided, and what order should tables be joined in. Indexes need to eliminate work - so if for example you were trying to index a column called "Country" in a table full of all people in the USA, then it would be faster to avoid that index. What is also important to note, is that InnoDB will often update these statistics internally without you needing to do so, and that the 'read lock' that the manual describes is kind of weird (shameless plug for a bug I filed back in 2007). Up until 5.6, statistics are in memory only, and very coarse - sampling just a small amount of data. With 5.6, there is now the new Persistent Optimizer Statistics enhancement as well as innodb_stats_auto_recalc is also a variable, and STATS_PERSISTENT, STATS_AUTO_RECALC, and STATS_SAMPLE_PAGES are configurable per table as CREATE TABLE options. It's a shame features like this don't get enough press. I still find myself using ANALYZE TABLE as part of debugging slow queries to confirm that it is not a stale causing a problem, but I don't find any routine operational use case for it. Pro-tip: My explaination above with a "Country" table being filled with all "USA" was a bit of a simplification, since not all optimizer decisions will use these pre-computed statistics. I believe in many cases if we are just talking about a single table (and not trying to determine join order), the optimizer will just ask InnoDB to estimate how many records there are in a given range. I am hoping these sort of behaviors will be more exposed in future MySQL versions. I was very happy to see EXPLAIN for UPDATE and DELETE statements in MySQL 5.6 - and in some cases the new JSON EXPLAIN format seems to show more information. CHECK TABLE CHECK TABLE to me is a MyISAM-ism. As noted in the manual: If CHECK TABLE finds a problem for an InnoDB table, the server shuts down to prevent error propagation. Details of the error will be written to the error log. InnoDB is an ACID compliant (durable) data store, so it doesn't have the same inconsistency situations that MyISAM does. The behavior that the manual is describing here is the same behavior that happens if the server detects corruption through standard operation - which is detected via CRC checksums on each page it stores. As Oli writes check table probably won't work on very large tables (> 200-400 GB), so this command does not really have any practical use for me. REPAIR TABLE From the MySQL manual: REPAIR TABLE only applies to MyISAM, ARCHIVE, and CSV tables. See Section 14.3, "The MyISAM Storage Engine", and Section 14.6, "The ARCHIVE Storage Engine", and Section 14.5, "The CSV Storage Engine" So no use for this either. OPTIMIZE TABLE For InnoDB, the wording in the in the MySQL manual and the error message is very specific on this one: For InnoDB tables, OPTIMIZE TABLE is mapped to ALTER TABLE, which rebuilds the table to update index statistics and free unused space in the clustered index. Beginning with MySQL 5.1.27, this is displayed in the output of OPTIMIZE TABLE when you run it on an InnoDB table, as shown here: mysql> OPTIMIZE TABLE foo; +----------+----------+----------+-------------------------------------------------------------------+ | Table | Op | Msg_type | Msg_text | +----------+----------+----------+-------------------------------------------------------------------+ | test.foo | optimize | note | Table does not support optimize, doing recreate + analyze instead | | test.foo | optimize | status | OK | +----------+----------+----------+-------------------------------------------------------------------+ So what this means, is that internally we create a new table - much like the existing table, then we trickle load the data into it one row at a time. For the clustered index (aka primary key) this may result in a significant space saving if data was inserted out of order, or if there have been modifications which have caused there to be some gaps which have affected fill-factor. It's important to note while explaining this, that some gaps are expected - as InnoDB only fills pages 15/16ths full. For the secondary key indexes they will be trickle loaded one row at a time in the order of the clustered index - which may result in them going straight back to being fragmented anyway. InnoDB's implementation of MVCC does have multiple versions in the secondary indexes however, so it is possible that gaps may be reclaimed here. In MySQL 5.5, InnoDB introduced a feature called "fast index create" that could create these secondary indexes more optimally by presorting the data first and then creating the index. However, this feature is not tied into OPTIMIZE TABLE (yet) in official Oracle MySQL releases. See Bug #57583. Due to it's massively high cost, I find I run OPTIMIZE a lot less than other people (read: almost never), and Baron Schwartz has even has a humorous way of describing it: .. like something you'd hear from a naive Windows user who buys a $99 piece of software to make his PC "boot faster" or "fix his registry" or something.

αυτός ειναι ο Γιάννης που όλοι αγαπούν

παιδιά γνωρίζει κανείς πως το Forum Logo (PNG) θα μπορούσε να αναδομηθεί σε vector ? (PSD, AI) ? λογικά πρεπει να ξανασχεδιαστεί από την αρχή νομίζω

Apache 2 - HowTo - Tune Apache Requirements: You will need to have an understanding of how Apache functions and basic ability to with with BASH and edit configuration files. The load handling of the Apache service is controlled from the httpd.conf file. Most Linux Server will be under /etc/httpd/conf/httpd.conf however cPanel uses /usr/local/apache/conf/httpd.conf. The most common method is to use the Global Prefork options. # prefork MPM # StartServers: number of server processes to start # MinSpareServers: minimum number of server processes which are kept spare # MaxSpareServers: maximum number of server processes which are kept spare # ServerLimit: maximum value for MaxClients for the lifetime of the server # MaxClients: maximum number of server processes allowed to start # MaxRequestsPerChild: maximum number of requests a server process serves <IfModule prefork.c> StartServers 15 MinSpareServers 10 MaxSpareServers 40 ServerLimit 256 MaxClients 256 MaxRequestsPerChild 1000 </IfModule> Most of the time you only need to adjust the prefork.c and not worry about the worker.c section. Making adjustments to this is not an exact science as many different variables come into play such as how many sites are hosted, how much traffic is coming through, how many of the pages are static verses having sub functions, are MySQL calls being used, and so on. The first general rule is that you are trying to balance having as many open connections as possible verses the server load. The more connections that are open generates server load. The more server load, the slower the site will respond. However if there are not enough connections available then the site will not always respond to everyone. This is controled through the following: StartServers How many apache servers start in the very beginning. If this is set too low then it will take some time to catch up to the needed load when restarting the Apache service MinSpareServers How few servers will it go down to to save on RAM and CPU. If this is set too low then it will be slow to respond to sudden peaks in traffic MaxSpareServers Maximum number of servers. If set too low then there will not be enough open sockets for all requests and the site will appear down for some users. ServerLimit Must equal MaxSpareServers if MaxSpareServers is greater than 256 The second general rule is balancing the following two options. A large RAM based Apache configuration that allows many different connections with few instances, or many small RAM based Apache configuration that allows very few connections. The first option is better for a single or very few sites hosting a large database, where the second option is better for running a large number of different sites with little or no database involved. This is controlled through the following: MaxClients How many sessions a server can handle. A rule of thumb to make a good starting point is to set this to 150 times the number of Gigs of RAM on the server. MaxRequestsPerChild How often the service refreshes cached information and or restarts the server to accept new sessions. So if you are hosting a large database it is better to have a few servers with many clients, where as if you are hosting many different sites it is better to have many different servers with few clients. If you are running a cron job that changes the site dynamically then you want few requests per child so it does not cache the information for too long. After making changes you would then restart the Apache service. The following commands can be run to check the server load. Note that this should be run while there is peak traffic to the server for the most accurate reading. Apache 1 echo '##### Apache Load Check 1.2 ###########' ;\ echo '##### Written by Joe Ciancimino 2009 #####' watch \ "echo "CTRL+C TO EXIT" ;\ clear ;\ echo vmstat ;\ vmstat ;\ echo Load ;\ w ;\ echo Apache Processes ;\ ps -elf |grep 'http' |wc -l ;\ echo Active Apache Conections ;\ netstat -nalp |grep ':80 ' |grep 'ESTABLISHED'|wc -l ;\ echo Apache Conections ;\ netstat -nalp |grep ':80 ' |wc -l ;\ echo SYN Conections ;\ netstat -nalp |grep 'SYN' |wc -l ;\ echo IPCS ;\ ipcs |grep 0x0 |wc -l" ;\ echo '##### End Apache Load Check ##########' ;\ Apache 2 watch "/etc/rc.d/init.d/httpd status" While a lot of people may give you formulas to determine the settings based on RAM and CPU usage, the result would just be a baseline that still needs to be further tweaked. The main thing is to keep an eye on the load of the server during peak hours. Some say to keep the load around 1 per CPU, but you can usually push it as high as around 4 per CPU with out too much trouble if needed. It would not be considered optimal but rather "Red Lining" the server. If you watch what happens during the startup you may want to increase StartServers to around 30 and might even try pushing MaxSpareServers up to around 60. Any change then restart Apache and watch the load. If you don't have many sites and describe a lot of database usage, instead of pushing the MaxSpareServers up very high, you might try after that to push Max Clients as needed. The other thing you are looking for is in the netstat command is SYN connections. netstat -nalp | grep ':80 ' | grep SYN If you see a lot of SYN connections then you still need to increase MaxSpareServers Once you are satisfied with the performance from tuning the prefork, you may want to further secure Apache from some buffer overflow exploits. While this is described as security, it is actually simply a second layer to how Apache is tuned, so this too will effect the performance of the service. RLimitMEM softlimit hardlimit Limits how much RAM the httpd processes will take. Suggestion: Run the command 'free -l' and you should see some thing like: free -l total used free shared buffers cached Mem: 1034584 1015908 18676 0 201960 396040 Low: 903576 885152 18424 High: 131008 130756 252 -/+ buffers/cache: 417908 616676 Swap: 1052248 144 1052104 Take the larger of the two between the Low and High available memory for the first limit and put the Total Mem as the second limit. RLimitMEM 903576 1034584 RLimitCPU softlimit hardlimit Configure the maximum CPU time in seconds used by a process Suggestion: Run the command 'cat /proc/cpuinfo' to see how many core processors you have to work with. Use '50 * the number of processors' for the softlimit and '75 * the number of processors'for the hard limit. cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel® Xeon™ CPU 2.40GHz stepping : 7 cpu MHz : 2393.370 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr bogomips : 4788.04 processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel® Xeon™ CPU 2.40GHz stepping : 7 cpu MHz : 2393.370 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe cid xtpr bogomips : 4783.86 RLimitCPU 100 140 RLimitNPROC softlimit hardlimit Limits the number of subprocesses httpd can fork to at any one time such as CGI. Suggestion: Would suggest to take the 1/2 the number from the MaxSpareServers for the soft limit and match it for the hard limit. RLimitNPROC 10 20 So combined it would look some thing like: RLimitMEM 903576 1034584 RLimitCPU 100 140 RLimitNPROC 10 20 <IfModule prefork.c> StartServers 15 MinSpareServers 10 MaxSpareServers 40 ServerLimit 600 MaxClients 600 MaxRequestsPerChild 1000 HostnameLookups Off KeepAlive Off #KeepAliveTimeout 30 </IfModule> Source: https://sites.google.com/site/zenarstudio/home/kb/apache-2---howto---tune-apache

Apache by default logs data directly to log files. While this isn’t a bad thing, it is not your only option. Both Apache 1.x and Apache 2.x bring with them the option of enabling something called “Piped Logging”, though cPanel will only allow you to enable it for version 2.x. Piped logging is extremely powerful when used correctly, and has far more flexibility than what we are using here. The way it is described here, we will be attempting to negate the memory hungry apache processes that creep up when a server is hosting very low traffic websites (less than 1 request per second) with traditional Apache log configurations. The symptom: Apache processes using a lot of memory. You will see Apache using a large percent of the memory (MEM) when running a ‘top’, such as what you see below (when sorted by memory use) and you’ll also note that the root Apache process has been running for a long time: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 15733 root 15 0 554m 541m 5752 S 0.0 52.9 851:59.84 httpd 17790 www 15 0 556m 544m 5408 S 0.0 53.1 0:02.77 httpd 17616 www 16 0 555m 543m 5440 S 0.0 53.1 0:04.69 httpd 18368 www 15 0 555m 543m 5396 S 0.0 53.1 0:01.05 httpd 29924 www 16 0 555m 543m 5548 S 0.0 53.1 0:08.91 httpd 18363 www 15 0 555m 542m 5352 S 0.0 53.0 0:00.55 httpd 22294 www 15 0 554m 542m 5376 S 3.9 53.0 0:00.27 httpd 22093 www 15 0 555m 541m 4556 S 0.0 52.9 0:00.33 httpd 22232 www 15 0 554m 541m 4552 S 0.0 52.9 0:00.27 httpd To see if traditional logging is enabled, check your Apache error log for messages that show Apache being restarted around every 2 hours: [host - root]: grep Graceful /usr/local/apache/logs/error_log You will see something like this: [Mon May 31 14:29:55 2010] [notice] Graceful restart requested, doing restart [Mon May 31 16:43:37 2010] [notice] Graceful restart requested, doing restart [Mon May 31 18:57:19 2010] [notice] Graceful restart requested, doing restart [Mon May 31 21:11:02 2010] [notice] Graceful restart requested, doing restart The Fix! Enter Piped logging. Enabling piped logging in this way has a few different effects, but the one we are primarily concerned with is preventing Apache from initiating that graceful restart request every two hours. WARNING: By following these directions your Apache configuration is rebuilt from the existing cPanel templates (the last distilled configuration), so you will lose anything that was not added or configured through cPanel/WHM. The directions below explain how to make a backup of the configuration before rebuilding it. Pre-implementation: Note: You will need to have root access to the server in order to implement piped logging. Software Requirements: Cpanel Version: 11.25.0-R43471 or later Apache Version 2 or later You can check your versions with the following commands: cPanel: [host - root]: cat /usr/local/cpanel/version For Apache: [host - root]: /usr/local/apache/bin/httpd -v Implementation There are two possible ways to implement this fix, one is via the command line, the other is through the WHM. Method 1: All Command Line Make a backup of the Apache config: [host:root]: cp /usr/local/apache/conf/httpd.conf /usr/local/apache/conf/httpd.prepipedlogging Edit /var/cpanel/cpanel.config: [host:root]: vi /var/cpanel/cpanel.config Add the following enable_piped_logs=1 Make cPanel aware of the change: [host:root]: /usr/local/cpanel/whostmgr/bin/whostmgr2 --updatetweaksettings Rebuild the Apache config: [host:root]: /scripts/rebuildhttpdconf Stop and Start Apache: /etc/init.d/httpd stop /etc/init.d/httpd start Method 2: Allow cPanel/WHM to do the hard parts Make a backup of the Apache config: [host:root]: cp /usr/local/apache/conf/httpd.conf /usr/local/apache/conf/httpd.prepipedlogging Log into WHM, and follow this sequence to the right place: Service Configuration >> Apache Configuration >> Piped Log Configuration Enable piped Apache logging, save it and let it rebuild the configuration. Finishing up After making any changes that involve your Apache configuration it is a very good idea to test all your hosted sites to make sure they still work. If it’s not practical to check all of your sites check as many different sites as you can. You should see a difference in your memory use and your service stability nearly immediately, and it should be long term.

Question: I'm using Exim mail server under CentOS Linux. How do I remove all messages from the Exim mail queue using a shell prompt? Answer: Exim is a mail transfer agent (MTA) used on Unix-like operating systems. It aims to be a general and flexible mailer with extensive facilities for checking incoming e-mail. To print a list of the messages in the queue, enter: # exim -bp To remove a message from the queue, enter: # exim -Mrm {message-id} To remove all messages from the queue, enter: # exim -bp | awk '/^ *[0-9]+[mhd]/{print "exim -Mrm " $3}' | bash Dallas Marlow, suggested following clean command: # exim -bp | exiqgrep -i | xargs exim -Mrm

ωρα να αναβαθμιστούμε, ισως λυθει και το μονο θεμα σε εκκρεμότητα σήμερα ...

μια χαρά, και με αυτά τα aliases κανω δουλειά πάντως ## get top process eating memory alias psmem='ps auxf | sort -nr -k 4' alias psmem10='ps auxf | sort -nr -k 4 | head -10' ## get top process eating cpu ## alias pscpu='ps auxf | sort -nr -k 3' alias pscpu10='ps auxf | sort -nr -k 3 | head -10'

Σημείωση εδώ: ούτε σε FB ούτε σε LinkedIn ζητήθηκε validation, μονο Twitter

ναί, και μαλιστα εχει λυθει και ένα ακόμη, δεν ζητάει email validation. Πριν λιγο με την παλαιότερη από twitter ζήτησε κανονικα. Απλά περιμένω να πάμε προς μεσάνυχτα για να κανω το upgrade ( forum offline, backup etc etc )

παιδιά, όποιος ενδιαφέρεται ένα PM για να τον εντάξουμε στην αντίστοιχη κατηγορία

Παιδεύτηκα με αυτο και ηταν απλά ένα typo ...! Προσπαθώντας να συνδέσω το Login με το twitter API ( οδηγίες : https://invisionpower.com/4guides/how-to-use-ips-community-suite/social-sign-in/twitter-r238/ ) και βλεπω αυτο ενώ όλα είναι σωστά: εψαξα λιγο παραπάνω και διαβάζω εδω: https://webflake.sx/topic/20349-how-to-setup-twitter/ Κατέβασα και το προτεινόμενο αρχείο system/login/twitter.php και είπα να τα συγκρίνω με αυτό που έχουμε:

Our privacy policy describes how we use and store the data that we gather from you in order to provide our products and services. Our Commitment To Privacy Your privacy is important to us. To better protect your privacy we provide this notice explaining our online information practices and the choices you can make about the way your information is collected and used. To make this notice easy to find, we make it available on our homepage and at every point where personally identifiable information may be requested. The Information We Collect This notice applies to all information collected or submitted on any of the ForumsAndMore websites. On some pages, you can order products, make requests, and register to receive materials. The types of personal information collected at these pages are: Name Address Email address Phone number Credit/Debit Card Information The Way We Use Information We use the information you provide about yourself when placing an order only to complete that order. We do not share this information with outside parties except to the extent necessary to complete that order. We use return email addresses to answer the email we receive. Such addresses are not used for any other purpose and are not shared with outside parties. You can register with our website if you would like to receive our services as well as updates on our new products and services. Information you submit on our website will not be used for this purpose unless you fill out the registration form. We use non-identifying and aggregate information to better design our website and to share with advertisers. For example, we may tell an advertiser that X number of individuals visited a certain area on our website, or that Y number of men and Z number of women filled out our registration form, but we would not disclose anything that could be used to identify those individuals. Finally, we never use or share the personally identifiable information provided to us online in ways unrelated to the ones described above without also providing you an opportunity to opt-out or otherwise prohibit such unrelated uses. Our Commitment to Data Security To prevent unauthorized access, maintain data accuracy, and ensure the correct use of information, we have put in place appropriate physical, electronic, and managerial procedures to safeguard and secure the information we collect online. Our Commitment to Children's Privacy Protecting the privacy of the very young is especially important. For that reason, we never collect or maintain information at our website from those we actually know are under 13, and no part of our website is structured to attract anyone under 13. How You Can Access Or Correct Your Information You can access all your personally identifiable information that we collect online and maintain by emailing our privacy department or otherwise contacting our company. We use this procedure to better safeguard your information. You can correct factual errors in your personally identifiable information by sending us a request that credibly shows error. To protect your privacy and security, we will also take reasonable steps to verify your identity before granting access or making corrections. Spam Monitoring Service The IPS Spam Monitoring Service collects data from those sites using IPS software that choose to participate in the service. The email address and IP address of the registering member is passed to the service to determine the likelihood a registering account is a spam source. Data from accounts determined not to be spammers are permanently deleted within 48 hours. Data from accounts determined to be spammers may be stored indefinitely to create a block list. How To Contact Us Should you have other questions or concerns about these privacy policies, please use the contact form in the forum footer or email us at info [ a t ] designhost.gr

Version 4.1.18 of the IPS Community Suite is now available. In addition to bug fixes and performance improvements, this release also includes: Pinterest share link has been added Converters are now included as a Suite-level application you can download with your package in the Client Area Running a conversion will now skip steps that do not have anything to convert Two Factor Authentication Images embedded in the editor can now have an alternative title set for accessibility Users signing in through social services, such as Facebook, will no longer be required to validate their email address When a location is specified for a Calendar Event, the address will be shown underneath the map. The map itself should also be more accurate now. The Approval Queue page now has a "Hide" button to hide content (rather than only being able to approve / delete) Disabling Profile Photo uploads will now also disable importing from a URL An issue has been fixed where adding tags using other languages may not work properly Cropping Animated GIF's for photos is now supported when ImageMagick is in use Files purchased in Downloads will now have a link back to the file from their purchase page in the Manage Purchases section The Admin CP will now indicate whether or not a member is connected to a social network The Admin CP will now display more information for a user who has been banned imgur embedded is now supported Errors caused by third party applications / plugins will now be clearer Option to report fatal errors automatically to IPS so we can fix common issues

πρέπει να το δοκιμάσω το παρακάτω, δείχνει καλύτερο ίσως cat /dev/null > /root/mailaccounts.txt CP_ACCOUNTS=`ls -1A /var/cpanel/users/` for user in `echo -n $CP_ACCOUNTS` do /root/mailaccounts.txt domain=`grep -i ^dns /var/cpanel/users/$user |cut -d= -f2` for dom in `echo -n "$domain"` do PASSWD_FILE="/home/$user/etc/$dom/passwd" if [ -f $PASSWD_FILE ] && [ -s $PASSWD_FILE ] then for mail in `cat $PASSWD_FILE| cut -d":" -f1` do echo "$mail@$dom" >> mailaccounts.txt done fi done done https://www.nixpal.com/cpanel-count-and-list-all-mailboxes/

Βλεπω το RV042 εχει web interface αλλα γενικα με Cisco Πολλες φορες πρεπει να κατεβεις στο IOS για να κανεις δουλεια

Εξαρτάται κυρίως από το σύνολο τον aggregated γραμμών σε bandwidth Δηλαδη για 2 VDSL ακόμα και 50Mbps γιατι να ειναι Bottlenech το 100Mbit LAN ? εκτός και κατάλαβα κάτι λάθος