|
Here is how to disable SELinux on CentOS 7. That shall also work on the corresponding RedHat systems. First of all check status of SELinux on your system:
~]$ sestatus To make the SELinux permissive immediately: ~]$ sudo setenforce Permissive To make SELinux permissive after reboot, edit /etc/sysconfig/selinux to get SELINUX=permissive To disable SELinux altogether, edit /etc/sysconfig/selinux to get SELINUX=disabled The changes in /etc/sysconfig/selinux will be in effect after sudo reboot |
|
If you need to try bunch of different things with JavaScript, fiddle with your script quickly, go to http://jsfiddle.net Example with picture overlays and image map by Jamie Treworgy |
|
There was a great presentation given by Jared Richardson from AgileArtisans. Author of Ship it! A Practical Guide to Successful Software Projects Highlights
Discuss - Study - Experiment - Learn -- steps shall be short. Timebox them. Measure iterations in weeks. Do ~3 experiments. Create feedback loops. Try out architecture, adopt skeleton prototypes. Start thin, as you can't get to something complex until you make something simple. 70% of software development work is rework. Communicate early! Developers and QA are better to discuss features *before* the developers invested time and soul into the code. To actually see the scope - Put things on the wall. Print or write. Sticky notes are good too. Interesting idea: Issue "cash points" to the team members for deliverables ready. The "ready" definition includes acceptance by QA. Do not giveout points to the developers until QA acceptance. Beginners need checklists and steps! Teach your colleagues! Work with the managers to allocate time for learning/teaching/knowledge exchange sessions. Attachments: Image 1 |
and 
. The slides are 
|
Had a find of the day, which seem to change my coding practice further on :-) That is Atom editor. Atom editor is free, hackable and extendable integrated software development environment (IDE). Integration with Git comes right out of the box. The number of plugins (packages) is quite remarkable, and it is growing. Many of these packages are duplicating each other, but that's expected, as the product is in its early "expansion" stage. I've been doing development with Eclipse before. Atom seems to be more suitable for quick tasks and in-place edits than Eclipse. It is faster than Eclipse, and it is easier to setup. To me, Atom looks like Notepad++, but better. So far Source Insight, was the best code editor I've seen, but Atom is newer and it comes Free, and I am sure it will have all the same features, but with better customization. |
|
If you are thrown at legacy C code and see "Invalid regular expression" from regexec -- don't rush to blame your regular expression. The root cause for the "Invalid regular expression" could be improper set of flags used with the regexec call. Synapsis You have a simple regex. regcomp does compile the regex just fine. But when you get to regexec - it fails with "Invalid regular expression", and the regexec call uses some flags like this: regexec(compiled_regex, subj_string, 0, NULL, REG_NOSUB | REG_ICASE); // the flags are WRONG!
Solution Get rid of improper flags. The only acceptable flags to the regexec are: REG_NOTBOL - Do not regard the beginning of the specified string as the beginning of a line; more generally, don’t make any assumptions about what text might precede it. REG_NOTEOL - Do not regard the end of the specified string as the end of a line; more generally, don’t make any assumptions about what text might follow it. REG_NOSUB, REG_ICASE or whatever else - are supposed to be used with regcomp For details see regex.h and/or Matching a Compiled POSIX Regular Expression. |
|
When attempting to use DBI with freetds from your Perl script you may see: [unixODBC] [Driver Manager] Data source name not found, and no default server specified (SQL-IM002) That error wording maybe misleading. It sounds like a DSN is missing or misspelled in /etc/odbc.ini, but in fact it also maybe Driver string having a non-exec/non-conforming parameter. DSNs from /etc/odbc.ini may rely on driver declarations from /etc/odbcinst.ini: For example, this piece from /etc/odbc.ini [dsn_example] ... Driver = SQL ..
[unixODBC] [Driver Manager] Data source name not found, and no default server specified (SQL-IM002)
To remedy the error you may either, [dsn_example] ... Driver = /usr/lib/libtdsodbc.so.0 .. If you need to debug more, see Troubleshooting ODBC connections. These 3 tools: tsql, isql, osql are indispensable. I did identify that Driver issue with the help of osql. |
|
via http://tripython.org/ meetings comes presentation http://people.apache.org/~trawick/TriPython-httpd.pdf on variety of ways to deploy Python web applications to httpd (Apache) and nginx. |