The solution is quite simple:
In wp-config.php
before require_once
add below code into file :
define('CONCATENATE_SCRIPTS', false);
The solution is quite simple:
In wp-config.php
before require_once
add below code into file :
define('CONCATENATE_SCRIPTS', false);
Vandaag met een AIX systeem aan de slag geweest. Zeker bij gebruik van Bash shell goed te vergelijken met Linux. Bij het uitpakken van enkele ZIP-bestanden liep ik al snel tegen de volgende melding aan:
/install/IM>unzip ../agent.installer.aix.gtk.ppc_1.8.1000.20141126_2002.zip -bash: unzip: command not found
Echter java is standaard geinstalleerd op een AIX machine, dus eenvoudig opgelost.
/install/IM>jar -xvf ../agent.installer.aix.gtk.ppc_1.8.1000.20141126_2002.zip
En uitpakken maar…
If you’ve ever wondered what is thrashing your hard drive but can’t figure out which process it is, you can use the iotop utility to help.
The iotop utility works the same as the top command that shows system process activity—just open up a terminal window and type iotop
to see a display of all processes and threads, and the amount of disk activity going on.
You can use the left and right arrow keys to change the sorting, and the R key to reverse the sort—but the really useful option is the O key, which changes the display to only show the threads with I/O activity. There’s a number of additional command-line switches that you can use, which you can read about by typing man iotop
at the terminal prompt.
Installing iotop on recent versions of Ubuntu or Debian is as simple as typing sudo apt-get install iotop
at a terminal prompt on RedHat or Centos it is yum install iotop
at the prompt—for other distributions you may have to install it manually.
Original source: Lifehacker
First of all you need to be on the most recent dashboard which is 16537. Use Google to find out how to upgrade. I used Flash360 to generate a NAND file. Got my CPU key by booting into Xelllaunch. Then I used Horizon to generate a new NAND file with the 16357 dash and my CPU key combined. After that Flash360 again to put the NAND on my XBOX.
Now for Call of Duty: Ghosts:
You probably already downloaded the two iso images of Ghosts. Next use exiso to extract them. Get it from this location: http://digiex.net/attachments/downloads/download-center-2-0/xbox-360-content/apps-pc/7467d1318226690-exiso-download-extracts-xgd3-images-exiso.zip
When extracted you now have to directories. Copy the first directory (eg. ghostsdisc1) to your games directory: hdd1:\\games
Now browse to the directory in which the second iso was extracted. Open the content directory and then the 0000000000 directory. You’ll see another dir in there with a code 415608FC. Copy this directory (CRTL-C)
Browse to hdd1:\\Content\00000000000 and paste the previously copied directory in there. After the copying has finished you a ready to go! Enjoy
Het blijkt dat de Digium X100P FXO kaarten die voor enkele honderden euros verkocht worden, feitelijk omgebouwde v92 faxmodems zijn.
Er zijn twee manieren om je oude V92 faxmodem te laten werken met bijvoorbeeld Asterisk:
– de driver aanpassen zodat je het modem kunt gebruiken als fxo kaart
– de kaart aanpassen zodat deze wordt herkend als officiële X100P kaart.
Het verschil zit ‘m in het “vendorID” dat de kaart heeft. De Digium kaarten hebben een andere vendor code en de software (driver) werkt alleen met die vendor code.
Onderstaande methoden werken overigens alleen met de volgende chipsets:
– Intel 537PG and 537PU
Let op!: 537EP is gebaseerd op de si3052 chip, deze is niet compatible met de tj320 chip (en wcfxo module).
– Ambient MD3200
– Motorola 62802 – soms is deze geplaatst op SM56 PCI modems.
Op een site als Marktplaats of eBay kun je het beste zoeken op “Intel Winmodem” of “fax modem”. Vraag de verkoper altijd om een foto van de chipset op de kaart om er zeker van te zijn dat je een van de juiste chipsets hebt.
Methode 1:
Wijzig de source code van zaptel/wcfxo.c:
static struct pci_device_id wcfxo_pci_tbl[] __devinitdata = {
{ 0xe159, 0×0001, 0×8085, PCI_ANY_ID, 0, 0, (unsigned long) &wcx101p },
{ 0×1057, 0×5608, PCI_ANY_ID, PCI_ANY_ID, 0, 0, (unsigned long) &wcx100$ };
in:
static struct pci_device_id wcfxo_pci_tbl[] __devinitdata = {
{ 0xe159, 0×0001, 0×8085, PCI_ANY_ID, 0, 0, (unsigned long) &wcx101p },
{ 0xe159, 0×0001, 0×8086, PCI_ANY_ID, 0, 0, (unsigned long) &wcx101p },
{ 0×1057, 0×5608, PCI_ANY_ID, PCI_ANY_ID, 0, 0, (unsigned long) &wcx100$ };
Na deze aanpassing werken zowel de officiële Digium X100p kaarten als een omgebouwde V92 Intel Winmodems.
Methode 2 (deze heb ik gebruikt):
Deze methode is dezelfde die Digium gebruikt om hun “echte” X100P kaarten te maken. Door het verwijderen van weerstanden R13 en R19 met een soldeerbout (let op! dit is SMD montage!!). Door het verwijderen van deze pull-down weerstanden wijzigt het vendorID dat van de kaart gelezen wordt. Door het verwijderen van de weerstanden heb je nu een kaart die als echte Digium X100p herkend wordt in Asterisk.
Om het geheel werkend te krijgen in Asterisk zet je de volgende code in/etc/zaptel.conf:
loadzone=nl
defaultzone=nl
; Use Kewlstart FXS signalling for the Wildcard X100P
fxsks=1
En in /etc/asterisk/zapata.conf:
[channels]
language=en
context=from-pstn
signalling=fxs_ks
channel => 1
Als de DAHDI driver geladen is kun je met het volgende commando de werking van de kaart testen:
dahdi_cfg -vv
De output is dan gelijk aan dit scherm:
Met het commando “lspci” kun je eventueel kijken of Linux je kaart wel herkend.
For the 2008 Server when it’s greyed out. To lift the password complexity:
secedit /export /cfg C:\new.cfg
Then you edit new.cfg (it is ini format) and change line “PasswordComplexity = 1″ to “PasswordComplexity = 0″.
Apply it on your Windows 2008 server with:
secedit /configure /db %windir%\security\new.sdb /cfg C:\new.cfg /areas SECURITYPOLICY
Changing Centos 5.9 32-bit to 64-bit (make sure your system is on 5.9 first!)
Download kernel-2.6.18-348.12.1.el5.x86_64.rpm from a Centos mirror and move it to /root on your server.
Install 64bit kernel:
rpm -Uhv --force --ignorearch kernel-2.6.18-348.12.1.el5.x86_64.rpm
Change boot order to new kernel:
vi /boot/etc/grub.conf
set default=0
reboot
Install package that contains yumdownloader:
yum install yum-utils
vi /etc/rpm/platform
replace i386-redhat-release with x86_64-redhat-release
rm -rf /var/cache/yum
Download 64-bit RPMs:
rpm -qa --queryformat '%{NAME}-%{VERSION}-%{RELEASE} %{ARCH}\n' | grep 86$ | sed 's/.\{4\}$//'| xargs yumdownloader
Explanation:
retrieve architecture information on all packages
select only i386 packages
remove ” i386″ from string
feed result into yumdownloader
rm -rf *.i686.rpm rm -rf *.i386.rpm rpm -iv --force *.rpm
reboot
Your system will be 64-bit now.
Disclaimer: This is very much unsupported! If you decide to do it, it is at your own risk!!
We use Centreon and Nagios for server monitoring. To check whether a WebSphere SOAP service is up and running you can use the following line:
./check_http -S -k ‘SOAPAction: ping’ -r ‘Current Status.*OK’ -T text/xml -P ” -t 10 -m 512 -p 9080 -H 10.20.30.1 -u /services/search/search.svc
HTTP OK HTTP/1.1 200 OK – 0.021 second response time |time=0.045343s;;;0.000000 size=903B;512;0;0
The best way is to download the IBMIM (IBM Installation Manger) separately, Once downloaded, you can manually set the following repositories to use with in IBMIM to download your version of WAS 8.
You can use Installation Manager on your local system to update WebSphere Application Server Version 8.0.0.0 with the interim fixes from the live web-based repositories at the following locations:
Application Client for IBM WebSphere Application Server:
http://www.ibm.com/software/repositorymanager/V8WASSupplements
Application Client for IBM WebSphere Application Server (ILAN):
http://www.ibm.com/software/repositorymanager/V8WASSupplementsILAN
DMZ Secure Proxy Server for IBM WebSphere Application Server:
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.NDDMZ.v80
IBM Web Enablement for IBM i
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.WEBENAB.v80
IBM WebSphere Application Server:
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.BASE.v80
IBM WebSphere Application Server – Express:
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.EXPRESS.v80
IBM WebSphere Application Server for Developers:
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.DEVELOPERS.v80
IBM WebSphere Application Server for Developers (ILAN):
http://www.ibm.com/software/repositorymanager/V8WASDeveloperILAN
IBM WebSphere Application Server Network Deployment:
http://www.ibm.com/software/repositorymanager/com.ibm.websphere.ND.v80
IBM WebSphere Application Server Network Deployment Trial:
http://www.ibm.com/software/repositorymanager/V8WASNDTrial
Web Server Plug-ins for IBM WebSphere Application Server:
http://www.ibm.com/software/repositorymanager/V8WASSupplements
Web Server Plug-ins for IBM WebSphere Application Server (ILAN):
http://www.ibm.com/software/repositorymanager/V8WASSupplementsILAN
From: http://www-01.ibm.com/support/docview.wss?uid=swg27021731
Today a problem with a customer running Domino 8.5.2 on AIX 6.1 where the SMTP listeren task gave the following error:
05/22/2012 01:09:57 AM ERROR: bindsock' helper application is missing, not executable, not setuid root, or no sticky bit set 05/22/2012 01:09:57 AM SMTP Server: Listener failure: 'bindsock' is missing, not executable, not owned by root, not setuid root or user needs net_privaddr privilege. 05/22/2012 01:09:57 AM Suspending listen task for 20 seconds due to network errors
The settings for bindsock were correct (see IBM technote: http://www-01.ibm.com/support/docview.wss?uid=swg21097534)
$ ls -l /opt/lotus/notes/latest/ibmpow/bindsock
-r-sr-xr-x 1 root bin 14488 Jan 10 20:45 bindsock
$
which is correct.
It appeared sendmail was still running causing a port conflict. The solution is to stop sendmail and prevent it from starting again.
To stop sendmail from starting on reboot, comment it out in the /etc/rc.tcpip file. Then do stopsrc -s sendmail to end the running copy.