In this example find files modified between 15 December 2012 and 16 December 2012, in /var directory:
touch --date "2012-12-15" /tmp/start
touch --date "2012-12-16" /tmp/end
find /var -type f -newer /tmp/start -not -newer /tmp/end
touch --date "2012-12-15" /tmp/start
touch --date "2012-12-16" /tmp/end
find /var -type f -newer /tmp/start -not -newer /tmp/end
# echo "86400" > /var/qmail/control/queuelifetime
# /etc/init.d/qmail restart
http://localhost:8080/solr/update?stream.body=<delete><query>id:XXXXX</query></delete>&commit=true
http://localhost:8983/solr/update?stream.body=<delete><query>id:XXXXX</query><query>entitytype:YourContent</query></delete>&commit=true
<delete><query>*:*</query></delete>
Source: http://blog.dileno.com/archive/201106/delete-documents-from-solr-index-by-query/
PHP Parse error: syntax error,
unexpected T_NAMESPACE, expecting T_STRING
find
-name
"*.php"
-
exec
sed
-i
's/Namespace::/MWNamespace::/g'
{} \;
proxy = yourproxy.com:8080
<?php
//Connect String
$db="(DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS=(PROTOCOL=TCP)
(HOST=REMOTE_DB_IP)(PORT=XXXX)
)
)
(CONNECT_DATA=(SID=ORACLE_SID))
)";
//Connect to DB
$conn = oci_connect('USERNAME','PASSWORD',$db);
//Run a sample query
$s = oci_parse($conn, 'select * from DB_TABLE');
oci_execute($s);
oci_fetch_all($s, $res);
echo "<pre>\n";
var_dump($res);
echo "</pre>\n";
//Close DB Connection
oci_close($conn);
?>
VBoxManage modifyhd YOUR_HARD_DISK.vdi --resize SIZE_IN_MB
Example:
VBoxManage modifyhd MyWindows7.vdi --resize 20000
Start your guest machine and resize the partition with your suitable tool. (for example: Gparted for Linux or Windows Partition Manager for windows)
# man Mail::SpamAssassin::Conf
1
2
3
4
5
6
7
8
9
10
11
12
13
| -- -- Table structure for table `test1` -- ... DROP TABLE IF EXISTS `test1`; CREATE TABLE `test1` ( ... LOCK TABLES `test1` WRITE; INSERT INTO `test1` VALUES (1,0,’2 ... UNLOCK TABLES; ... –- –- Table structure for table `test2` –- |
your administration account! Create a new account with minimal rights.
So what is the username? Depends on your AD Layout. This should give you a pretty good hint
CN=YOUR-NAME,OU=IT Department,OU=Germany,DC=example,DC=com
here is your sample .htaccess:
# Using this to bind
AuthLDAPBindDN "CN=YOUR-USER,OU=IT Department,DC=example,DC=com"
AuthLDAPBindPassword "XXX"
# search user
AuthLDAPURL "ldap://IP-DOMAIN-CONTROLLER/ou=Germany,dc=example,dc=com?sAMAccountName?sub?(objectClass=*)"
AuthType Basic
AuthName "USE YOUR WINDOWS ACCOUNT"
AuthBasicProvider ldap
# Important, otherwise "(9)Bad file descriptor: Could not open password file: (null)"
AuthUserFile /dev/null
require valid-user
you always need to specify at least one organizational unit (ou).
PS.: If your users are split into multiple OU's, your are limiting the logons to OU's from one OU. This is the case im my environment where users are split into different regions. You should use another port (3268).
AuthType Basic
AuthBasicProvider ldap
AuthzLDAPAuthoritative Off
AuthName "whateveryouwant"
AuthLDAPURL "ldap://IP-DOMAIN-CONTROLLER:3268/dc=example,dc=com?sAMAccountName?sub?(objectClass=*)"
# Using this to bind
AuthLDAPBindDN "YOUR-USER@example.com"
AuthLDAPBindPassword "XXX"
require valid-user
When the data has been double-encoded, you will still have funny looking characters in the database.
Here is how to fix it, in two simple steps, using themysqldump
andmysql
commands:
Source Database:
mysqldump -h DB_HOST -u DB_USER -p DB_PASSWORD --opt --quote-names \
--skip-set-charset --default-character-set=latin1 DB_NAME > DB_NAME-dump.sql
Target Database: mysql -h DB_HOST -u DB_USER -p DB_PASSWORD \
--default-character-set=utf8 DB_NAME < DB_NAME-dump.sql