Friday, September 11, 2009

Optimize all your mysql databases automatically

SkyHi @ Friday, September 11, 2009
// description of your code here
Use this script preferably with a cronjob to automatically optimize all the tables in your mysql databases. Under root privilleges the script will search for all the databases in your server and will optimize them all. Hope you will like it as it took me more than 3 hours to write it


echo '
' . "\n\n";

set_time_limit( 100 );

$time = microtime();
$time = explode(' ', $time);
$time = $time[1] + $time[0];
$start = $time;

//Connection variables :
$h = 'localhost';
$u = 'root';
$p = 'password';

$dummy_db = 'mysql';//The php->mysql API needs to connect to a database even when executing scripts like this. If you got an error from this(permissions), just replace this with the name of your database

$db_link = mysql_connect($h,$u,$p);

$res = mysql_db_query($dummy_db, 'SHOW DATABASES', $db_link) or die('Could not connect: ' . mysql_error());
echo 'Found '. mysql_num_rows( $res ) . ' databases' . "\n";
$dbs = array();
while ( $rec = mysql_fetch_array($res) )
{
$dbs [] = $rec [0];
}

foreach ( $dbs as $db_name )
{
echo "Database : $db_name \n\n";
$res = mysql_db_query($dummy_db, "SHOW TABLE STATUS FROM `" . $db_name . "`", $db_link) or die('Query : ' . mysql_error());
$to_optimize = array();
while ( $rec = mysql_fetch_array($res) )
{
if ( $rec['Data_free'] > 0 )
{
$to_optimize [] = $rec['Name'];
echo $rec['Name'] . ' needs optimization' . "\n";
}
}
if ( count ( $to_optimize ) > 0 )
{
foreach ( $to_optimize as $tbl )
{
mysql_db_query($db_name, "OPTIMIZE TABLE `" . $tbl ."`", $db_link );
}
}
}

$time = microtime();
$time = explode(' ', $time);
$time = $time[1] + $time[0];
$finish = $time;
$total_time = round(($finish - $start), 6);
echo 'Parsed in ' . $total_time . ' secs' . "\n\n";
?>



Reference: http://snippets.dzone.com/posts/show/2526

Optimizing Apache, PHP and MySQL

SkyHi @ Friday, September 11, 2009
Reference: http://blog.fedecarg.com/2007/06/22/optimizing-apache-and-php/

Sendmail Anti-Spam Configuration Control

SkyHi @ Friday, September 11, 2009
Anti-Spam Configuration Control

1. Overview
2. relay_* Features
3. Access Database
4. Fine Control In The Access Database
5. Delay All Checks
6. Header Checks

Overview
The primary anti-spam features available in sendmail are:

* Relaying is denied by default.
* Better checking on sender information.
* Access database.
* Header checks.

Relaying (transmission of messages from a site outside your host (class {w}) to another site except yours) is denied by default. Note that this changed in sendmail 8.9; previous versions allowed relaying by default. If you really want to revert to the old behaviour, you will need to use FEATURE(`promiscuous_relay'). You can allow certain domains to relay through your server by adding their domain name or IP address to class {R} using RELAY_DOMAIN() and RELAY_DOMAIN_FILE() or via the Access Database. Note that IPv6 addresses must be prefaced with "IPv6:". The file consists (like any other file based class) of entries listed on separate lines, e.g.,
sendmail.org
128.32
IPv6:2002:c0a8:02c7
IPv6:2002:c0a8:51d2::23f4
host.mydomain.com
[UNIX:localhost]

Notice: the last entry allows relaying for connections via a UNIX socket to the MTA/MSP. This might be necessary if your configuration doesn't allow relaying by other means in that case, e.g., by having localhost.$m in class {R} (make sure $m is not just a top level domain).
relay_* Features

If you use
FEATURE(`relay_entire_domain')

then any host in any of your local domains (that is, class {m}) will be relayed (that is, you will accept mail either to or from any host in your domain).

You can also allow relaying based on the MX records of the host portion of an incoming recipient address by using
FEATURE(`relay_based_on_MX')

For example, if your server receives a recipient of user@domain.com and domain.com lists your server in its MX records, the mail will be accepted for relay to domain.com. This feature may cause problems if MX lookups for the recipient domain are slow or time out. In that case, mail will be temporarily rejected. It is usually better to maintain a list of hosts/domains for which the server acts as relay. Note also that this feature will stop spammers from using your host to relay spam but it will not stop outsiders from using your server as a relay for their site (that is, they set up an MX record pointing to your mail server, and you will relay mail addressed to them without any prior arrangement). Along the same lines,
FEATURE(`relay_local_from')

will allow relaying if the sender specifies a return path (i.e. MAIL FROM: ) domain which is a local domain.

This is a dangerous feature as it will allow spammers to spam using your mail server by simply specifying a return address of user@your.domain.com. It should not be used unless absolutely necessary.

A slightly better solution is
FEATURE(`relay_mail_from')

which allows relaying if the mail sender is listed as RELAY in the access map. If an optional argument `domain' (this is the literal word `domain', not a placeholder) is given, the domain portion of the mail sender is also checked to allowing relaying. This option only works together with the tag From: for the LHS of the access map entries (see below: Finer control).

This feature allows spammers to abuse your mail server by specifying a return address that you enabled in your access file. This may be harder to figure out for spammers, but it should not be used unless necessary.

Instead use SMTP AUTH or STARTTLS to allow relaying for roaming users.

If source routing is used in the recipient address (e.g., RCPT TO: ), sendmail will check user@site.com for relaying if othersite.com is an allowed relay host in either class {R}, class {m} if FEATURE(`relay_entire_domain') is used, or the access database if FEATURE(`access_db') is used. To prevent the address from being stripped down, use:
FEATURE(`loose_relay_check')

If you think you need to use this feature, you probably do not. This should only be used for sites which have no control over the addresses that they provide a gateway for. Use this FEATURE with caution as it can allow spammers to relay through your server if not setup properly.

NOTICE: It is possible to relay mail through a system which the anti-relay rules do not prevent:
the case of a system that does use FEATURE(`nouucp', `nospecial') (system A) and relays local messages to a mail hub (e.g., via LOCAL_RELAY or LUSER_RELAY) (system B). If system B doesn't use FEATURE(`nouucp') at all, addresses of the form would be relayed to .
System A doesn't recognize `!' as an address separator and therefore forwards it to the mail hub which in turns relays it because it came from a trusted local host. So if a mailserver allows UUCP (bang-format) addresses, all systems from which it allows relaying should do the same or reject those addresses.

As of 8.9, sendmail will refuse mail if the MAIL FROM: parameter has an unresolvable domain (i.e., one that DNS, your local name service, or special case rules in ruleset 3 cannot locate). This also applies to addresses that use domain literals, e.g., , if the IP address can't be mapped to a host name. If you want to continue to accept such domains, e.g., because you are inside a firewall that has only a limited view of the Internet host name space (note that you will not be able to return mail to them unless you have some "smart host" forwarder), use
FEATURE(`accept_unresolvable_domains')

Alternatively, you can allow specific addresses by adding them to the access map, e.g.,

From:unresolvable.domain OK
From:[1.2.3.4] OK
From:[1.2.4] OK

Notice: domains which are temporarily unresolvable are (temporarily) rejected with a 451 reply code. If those domains should be accepted (which is discouraged) then you can use
LOCAL_CONFIG
C{ResOk}TEMP

sendmail will also refuse mail if the MAIL FROM: parameter is not fully qualified (i.e., contains a domain as well as a user). If you want to continue to accept such senders, use
FEATURE(`accept_unqualified_senders')

Setting the DaemonPortOptions modifier 'u' overrides the default behavior, i.e., unqualified addresses are accepted even without this FEATURE. If this FEATURE is not used, the DaemonPortOptions modifier 'f' can be used to enforce fully qualified domain names.
Access Database

An ``access'' database can be created to accept or reject mail from selected domains. For example, you may choose to reject all mail originating from known spammers. To enable such a database, use
FEATURE(`access_db')

Notice: the access database is applied to the envelope addresses and the connection information, not to the header.

The FEATURE macro can accept as second parameter the key file definition for the database; for example
FEATURE(`access_db', `hash -T /etc/mail/access_map')

Notice: If a second argument is specified it must contain the option `-T' as shown above. The optional third and fourth parameters may be `skip' or `lookupdotdomain'. The former enables SKIP as value part (see below), the latter is another way to enable the feature of the same name.

Remember, since /etc/mail/access is a database, after creating the text file as described below, you must use makemap to create the database map. For example:
makemap hash /etc/mail/access < /etc/mail/access

The table itself uses e-mail addresses, domain names, and network numbers as keys. Note that IPv6 addresses must be prefaced with "IPv6:". For example,

spammer@aol.com REJECT
cyberspammer.com REJECT
TLD REJECT
192.168.212 REJECT
IPv6:2002:c0a8:02c7 RELAY
IPv6:2002:c0a8:51d2::23f4 REJECT

would refuse mail from spammer@aol.com, any user from cyberspammer.com (or any host within the cyberspammer.com domain), any host in the entire top level domain TLD, 192.168.212.* network, and the IPv6 address 2002:c0a8:51d2::23f4. It would allow relay for the IPv6 network 2002:c0a8:02c7::/48.

The value part of the map can contain:
OK Accept mail even if other rules in the running ruleset would reject it, for example, if the domain name is unresolvable. "Accept" does not mean "relay", but at most acceptance for local recipients. That is, OK allows less than RELAY.
RELAY Accept mail addressed to the indicated domain or received from the indicated domain for relaying through your SMTP server. RELAY also serves as an implicit OK for the other checks.
REJECT Reject the sender or recipient with a general purpose message.
DISCARD Discard the message completely using the $#discard mailer. If it is used in check_compat, it affects only the designated recipient, not the whole message as it does in all other cases. This should only be used if really necessary.
SKIP This can only be used for host/domain names and IP addresses/nets. It will abort the current search for this entry without accepting or rejecting it but causing the default action.
### any text where ### is an RFC 821 compliant error code and "any text" is a message to return for the command. The string should be quoted to avoid surprises, e.g., sendmail may remove spaces otherwise. This type is deprecated, use one the two ERROR: entries below instead.
ERROR:### any text as above, but useful to mark error messages as such.
ERROR:D.S.N:### any text where D.S.N is an RFC 1893 compliant error code and the rest as above.

For example:

cyberspammer.com ERROR:"550 We don't accept mail from spammers"
okay.cyberspammer.com OK
sendmail.org RELAY
128.32 RELAY
IPv6:1:2:3:4:5:6:7 RELAY
[127.0.0.3] OK
[IPv6:1:2:3:4:5:6:7:8] OK

would accept mail from okay.cyberspammer.com, but would reject mail from all other hosts at cyberspammer.com with the indicated message. It would allow relaying mail from and to any hosts in the sendmail.org domain, and allow relaying from the 128.32.*.* network and the IPv6 1:2:3:4:5:6:7:* network. The latter two entries are for checks against ${client_name} if the IP address doesn't resolve to a hostname (or is considered as "may be forged"). That is, using square brackets means these are host names, not network numbers.

Warning: if you change the RFC 821 compliant error code from the default value of 550, then you should probably also change the RFC 1893 compliant error code to match it.

For example, if you use
user@example.com ERROR:450 mailbox full

the error returned would be "450 5.0.0 mailbox full" which is wrong. Use "ERROR:4.2.2:450 mailbox full" instead.

Note, UUCP users may need to add hostname.UUCP to the access database or class {R}.

If you also use:
FEATURE(`relay_hosts_only')

then the above example will allow relaying for sendmail.org, but not hosts within the sendmail.org domain. Note that this will also require hosts listed in class {R} to be fully qualified host names.

You can also use the access database to block sender addresses based on the username portion of the address. For example:
FREE.STEALTH.MAILER@ ERROR:550 Spam not accepted

Note that you must include the @ after the username to signify that this database entry is for checking only the username portion of the sender address.

If you use:
FEATURE(`blacklist_recipients')

then you can add entries to the map for local users, hosts in your domains, or addresses in your domain which should not receive mail:

badlocaluser@ ERROR:550 Mailbox disabled for this username
host.mydomain.com ERROR:550 That host does not accept mail
user@otherhost.mydomain.com ERROR:550 Mailbox disabled for this recipient

This would prevent a recipient of badlocaluser@mydomain.com, any user at host.mydomain.com, and the single address user@otherhost.mydomain.com from receiving mail.

Please note: a local username must be now tagged with an @ (this is consistent with the check of the sender address, and hence it is possible to distinguish between hostnames and usernames). Enabling this feature will keep you from sending mails to all addresses that have an error message or REJECT as value part in the access map. Taking the example from above:

spammer@aol.com REJECT
cyberspammer.com REJECT

Mail can't be sent to spammer@aol.com or anyone at cyberspammer.com.

There are several DNS based blacklists, the first of which was the RBL (``Realtime Blackhole List'') run by the MAPS project, see http://mail-abuse.org/. These are databases of spammers maintained in DNS. To use such a database, specify
FEATURE(`dnsbl')

This will cause sendmail to reject mail from any site in the original Realtime Blackhole List database. This default DNS blacklist, blackholes.mail-abuse.org, is a service offered by the Mail Abuse Prevention System (MAPS). As of July 31, 2001, MAPS is a subscription service, so using that network address won't work if you haven't subscribed. Contact MAPS to subscribe (http://mail-abuse.org/).

You can specify an alternative RBL server to check by specifying an argument to the FEATURE. The default error message is
Rejected: IP-ADDRESS listed at SERVER

where IP-ADDRESS and SERVER are replaced by the appropriate information. A second argument can be used to specify a different text. By default, temporary lookup failures are ignored and hence cause the connection not to be rejected by the DNS based rejection list. This behavior can be changed by specifying a third argument, which must be either `t' or a full error message. For example:
FEATURE(`dnsbl', `dnsbl.example.com', `', `"451 Temporary lookup failure for " $&{client_addr} " in dnsbl.example.com"')

If `t' is used, the error message is:
451 Temporary lookup failure of IP-ADDRESS at SERVER

where IP-ADDRESS and SERVER are replaced by the appropriate information.

This FEATURE can be included several times to query different DNS based rejection lists, e.g., the MAPS Dial-Up User List (DUL).

Notice: to avoid checking your own local domains against those blacklists, use the access_db feature and add:

Connect:10.1 OK
Connect:127.0.0.1 RELAY

to the access map, where 10.1 is your local network. You may want to use "RELAY" instead of "OK" to allow also relaying instead of just disabling the DNS lookups in the backlists.

The features described above make use of the check_relay, check_mail, and check_rcpt rulesets. Note that check_relay checks the SMTP client hostname and IP address when the connection is made to your server. It does not check if a mail message is being relayed to another server. That check is done in check_rcpt. If you wish to include your own checks, you can put your checks in the rulesets Local_check_relay, Local_check_mail, and Local_check_rcpt. For example if you wanted to block senders with all numeric usernames (i.e. 2312343@bigisp.com), you would use Local_check_mail and the regex map:

LOCAL_CONFIG
Kallnumbers regex -a@MATCH ^[0-9]+$

LOCAL_RULESETS
SLocal_check_mail
# check address against various regex checks
R$* $: $>Parse0 $>3 $1
R$+ < @ bigisp.com. > $* $: $(allnumbers $1 $)
R@MATCH $#error $: 553 Header Error

These rules are called with the original arguments of the corresponding check_* ruleset. If the local ruleset returns $#OK, no further checking is done by the features described above and the mail is accepted. If the local ruleset resolves to a mailer (such as $#error or $#discard), the appropriate action is taken. Otherwise, the results of the local rewriting are ignored.

Finer control by using tags for the LHS of the access map

Read this section only if the options listed so far are not sufficient for your purposes. There is now the option to tag entries in the access map according to their type. Three tags are available:

Connect: connection information (${client_addr}, ${client_name})
From: envelope sender
To: envelope recipient

If the required item is looked up in a map, it will be tried first with the corresponding tag in front, then (as fallback to enable backward compatibility) without any tag, unless the specific feature requires a tag. For example,

From:spammer@some.dom REJECT
To:friend.domain RELAY
Connect:friend.domain OK
Connect:from.domain RELAY
From:good@another.dom OK
From:another.dom REJECT

This would deny mails from spammer@some.dom but you could still send mail to that address even if FEATURE(`blacklist_recipients') is enabled. Your system will allow relaying to friend.domain, but not from it (unless enabled by other means). Connections from that domain will be allowed even if it ends up in one of the DNS based rejection lists. Relaying is enabled from from.domain but not to it (since relaying is based on the connection information for outgoing relaying, the tag Connect: must be used; for incoming relaying, which is based on the recipient address, To: must be used). The last two entries allow mails from good@another.dom but reject mail from all other addresses with another.dom as domain part.
Delay all checks

By using FEATURE(`delay_checks') the rulesets check_mail and check_relay will not be called when a client connects or issues a MAIL command, respectively. Instead, those rulesets will be called by the check_rcpt ruleset; they will be skipped if a sender has been authenticated using a "trusted" mechanism, i.e., one that is defined via TRUST_AUTH_MECH(). If check_mail returns an error then the RCPT TO command will be rejected with that error. If it returns some other result starting with $# then check_relay will be skipped. If the sender address (or a part of it) is listed in the access map and it has a RHS of OK or RELAY, then check_relay will be skipped.
This has an interesting side effect: if your domain is my.domain and you have

my.domain RELAY

in the access map, then any e-mail with a sender address of will not be rejected by check_relay even though it would match the hostname or IP address. This allows spammers to get around DNS based blacklist by faking the sender address. To avoid this problem you have to use tagged entries:

To:my.domain RELAY
Connect:my.domain RELAY

if you need those entries at all (class {R} may take care of them).

FEATURE(`delay_checks') can take an optional argument:
FEATURE(`delay_checks', `friend') enables spamfriend test
FEATURE(`delay_checks', `hater') enables spamhater test

If such an argument is given, the recipient will be looked up in the access map (using the tag Spam:). If the argument is `friend', then the default behavior is to apply the other rulesets and make a SPAM friend the exception. The rulesets check_mail and check_relay will be skipped only if the recipient address is found and has RHS FRIEND. If the argument is `hater', then the default behavior is to skip the rulesets check_mail and check_relay and make a SPAM hater the exception. The other two rulesets will be applied only if the recipient address is found and has RHS HATER.

This allows for simple exceptions from the tests, e.g., by activating the friend option and having

Spam:abuse@ FRIEND

in the access map, mail to abuse@localdomain will get through (where "localdomain" is any domain in class {w}). It is also possible to specify a full address or an address with +detail:

Spam:abuse@my.domain FRIEND
Spam:me+abuse@ FRIEND
Spam:spam.domain FRIEND

Note: The required tag has been changed in 8.12 from To: to Spam:.

This change is incompatible to previous versions. However, you can (for now) simply add the new entries to the access map, the old ones will be ignored. As soon as you removed the old entries from the access map, specify a third parameter (`n') to this feature and the backward compatibility rules will not be in the generated .cf file.
Header Checks

You can also reject mail on the basis of the contents of headers. This is done by adding a ruleset call to the 'H' header definition command in sendmail.cf. For example, this can be used to check the validity of a Message-ID: header:

LOCAL_CONFIG
HMessage-Id: $>CheckMessageId

LOCAL_RULESETS
SCheckMessageId
R< $+ @ $+ > $@ OK
R$* $#error $: 553 Header Error

The alternative format:

HSubject: $>+CheckSubject

that is, $>+ instead of $>, gives the full Subject: header including comments to the ruleset (comments in parentheses () are stripped by default).

A default ruleset for headers which don't have a specific ruleset defined for them can be given by:

H*: $>CheckHdr

Notice:

1. All rules act on tokens as explained in doc/op/op.{me,ps,txt}. That may cause problems with simple header checks due to the tokenization. It might be simpler to use a regex map and apply it to $&{currHeader}.
2. There are no default rulesets coming with this distribution of sendmail. You can either write your own or you can search the WWW for examples.

After all of the headers are read, the check_eoh ruleset will be called for any final header-related checks. The ruleset is called with the number of headers and the size of all of the headers in bytes separated by $|. One example usage is to reject messages which do not have a Message-Id: header. However, the Message-Id: header is not a required header and is not a guaranteed spam indicator. This ruleset is an example and should probably not be used in production.

LOCAL_CONFIG
Kstorage macro

HMessage-Id: $>CheckMessageId

LOCAL_RULESETS
SCheckMessageId
# Record the presence of the header
R$* $: $(storage {MessageIdCheck} $@ OK $) $1
R< $+ @ $+ > $@ OK
R$* $#error $: 553 Header Error

Scheck_eoh
# Check the macro
R$* $: < $&{MessageIdCheck} >
# Clear the macro for the next message
R$* $: $(storage {MessageIdCheck} $) $1
# Has a Message-Id: header
R< $+ > $@ OK
# Allow missing Message-Id: from local mail
R$* $: < $&{client_name} >
R< > $@ OK
R< $=w > $@ OK
# Otherwise, reject the mail
R$* $#error $: 553 Header Error

Reference: http://www.blogger.com/post-create.g?blogID=1893597042435035889

Thursday, September 10, 2009

shell scripting

SkyHi @ Thursday, September 10, 2009
http://www.unix.com/shell-programming-scripting/


http://nixcraft.com/shell-scripting/

Shell script to chown for specific user

SkyHi @ Thursday, September 10, 2009
#!/bin/bash
IFS="
"

find / -user username >> /tmp.out

for i in `cat /tmp.out`; do
chown username "$i"
done
rm /tmp.out

exit




#find . -user username -exec chown otheruser {} \;
# find . -group apache -exec chgrp root {} \;


#find . -user username -exec chown otheruser {} \;
# find . -perm 775 -type d -exec chmod 775 {} \;
# find . -perm 644 -type f -exec chmod 664 {} \;

Shell script to change folder directory owner after restore

SkyHi @ Thursday, September 10, 2009

#!/bin/bash
HOMED="/home"
DIRS=$(ls -l $HOMED | grep ^d | awk '{ print $8}')
for d in $DIRS
do
echo "chown -R $d.$d $HOMED/$d"
done

Wednesday, September 9, 2009

Migrating from Blogger to Wordpress (FTP blogs)

SkyHi @ Wednesday, September 09, 2009
This post will explain how to migrate your FTP based Blogger account to a Wordpress based blog. It will keep your Google rankings, keep your permalinks and get it all done with minimum downtime.

I found many posts around the net about the best way to migrate from Blogger to Wordpress. However, many are out of date or overly complicated and many others didn’t work with FTP which is what I was after (you will use FTP if you use Blogger to post to your own domain e.g. www.benfrain.com/notepad/ rather than www.benfrain.blogspot.com).

1. If you have the ability to back up your site - do it first. You’ll be happy you did if it all goes wrong.

2. Log in to your blogger account. Goto Settings >> Publishing and then choose ‘Switch to: • blogspot.com (Blogger’s free hosting service)’. Enter the word verification and ‘Save Settings’

3. Head over to www.wordpress.com and set up a new online Wordpress account. Once you are set up (you’ll have to verify by email etc):

4. From the Wordpress interface, browse to Tools > Import and choose ‘Blogger’. Now follow this wizard through, let the blog be authenticated and click import to bring your posts into the Wordpress blog. Note: once this is complete you can switch Blogger back to FTP publishing if you wish but it isn’t necessary.

5. Once all the posts and comments are in, from the Wordpress interface choose Tools > Export and click the ‘Download Export File’ - save this somewhere safe e.g. to your desktop. You can now close your Wordpress.com hosted Wordpress blog. Wordpress doesn’t let you delete online Wordpress accounts you make with them so make sure you delete all the posts you just imported or they may show up in two place through search engines etc. ALl references to the Wordpress interface from now on will relate to the one you install on your own domain…

6. Use an FTP client (e.g. Filezilla) and delete the existing blog directory. However DO NOT delete the ‘uploaded images’ directory or you will lose all your pics when you import. Instead, download this folder to the desktop first then delete the direcory e.g. www.benfrain.com/notepad/uploaded images/ got downloaded and then www.benfrain.com/notepad/ got deleted.

7. Install Wordpress on your domain. If you have installatron or similar set up by your host it is very easy, if not, you’ll have to download and install the full package. The key however is to set your Wordpress blog up in the same directory you used to use for Blogger. Therefore, my new Wordpress blog was also www.benfrain.com/notepad/

8. Upload the ‘uploaded images’ to the new ‘notepad’ directory that Wordpress made on install. For example, my blog was at www.benfrain.com/notepad/ so I uploaded the ‘uploaded images’ folder from my desktop into that directory using Filezilla - NOTE: do not rename the ‘uploaded images’ directory!

9. Log in to your new FTP installed Wordpress blog e.g. www.yourdomain.com/blog/wp-admin/ and choose Tools >> Import. Choose ‘Wordpress’ and browse to the file you saved to your desktop and click ‘Import’. When prompted to import images, do so. You should now see all your posts and images but the permalinks (the actual url’s the postings have) are all different…

10. We now need to correct all the URL’s that Wordpress uses for posts so that we retain existing links from Google etc. To do this, head over to http://wordpress.org/extend/plugins/ and search and download ‘Maintain Blogger Permalinks‘ by Justin Watt. Add the Plugin by choosing Plugins >> Add new from the Wordpress interface, browse to the downloaded Zip file and install and Activate the plugin.

11. Still in Wordpress, choose Settings >> Permalinks and click the Radio Button for ‘Custom Structure’ and enter the following in the box ‘/%year%/%monthnum%/%postname%.html’ (the bit inside the apostrophes) - and click ’save changes’ this will ensure posts follow the same naming convention as Blogger.

12. Now choose Tools >> Maintain Blogger Permalinks and click the ‘Maintain Blogger Permalinks’ button. This will now rename all your existing posts to be the same format as they were in your Blogger FTP blog, preserving the page rank and links to those posts that already exist.

That’s it! Wordpress is a great app and amending the template (if indeed you did amend it) is as simple, if not simpler, than it is in Blogger and the wealth of plugins and ease of use it superb.

I’d love to know how anyone gets on with this, let me know…


Reference: http://benfrain.com/notepad/2009/04/migrating-from-ftp-based-blogger-to-wordpress.html

Secure tmp file system

SkyHi @ Wednesday, September 09, 2009
[root@web ~]# cat /etc/fstab
/dev/VolGroup00/LogVol00 / ext3 defaults 1 1
LABEL=/tmp /tmp ext3 noexec,nosuid,nodev,rw 0 0
LABEL=/var /var ext3 defaults 1 2
LABEL=/var/www/html /var/www/html ext3 defaults 1 2
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults,nosuid,noexec,rw 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
/dev/VolGroup00/LogVol01 swap swap defaults 0 0

Security Hints for PHP/MySQL Applications

SkyHi @ Wednesday, September 09, 2009
Security Hints for PHP/MySQL Applications
Apache Server Security

This page provides some geneal hints for Apache servers running PHP applications. I recommend to consider them for ConfTool installations and they are probably useful for most other productive environments with PHP and MySQL.
Access to Backup Files

It is advisable to block access to all backup files. If these are for instance PHP files, they are usually not executed and may reveal parameters like the password for your mysql database.

To block the access to backup files with the extensions "bak", "BAK" and "~" use the following lines in your httpd.conf file:


order deny,allow
deny from all


Example:


# For Conftool you need none of the options directive, if you do not
# use the .htaccess file, but make the conftool settings in php.ini
options none

# Controls who can get stuff from this server.
order deny,allow
allow from all

# Prevent access to backup files!

order deny,allow
deny from all





http://www.zdziarski.com/projects/mod_evasive/
MySql Database Security
Limit Network Access

If not required, block network access to the mysql database server from other hosts.

One way to limit any network access to your MySQL server is adding the parameter

skip-networking

to your mysql configuration file "my.cnf" (usually in /etc/ or C:/Windows/). Applications now have to use a socket file to access the MySQL deamon.

If disabling network access causes compatibility issues with some of your applications, you may also use

bind-address = 127.0.0.1

to limit access to localhost only.
Update Default Root User

Many distributions install a "root" MySQL user without any password. Make sure to set a password for the "root" user after a new server installation.

From the command line call

mysql mysql -u root

In the mysql client you have to enter two commands:

UPDATE user SET Password=PASSWORD('myNewPassword') WHERE user='root';
flush privileges;

The second command reads the new password into the mysql server.

Alternatively you can also use the "mysqladmin tool"

mysqladmin -u root password

You will be prompted for the password.

If you get the error message

mysqladmin: connect to server at 'localhost' failed
error: 'Access denied for user 'root'a'localhost' (using password: NO)'

a password for the user root is already set.
PHP Security Settings

PHP is not an "unsave" programming language, but there are some PHP settings that are recommended to reduce the vulnerability of most PHP installations. They are set in your php.ini file, some can also be set in the apache configuration file or your local .htaccess file. Please consider that other PHP scripts on your server might have problems with the settings recommended here.
DISABLE_FUNCTIONS

Some PHP functions can make your system vulnerable, as they provide access to system ressources, parameters or files.

Such are:

show_source, system, shell_exec, passthru, exec, phpinfo, popen, proc_open, proc_nice

Conftool makes use of two of these functions:

* "exec" is used on windows systems to check if the domain name of an email address exists. All parameters are sanitized before the function call. (The function is also used in some custom ConfTool libraries to access credit card gateways.)
* "popen" is used in the "phpmailer" library to send emails. You can alternatively use the build-in php function to send mails, but it is less powerful.

Therefore if you use one of the features above, you should only disable the following functions in the file "php.ini":

disable_functions = show_source, system, shell_exec, passthru, phpinfo, proc_open, proc_nice

REGISTER_GLOBALS

The switch

register_globals = Off

should always be set, as otherwise all http get and post variables are directly accessible as global variables in the PHP application. This is a potential security problem for any PHP application. I recommend not to use any PHP application that requires "register_globals" to be on.
ALLOW_URL_FOPEN

allow_url_fopen = Off

This should be set for most servers. It prevents that scripts can load php code from other web servers, a potential security issue.

allow_url_include = Off

Since PHP 5.2 the setting allow_url_include allows to disable remote addresses for the commands "include" and "require" only. So if some of your scripts require allow_url_fopen, the above settings might be an alternative.
DISPLAY_ERRORS

display_errors = Off

This setting will turn off the output of PHP error messages to your users and possible attackers. It should always be set to "off" in a productive environment. You can (and should) still log (and analyze) errors in the server's error_log by setting:

log_errors = On

OPEN_BASEDIR

Syntax: open_basedir = "/path/to/conftool"

Limits the execution of php files on your Web server. Files outside the

given path(s) are not executed. It is always recommended to use it and to restrict php to those directories where known applications reside.

Example for Windows:

open_basedir = "D:/www/conftool/;C:/Program Files/Apache Group/Apache/htdocs/"

Unix/Linux example:

open_basedir = "/home/conftool/:/srv/www/"

SAFE_MODE

safe_mode = On/Off

Safe Mode restricts the access of php scripts on your web server. It is currently not recommended to use it with ConfTool as e.g. timeouts cannot be set and the access to uploaded files is limited. ConfTool does somehow work with safe mode, but there are many potential problems (e.g. with bulk mails).
Hardened-PHP Project

The Hardened-PHP project provides two patches / extensions for PHP that can improve the security of all PHP installations:

* The hardening patch adds security hardening features to the PHP core to protect servers against a number of well known problems in PHP applications and against potential unknown vulnerabilities.
* Suhosin is an extension for PHP to protect servers and users from known and unknown flaws in PHP applications and the PHP core by adding new security filters and PHP security settings.

Both patches work well with ConfTool. I recommend the Suhosin extension for any productive environment running PHP applications.
Conclusion

Security is not a state but a process. As PHP any MySQL are very popular systems, always keep track of recent developments and update your server settings. If you find any potential problems in ConfTool, please contact me immediately.



Reference: http://www.conftool.net/en/technical_documentation/security_hints.html

Steps to Tighten PHP Security

SkyHi @ Wednesday, September 09, 2009
Recently I have had to deal with some insecure PHP scripts on a couple of servers that have caused us some serious problems, as well as time, to recover from.

I am going to list some of the important steps you can take to protect your server and your site from insecure PHP applications. This will by no means a complete list of items to stop them, but this should help prevent most of the basic attacks ("script kiddie" attacks - where the attacker doesn't have a great deal of skill and is depending on a preset scenario).

Most of these solutions will assume you have some level of control (root) over the server.

* Turn off allow_url_fopen: This modification will prevent the use of http://www.domain.com/somescript.php and ftp://www.domain.com/somescript.php from being used in include(), include_once(), require(), require_once(), as well as fopen(). This will prevent a hacker from including malicious code remotely. This modification will prevent the vast majority of hack attempts in PHP from working.

The downside of this modification is that some legitmate applications that use fopen() to open a remote web page might be broken. You can encourage users to use the PHP curl functions instead as they accomplish the same results.

Edit your php.ini and change allow_url_fopen = On to allow_url_fopen = Off and restart your web server.

* Use open_basedir: open_basedir allows you to dictate which paths PHP is allowed to access for a given site. Generally we set this to the path of the website (/var/www/html), /tmp (for writting session data as well as for file uploads), and the path to the PEAR repository.

The good thing about open_basedir is that it is default deny, meaning if you don't specify the path in the open_basedir it is blocked.

The bad part about open_basedir is that it come sometimes block access to legitmate applications needed by your PHP applications (Gallery is one that comes to mind, as it makes use of some external applications in /usr/bin, so you must open access to that location).

Generally, you should use this directive for every website you host as it allows you to control which directories PHP can access and you can make sure that those directories have the correct permissions to prevent potential exploitation.

* Mount /tmp noexec, nosuid and nodev: This one is particularly useful as it allows you to tell the operating system not to run any applications in a given area of the hard drive. I can tell you personally that this one as saved me numerous times. When used in combintation with the open_basedir directive you can effectively limit what the hackers have access to, and what they are able to run.

If you have a seperate /tmp partition on your hard drive you can edit the /etc/fstab file and change the options for the /tmp line.

/dev/hda3 /tmp ext3 noexec,nosuid,nodev 0 0

If you don't have a seperate /tmp partition you can create one as a loopback filesystem and mount that as noexec. I will make a seperate post on how to do this later.

* Mount your web space noexec: This might not be possible, but is a great option just like mounting /tmp in noexec. The reason for this is to prevent binary applications from being uploaded and executed in your webspace. Like I said this might not be possible, but is an excellent prevention method to prevent local root exploit binaries (where a binary exploits a problem in the kernel to gain escallated priviledges on the server, the /proc race in the 2.6 kernel is a recent example of this type of exploit).

* Make sure your permissions are correct: You should not allow world write permissions on any files, other than those required (configuration files that are written by the web server, etc). This is very important as it will save you a great deal of trouble in the event that a hacker does gain access to your site, as they won't be able to overwrite your files. Additionally, you should only allow write access to specific folders where needed.

* Prevent PHP from parsing scripts in world writtable directories: This will prevent hackers from uploading malicious scripts and running them from your site. This is a great way to tighten security, and is pretty easy to manage, just set "php_admin_flag engine off" for any directory that can be written to by the web server user. This one will save you more hassle than you can ever imagine.

* Install mod_security: Mod Security is basically a web server firewall, allowing you to block specific types of requests, as well as inspect data as it is sent to the server. My only problem with mod_security is that it isn't default deny, which means you must identify what is blocked, rather than identifying what is allowed and rejecting everything else. Still it has its uses and you should have it installed in order to react to problems that do not have patches available yet.

We hope that this list of items will help protect your server from hackers and allow you to have some peace of mind that your sites are as secure as you can make them.


Reference: http://www.hostinggeek.com/2006/07/steps-to-tighten-php-security.html

rsync

SkyHi @ Wednesday, September 09, 2009
#!/bin/sh
backupSystemName=backupserver
backupSystemUser=backupuser
# rsync
echo "[backup/thedump] $HOSTNAME - `date` " > /tmpdirectory/.output
echo "------------------------------------" >> /tmpdirectory/.output
echo "directory: /etc" >> /tmpdirectory/.output
rsync -v -r -u -L --bwlimit=200 --delete --delete-excluded -e ssh -z /etc $backupSystemUser@$backupSystemName:/backupdirectory/$HOSTNAME >> /tmpdirectory/.output
echo "------------------------------------" >> /tmpdirectory/.output
echo "directory: /home" >> /tmpdirectory/.output
rsync -v -r -u -L --bwlimit=200 --delete --delete-excluded -e ssh -z /home $backupSystemUser@$backupSystemName:/backupdirectory/$HOSTNAME >> /tmpdirectory/.output
echo "------------------------------------" >> /tmpdirectory/.output
echo "directory: /usr/local" >> /tmpdirectory/.output
rsync -v -r -u -L --bwlimit=200 --delete --delete-excluded -e ssh -z --exclude apache/logs/ /usr/local $backupSystemUser@$backupSystemName:/backupdirectory/$HOSTNAME >> /tmpdirectory/.output
echo "------------------------------------" >> /tmpdirectory/.output
echo "directory: /root" >> /tmpdirectory/.output
rsync -v -r -u -L --bwlimit=200 --delete --delete-excluded -e ssh -z /root $backupSystemUser@$backupSystemName:/backupdirectory/$HOSTNAME >> /tmpdirectory/.output
echo "------------------------------------" >> /tmpdirectory/.output
echo "directory: /var" >> /tmpdirectory/.output
rsync -v -r -u -L --bwlimit=200 --delete --delete-excluded -e ssh -z --exclude /var/mail/ --exclude /var/log/ --exclude /var/spool/ /var $backupSystemUser@$backupSystemName:/backupdirectory/$HOSTNAME >> /tmpdirectory/.output
echo "------------------------------------" >> /tmpdirectory/.output
echo "complete." >> /tmpdirectory/.output
mail -s "[backup/thedump] $HOSTNAME - `date`" sysadmin@server < /tmpdirectory/.output

sendmail removes email more than n days old.

SkyHi @ Wednesday, September 09, 2009


A variation that removes email more than n days old.

find /var/spool/mqueue/ -type f -mtime +n -ls -exec rm {} \;
and
find /var/spool/mqueue.in/ -type f -mtime +n -ls -exec rm {} \;

I used n=1 to cleanup all email from mqueue more than 1 day old
find /var/spool/mqueue/ -type f -mtime +1 -ls -exec rm {} \;
As most spam is undeliverable so the server attempts to send for 5 days
Note: if you have a large mqueue it will take a while to complete.

[root@pot mqueue]# date
Wed Sep 9 10:46:37 PDT 2009


[root@pot mqueue]# ls -l|wc -l
1716





[root@pot mqueue]# find /var/spool/mqueue -mtime 1 -exec ls -l {} \;
-rw------- 1 root smmsp 873 2009-09-07 18:29 /var/spool/mqueue/Qfn832XASB009701
-rw------- 1 root smmsp 893 2009-09-07 20:59 /var/spool/mqueue/Qfn8349F0c024789
-rw------- 1 root smmsp 818 2009-09-08 01:59 /var/spool/mqueue/Qfn888xRKm015663
-rw------- 1 root smmsp 933 2009-09-08 04:28 /var/spool/mqueue/Qfn83BbnJF025245
-rw------- 1 root smmsp 809 2009-09-08 07:46 /var/spool/mqueue/Qfn88EkLUe013813
-rw------- 1 root smmsp 937 2009-09-07 13:29 /var/spool/mqueue/Qfn82LiDjA012825
-rw------- 1 root smmsp 870 2009-09-07 11:23 /var/spool/mqueue/Qfn858pwHv003138
-rw------- 1 root smmsp 984 2009-09-07 11:23 /var/spool/mqueue/Qfn861BimA005433
-rw------- 1 root smmsp 2222 2009-09-07 14:50 /var/spool/mqueue/dfn87Lo7mZ029723
-rw------- 1 root smmsp 830 2009-09-07 14:50 /var/spool/mqueue/Qfn87Lo7mZ029723
-rw------- 1 root smmsp 1665 2009-09-07 15:30 /var/spool/mqueue/dfn87MUHmO005276
-rw------- 1 root smmsp 9564 2009-09-07 10:58 /var/spool/mqueue/dfn87Hw8Ej016301
-rw------- 1 root smmsp 732 2009-09-07 10:58 /var/spool/mqueue/Qfn87Hw8Ej016301
-rw------- 1 root smmsp 1653 2009-09-07 11:22 /var/spool/mqueue/dfn87IMh8R021199
-rw------- 1 root smmsp 3177 2009-09-07 15:50 /var/spool/mqueue/dfn87MoI4n009310
-rw------- 1 root smmsp 1653 2009-09-07 18:36 /var/spool/mqueue/dfn881aqeR003540
-rw------- 1 root smmsp 1670 2009-09-07 20:08 /var/spool/mqueue/dfn88382Jl020169
-rw------- 1 root smmsp 4792 2009-09-08 07:46 /var/spool/mqueue/dfn88Ek3Ue013727
-rw------- 1 root smmsp 16354 2009-09-07 22:02 /var/spool/mqueue/dfn8852USc007108
-rw------- 1 root smmsp 785 2009-09-07 22:02 /var/spool/mqueue/Qfn8852USc007108
-rw------- 1 root smmsp 7008 2009-09-08 00:07 /var/spool/mqueue/dfn8877e7t028972
-rw------- 1 root smmsp 818 2009-09-08 00:07 /var/spool/mqueue/Qfn8877e7t028972
-rw------- 1 root smmsp 9787 2009-09-08 00:45 /var/spool/mqueue/dfn887jSWh003020
-rw------- 1 root smmsp 851 2009-09-08 00:45 /var/spool/mqueue/Qfn887jSWh003020
-rw------- 1 root smmsp 6983 2009-09-08 00:07 /var/spool/mqueue/dfn8877g1h028979
-rw------- 1 root smmsp 830 2009-09-08 00:07 /var/spool/mqueue/Qfn8877g1h028979
-rw------- 1 root smmsp 1663 2009-09-08 01:16 /var/spool/mqueue/dfn888Gkuf008249
-rw------- 1 root smmsp 3474 2009-09-08 01:45 /var/spool/mqueue/dfn888jgGs013304
-rw------- 1 root smmsp 836 2009-09-08 01:45 /var/spool/mqueue/Qfn888jgGs013304
-rw------- 1 root smmsp 3984 2009-09-08 01:59 /var/spool/mqueue/dfn888xRKm015653
-rw------- 1 root smmsp 3716 2009-09-08 01:59 /var/spool/mqueue/dfn888xYKm015698
-rw------- 1 root smmsp 7812 2009-09-08 02:07 /var/spool/mqueue/dfn8897rqS016976
-rw------- 1 root smmsp 3542 2009-09-08 01:59 /var/spool/mqueue/dfn888xRKm015663
-rw------- 1 root smmsp 851 2009-09-08 01:59 /var/spool/mqueue/Qfn888xRKm015653
-rw------- 1 root smmsp 812 2009-09-08 02:07 /var/spool/mqueue/Qfn8897rqS016976
-rw------- 1 root smmsp 8247 2009-09-08 02:07 /var/spool/mqueue/dfn8897tqS016999
-rw------- 1 root smmsp 4591 2009-09-08 02:22 /var/spool/mqueue/dfn889MgNG019595
-rw------- 1 root smmsp 815 2009-09-08 02:22 /var/spool/mqueue/Qfn889MgNG019595
-rw------- 1 root smmsp 824 2009-09-08 02:07 /var/spool/mqueue/Qfn8897tqS016999
-rw------- 1 root smmsp 7769 2009-09-08 08:57 /var/spool/mqueue/dfn88FvSiD031304
-rw------- 1 root smmsp 3873 2009-09-08 06:19 /var/spool/mqueue/dfn88DJPqq028889
-rw------- 1 root smmsp 812 2009-09-08 01:59 /var/spool/mqueue/Qfn888xYKm015698
-rw------- 1 root smmsp 815 2009-09-08 06:19 /var/spool/mqueue/Qfn88DJPqq028889
-rw------- 1 root smmsp 3501 2009-09-08 07:25 /var/spool/mqueue/dfn88EP0sp008882
-rw------- 1 root smmsp 777 2009-09-08 07:25 /var/spool/mqueue/Qfn88EP0sp008882
-rw------- 1 root smmsp 3467 2009-09-08 06:54 /var/spool/mqueue/dfn88DsOFx003182
-rw------- 1 root smmsp 818 2009-09-08 06:54 /var/spool/mqueue/Qfn88DsOFx003182
-rw------- 1 root smmsp 3618 2009-09-08 07:45 /var/spool/mqueue/dfn88EjhUe013582
-rw------- 1 root smmsp 806 2009-09-08 07:45 /var/spool/mqueue/Qfn88EjhUe013582
-rw------- 1 root smmsp 1666 2009-09-08 07:45 /var/spool/mqueue/dfn88Ejogt013624
-rw------- 1 root smmsp 785 2009-09-08 08:57 /var/spool/mqueue/Qfn88FvSiD031304
-rw------- 1 root smmsp 1683 2009-09-08 09:31 /var/spool/mqueue/dfn88GVP9J009581
-rw------- 1 root smmsp 3995 2009-09-08 07:46 /var/spool/mqueue/dfn88EkLUe013813
-rw------- 1 root smmsp 1664 2009-09-08 10:19 /var/spool/mqueue/dfn88HJMx9025290
find: /var/spool/mqueue/dfn89Hhmj5024236: No such file or directory
find: /var/spool/mqueue/qfn89Hhmj5024236: No such file or directory






[root@potato2 mqueue]# find /var/spool/mqueue -mtime +1 -exec ls -l {} \;
-rw------- 1 root smmsp 981 2009-08-04 23:27 /var/spool/mqueue/Qfn7557tel017436
-rw------- 1 root smmsp 943 2009-08-05 16:09 /var/spool/mqueue/Qfn751vt5W018935
-rw------- 1 root smmsp 820 2009-08-13 00:01 /var/spool/mqueue/Qfn7D71AQj012496
-rw------- 1 root smmsp 4565 2009-08-04 17:14 /var/spool/mqueue/dfn750EUYk001563
-rw------- 1 root smmsp 803 2009-08-04 17:14 /var/spool/mqueue/Qfn750EUYk001563
-rw------- 1 root smmsp 4266 2009-08-04 17:14 /var/spool/mqueue/dfn750Ev1O001681
-rw------- 1 root smmsp 794 2009-08-04 17:14 /var/spool/mqueue/Qfn750Ev1O001681
-rw------- 1 root smmsp 5743 2009-08-04 19:37 /var/spool/mqueue/dfn752bMId025193
-rw------- 1 root smmsp 10236 2009-08-11 10:12 /var/spool/mqueue/dfn7BHCXbn002060
-rw------- 1 root smmsp 3001 2009-08-04 18:57 /var/spool/mqueue/dfn751vt5W018935
-rw------- 1 root smmsp 859 2009-08-04 19:37 /var/spool/mqueue/Qfn752bMId025193
-rw------- 1 root smmsp 3523 2009-08-04 19:01 /var/spool/mqueue/dfn7521JSZ019537
-rw------- 1 root smmsp 904 2009-08-04 19:01 /var/spool/mqueue/Qfn7521JSZ019537
-rw------- 1 root smmsp 2149 2009-08-04 19:03 /var/spool/mqueue/dfn7523Y0p019929
-rw------- 1 root smmsp 860 2009-08-04 19:03 /var/spool/mqueue/Qfn7523Y0p019929
-rw------- 1 root smmsp 22144 2009-08-04 21:40 /var/spool/mqueue/dfn754eTXQ011566
-rw------- 1 root smmsp 2136 2009-08-04 21:41 /var/spool/mqueue/dfn754fflQ011761
-rw------- 1 root smmsp 860 2009-08-04 21:40 /var/spool/mqueue/Qfn754eTXQ011566
-rw------- 1 root smmsp 863 2009-08-04 21:41 /var/spool/mqueue/Qfn754fflQ011761
-rw------- 1 root smmsp 2173 2009-08-04 22:07 /var/spool/mqueue/dfn7557tel017436
-rw------- 1 root smmsp 973 2009-08-13 20:35 /var/spool/mqueue/Qfn7E3ZjFq007772
-rw------- 1 root smmsp 4827 2009-08-04 22:17 /var/spool/mqueue/dfn755HwxU019673
-rw------- 1 root smmsp 4911 2009-08-04 22:12 /var/spool/mqueue/dfn755Cuok018520
-rw------- 1 root smmsp 732 2009-08-04 22:12 /var/spool/mqueue/Qfn755Cuok018520
-rw------- 1 root smmsp 785 2009-08-04 22:17 /var/spool/mqueue/Qfn755HwxU019673
-rw------- 1 root smmsp 3150 2009-08-05 01:55 /var/spool/mqueue/dfn758tsAi024080
-rw------- 1 root smmsp 827 2009-08-05 01:55 /var/spool/mqueue/Qfn758tsAi024080
-rw------- 1 root smmsp 2051 2009-08-04 22:35 /var/spool/mqueue/dfn755Z2r4022991
-rw------- 1 root smmsp 830 2009-08-04 22:35 /var/spool/mqueue/Qfn755Z2r4022991
-rw------- 1 root smmsp 2094 2009-08-04 23:01 /var/spool/mqueue/dfn7561pjf028315
-rw------- 1 root smmsp 2109 2009-08-04 23:01 /var/spool/mqueue/dfn7561b7M028259
-rw------- 1 root smmsp 848 2009-08-04 23:01 /var/spool/mqueue/Qfn7561pjf028315
-rw------- 1 root smmsp 803 2009-08-05 06:07 /var/spool/mqueue/Qfn75D7F19029513
-rw------- 1 root smmsp 2568 2009-08-05 09:02 /var/spool/mqueue/dfn75G2v2X002907
-rw------- 1 root smmsp 958 2009-08-10 10:16 /var/spool/mqueue/Qfn7A8S3Xo003423
-rw------- 1 root smmsp 17403 2009-08-05 08:07 /var/spool/mqueue/dfn75F7t6s019730
-rw------- 1 root smmsp 924 2009-08-10 07:49 /var/spool/mqueue/Qfn75F7t6s019730
-rw------- 1 root smmsp 1930 2009-08-05 08:21 /var/spool/mqueue/dfn75FL5xi023450
-rw------- 1 root smmsp 854 2009-08-05 09:02 /var/spool/mqueue/Qfn75G2v2X002907
-rw------- 1 root smmsp 3577 2009-08-05 08:55 /var/spool/mqueue/dfn75FtwZj000752
-rw------- 1 root smmsp 8141 2009-08-05 13:13 /var/spool/mqueue/dfn75KDlPc011102
-rw------- 1 root smmsp 791 2009-08-05 08:55 /var/spool/mqueue/Qfn75FtwZj000752
-rw------- 1 root smmsp 2243 2009-08-05 19:09 /var/spool/mqueue/dfn7629hfh026532
-rw------- 1 root smmsp 2084 2009-08-05 11:17 /var/spool/mqueue/dfn75IHdt1010309
-rw------- 1 root smmsp 833 2009-08-05 11:17 /var/spool/mqueue/Qfn75IHdt1010309
-rw------- 1 root smmsp 2128 2009-08-05 12:02 /var/spool/mqueue/dfn75J2T20024763
-rw------- 1 root smmsp 872 2009-08-05 12:02 /var/spool/mqueue/Qfn75J2T20024763
-rw------- 1 root smmsp 821 2009-08-05 18:04 /var/spool/mqueue/Qfn7614DQO014537
-rw------- 1 root smmsp 788 2009-08-05 13:13 /var/spool/mqueue/Qfn75KDlPc011102
-rw------- 1 root smmsp 8266 2009-08-05 14:21 /var/spool/mqueue/dfn75LLhKr028312
-rw------- 1 root smmsp 857 2009-08-05 14:21 /var/spool/mqueue/Qfn75LLhKr028312
-rw------- 1 root smmsp 2186 2009-08-05 17:27 /var/spool/mqueue/dfn760RLAJ008509
-rw------- 1 root smmsp 3505 2009-08-05 15:03 /var/spool/mqueue/dfn75M3kQw006940
-rw------- 1 root smmsp 777 2009-08-05 15:03 /var/spool/mqueue/Qfn75M3kQw006940
-rw------- 1 root smmsp 3500 2009-08-05 16:47 /var/spool/mqueue/dfn75Nl6SG000420
-rw------- 1 root smmsp 777 2009-08-05 16:47 /var/spool/mqueue/Qfn75Nl6SG000420
-rw------- 1 root smmsp 8616 2009-08-05 17:00 /var/spool/mqueue/dfn7600KHn003339
-rw------- 1 root smmsp 839 2009-08-05 19:11 /var/spool/mqueue/Qfn762BFV3026813
-rw------- 1 root smmsp 2280 2009-08-05 19:31 /var/spool/mqueue/dfn762VNgU030867
-rw------- 1 root smmsp 866 2009-08-05 19:31 /var/spool/mqueue/Qfn762VNgU030867
-rw------- 1 root smmsp 842 2009-08-06 12:07 /var/spool/mqueue/Qfn76J7n6o019428
-rw------- 1 root smmsp 1980 2009-08-06 14:58 /var/spool/mqueue/dfn76Lw9cb004047
-rw------- 1 root smmsp 20170 2009-08-06 11:05 /var/spool/mqueue/dfn76I5jH3002154
-rw------- 1 root smmsp 791 2009-08-06 11:05 /var/spool/mqueue/Qfn76I5jH3002154
-rw------- 1 root smmsp 4892 2009-08-06 12:01 /var/spool/mqueue/dfn76J1qkG017649
-rw------- 1 root smmsp 2440 2009-08-06 14:56 /var/spool/mqueue/dfn76LuZLs003325
-rw------- 1 root smmsp 3157 2009-08-06 14:40 /var/spool/mqueue/dfn76Lexnk030473
-rw------- 1 root smmsp 809 2009-08-06 14:40 /var/spool/mqueue/Qfn76Lexnk030473
-rw------- 1 root smmsp 815 2009-08-06 14:56 /var/spool/mqueue/Qfn76LuZLs003325
-rw------- 1 root smmsp 2672 2009-08-06 21:29 /var/spool/mqueue/dfn774T6Q6010889
-rw------- 1 root smmsp 827 2009-08-06 14:58 /var/spool/mqueue/Qfn76Lw9cb004047
-rw------- 1 root smmsp 785 2009-08-06 21:29 /var/spool/mqueue/Qfn774T6Q6010889
-rw------- 1 root smmsp 3264 2009-08-06 17:28 /var/spool/mqueue/dfn770SSo8006697
-rw------- 1 root smmsp 5093 2009-08-06 17:49 /var/spool/mqueue/dfn770nM2T010250
-rw------- 1 root smmsp 815 2009-08-06 17:49 /var/spool/mqueue/Qfn770nM2T010250
-rw------- 1 root smmsp 794 2009-08-06 17:28 /var/spool/mqueue/Qfn770SSo8006697
-rw------- 1 root smmsp 3367 2009-08-06 21:29 /var/spool/mqueue/dfn774TJQ6010932
-rw------- 1 root smmsp 2418 2009-08-06 21:29 /var/spool/mqueue/dfn774TRQ6011022
-rw------- 1 root smmsp 830 2009-08-06 21:29 /var/spool/mqueue/Qfn774TRQ6011022
-rw------- 1 root smmsp 803 2009-08-06 21:29 /var/spool/mqueue/Qfn774TJQ6010932
-rw------- 1 root smmsp 3116 2009-08-06 22:46 /var/spool/mqueue/dfn775kh7N022317
-rw------- 1 root smmsp 803 2009-08-06 22:46 /var/spool/mqueue/Qfn775kh7N022317
-rw------- 1 root smmsp 3492 2009-08-06 23:50 /var/spool/mqueue/dfn776oEiU001546
-rw------- 1 root smmsp 777 2009-08-06 23:50 /var/spool/mqueue/Qfn776oEiU001546
-rw------- 1 root smmsp 782 2009-08-08 21:04 /var/spool/mqueue/Qfn7944sQP003628
-rw------- 1 root smmsp 833 2009-08-07 01:42 /var/spool/mqueue/Qfn778gmKl022385
-rw------- 1 root smmsp 1916 2009-08-07 05:24 /var/spool/mqueue/dfn77COr6S026523
-rw------- 1 root smmsp 2368 2009-08-07 07:10 /var/spool/mqueue/dfn77EAVHr014466
-rw------- 1 root smmsp 2333 2009-08-07 07:09 /var/spool/mqueue/dfn77E9Q5G014243
-rw------- 1 root smmsp 791 2009-08-07 05:24 /var/spool/mqueue/Qfn77COr6S026523
-rw------- 1 root smmsp 872 2009-08-07 07:10 /var/spool/mqueue/Qfn77EAVHr014466
-rw------- 1 root smmsp 839 2009-08-07 07:09 /var/spool/mqueue/Qfn77E9Q5G014243
-rw------- 1 root smmsp 8386 2009-08-07 09:32 /var/spool/mqueue/dfn77GW4W3014778
-rw------- 1 root smmsp 2329 2009-08-07 07:50 /var/spool/mqueue/dfn77EoAM5023775
-rw------- 1 root smmsp 839 2009-08-07 07:50 /var/spool/mqueue/Qfn77EoAM5023775
-rw------- 1 root smmsp 791 2009-08-07 09:32 /var/spool/mqueue/Qfn77GW4W3014778
-rw------- 1 root smmsp 5013 2009-08-07 09:46 /var/spool/mqueue/dfn77GkgRE018713
-rw------- 1 root smmsp 777 2009-08-07 09:46 /var/spool/mqueue/Qfn77GkgRE018713
-rw------- 1 root smmsp 3500 2009-08-07 10:29 /var/spool/mqueue/dfn77HT3sv030330
-rw------- 1 root smmsp 777 2009-08-07 10:29 /var/spool/mqueue/Qfn77HT3sv030330
-rw------- 1 root smmsp 2153 2009-08-07 22:35 /var/spool/mqueue/dfn785ZNLM012607
-rw------- 1 root smmsp 824 2009-08-07 22:35 /var/spool/mqueue/Qfn785ZNLM012607
-rw------- 1 root smmsp 2117 2009-08-08 00:35 /var/spool/mqueue/dfn787Zb9F028884
-rw------- 1 root smmsp 3873 2009-08-07 11:37 /var/spool/mqueue/dfn77IbIOL016804
-rw------- 1 root smmsp 1037 2009-08-08 23:57 /var/spool/mqueue/Qfn796vjCh027851
-rw------- 1 root smmsp 815 2009-08-07 11:37 /var/spool/mqueue/Qfn77IbIOL016804
-rw------- 1 root smmsp 6443 2009-08-08 00:41 /var/spool/mqueue/dfn787ffrl029590
-rw------- 1 root smmsp 800 2009-08-08 00:35 /var/spool/mqueue/Qfn787Zb9F028884
-rw------- 1 root smmsp 2153 2009-08-08 00:35 /var/spool/mqueue/dfn787Zg9F028896
-rw------- 1 root smmsp 732 2009-08-08 00:41 /var/spool/mqueue/Qfn787ffrl029590
-rw------- 1 root smmsp 2548 2009-08-08 00:35 /var/spool/mqueue/dfn787Zg9F028908
-rw------- 1 root smmsp 827 2009-08-08 00:35 /var/spool/mqueue/Qfn787Zg9F028896
-rw------- 1 root smmsp 3134 2009-08-08 05:30 /var/spool/mqueue/dfn78CU9Um001842
-rw------- 1 root smmsp 803 2009-08-08 05:30 /var/spool/mqueue/Qfn78CU9Um001842
-rw------- 1 root smmsp 803 2009-08-08 10:32 /var/spool/mqueue/Qfn78HWFbR011087
-rw------- 1 root smmsp 815 2009-08-08 11:10 /var/spool/mqueue/Qfn78IAMgb016789
-rw------- 1 root smmsp 2491 2009-08-08 11:10 /var/spool/mqueue/dfn78IAUgb016816
-rw------- 1 root smmsp 800 2009-08-08 11:10 /var/spool/mqueue/Qfn78IAUgb016816
-rw------- 1 root smmsp 806 2009-08-08 07:29 /var/spool/mqueue/Qfn78ETnoq017649
-rw------- 1 root smmsp 2534 2009-08-08 11:10 /var/spool/mqueue/dfn78IAZgb016837
-rw------- 1 root smmsp 821 2009-08-08 11:10 /var/spool/mqueue/Qfn78IAZgb016837
-rw------- 1 root smmsp 2176 2009-08-08 13:40 /var/spool/mqueue/dfn78KeugD005757
-rw------- 1 root smmsp 842 2009-08-08 13:40 /var/spool/mqueue/Qfn78KeugD005757
-rw------- 1 root smmsp 7906 2009-08-08 18:36 /var/spool/mqueue/dfn791alRY016806
-rw------- 1 root smmsp 806 2009-08-08 18:36 /var/spool/mqueue/Qfn791alRY016806
-rw------- 1 root smmsp 2659 2009-08-08 20:15 /var/spool/mqueue/dfn793F9iS029541
-rw------- 1 root smmsp 794 2009-08-08 20:15 /var/spool/mqueue/Qfn793F9iS029541
-rw------- 1 root smmsp 2870 2009-08-08 21:04 /var/spool/mqueue/dfn7944sQP003628
-rw------- 1 root smmsp 848 2009-08-08 21:04 /var/spool/mqueue/Qfn7944pDq003613
-rw------- 1 root smmsp 2129 2009-08-09 00:28 /var/spool/mqueue/dfn797SR8W000588
-rw------- 1 root smmsp 971 2009-08-10 07:49 /var/spool/mqueue/Qfn75FL5xi023450
-rw------- 1 root smmsp 3007 2009-08-08 23:57 /var/spool/mqueue/dfn796vjCh027851
-rw------- 1 root smmsp 842 2009-08-09 00:28 /var/spool/mqueue/Qfn797SR8W000588
-rw------- 1 root smmsp 8513 2009-08-09 01:07 /var/spool/mqueue/dfn7987Wf6007322
-rw------- 1 root smmsp 804 2009-08-09 01:07 /var/spool/mqueue/Qfn7987Wf6007322
-rw------- 1 root smmsp 2184 2009-08-09 03:48 /var/spool/mqueue/dfn79Ami8K028907
-rw------- 1 root smmsp 824 2009-08-09 03:48 /var/spool/mqueue/Qfn79Ami8K028907
-rw------- 1 root smmsp 2839 2009-08-09 03:48 /var/spool/mqueue/dfn79Amn8K028928
-rw------- 1 root smmsp 1938 2009-08-09 05:35 /var/spool/mqueue/dfn79CZGPc011024
-rw------- 1 root smmsp 779 2009-08-09 05:35 /var/spool/mqueue/Qfn79CZGPc011024
-rw------- 1 root smmsp 836 2009-08-09 03:48 /var/spool/mqueue/Qfn79Amn8K028928
-rw------- 1 root smmsp 2077 2009-08-09 17:40 /var/spool/mqueue/dfn7A0euee024915
-rw------- 1 root smmsp 2126 2009-08-09 22:50 /var/spool/mqueue/dfn7A5oYrK010965
-rw------- 1 root smmsp 803 2009-08-09 22:50 /var/spool/mqueue/Qfn7A5oYrK010965
-rw------- 1 root smmsp 4256 2009-08-09 23:10 /var/spool/mqueue/dfn7A6Ao6P014020
-rw------- 1 root smmsp 812 2009-08-09 23:10 /var/spool/mqueue/Qfn7A6Ao6P014020
-rw------- 1 root smmsp 1920 2009-08-10 00:22 /var/spool/mqueue/dfn7A7MtcF025945
-rw------- 1 root smmsp 734 2009-08-10 00:22 /var/spool/mqueue/Qfn7A7MtcF025945
-rw------- 1 root smmsp 734 2009-08-10 00:23 /var/spool/mqueue/Qfn7A7Na9o026063
-rw------- 1 root smmsp 6315 2009-08-10 02:23 /var/spool/mqueue/dfn7A9NuZa012329
-rw------- 1 root smmsp 974 2009-08-17 19:27 /var/spool/mqueue/Qfn7D2jUoB031445
-rw------- 1 root smmsp 1938 2009-08-10 00:23 /var/spool/mqueue/dfn7A7Na9o026063
-rw------- 1 root smmsp 3084 2009-08-10 01:28 /var/spool/mqueue/dfn7A8S3Xo003423
-rw------- 1 root smmsp 861 2009-08-10 02:23 /var/spool/mqueue/Qfn7A9NuZa012329
-rw------- 1 root smmsp 2377 2009-08-10 01:36 /var/spool/mqueue/dfn7A8aQg2004621
-rw------- 1 root smmsp 814 2009-08-10 01:36 /var/spool/mqueue/Qfn7A8aQg2004621
-rw------- 1 root smmsp 1962 2009-08-10 02:27 /var/spool/mqueue/dfn7A9RwVx013328
-rw------- 1 root smmsp 2030 2009-08-10 02:26 /var/spool/mqueue/dfn7A9QRSS012877
-rw------- 1 root smmsp 841 2009-08-10 02:26 /var/spool/mqueue/Qfn7A9QRSS012877
-rw------- 1 root smmsp 865 2009-08-10 02:27 /var/spool/mqueue/Qfn7A9RwVx013328
-rw------- 1 root smmsp 2000 2009-08-10 02:29 /var/spool/mqueue/dfn7A9T6gY013562
-rw------- 1 root smmsp 847 2009-08-10 02:29 /var/spool/mqueue/Qfn7A9T6gY013562
-rw------- 1 root smmsp 37726 2009-08-10 02:44 /var/spool/mqueue/dfn7A9iCXr016885
-rw------- 1 root smmsp 1044 2009-08-15 02:41 /var/spool/mqueue/Qfn7A9iCXr016885
-rw------- 1 root smmsp 808 2009-08-16 08:04 /var/spool/mqueue/Qfn7GF45dr008248
-rw------- 1 root smmsp 3206 2009-08-10 13:06 /var/spool/mqueue/dfn7AK6YqU020847
-rw------- 1 root smmsp 3879 2009-08-11 03:56 /var/spool/mqueue/dfn7BAuk0H022526
-rw------- 1 root smmsp 7133 2009-08-10 13:50 /var/spool/mqueue/dfn7AKovEa032131
-rw------- 1 root smmsp 4226 2009-08-10 10:40 /var/spool/mqueue/dfn7AHeFN0014642
-rw------- 1 root smmsp 790 2009-08-10 13:50 /var/spool/mqueue/Qfn7AKovEa032131
-rw------- 1 root smmsp 2088 2009-08-15 21:15 /var/spool/mqueue/dfn7G4F5NX014584
-rw------- 1 root smmsp 808 2009-08-15 21:15 /var/spool/mqueue/Qfn7G4F5NX014584
-rw------- 1 root smmsp 3554 2009-08-15 22:10 /var/spool/mqueue/dfn7G5ARAo022334
-rw------- 1 root smmsp 820 2009-08-15 22:10 /var/spool/mqueue/Qfn7G5ARAo022334
-rw------- 1 root smmsp 3703 2009-08-16 02:08 /var/spool/mqueue/dfn7G98Vt0023660
-rw------- 1 root smmsp 820 2009-08-16 02:08 /var/spool/mqueue/Qfn7G98Vt0023660
-rw------- 1 root smmsp 5357 2009-08-10 19:51 /var/spool/mqueue/dfn7B2pekk013110
-rw------- 1 root smmsp 811 2009-08-10 19:51 /var/spool/mqueue/Qfn7B2pekk013110
-rw------- 1 root smmsp 4561 2009-08-10 19:59 /var/spool/mqueue/dfn7B2xCmE014473
-rw------- 1 root smmsp 781 2009-08-10 19:59 /var/spool/mqueue/Qfn7B2xCmE014473
-rw------- 1 root smmsp 4464 2009-08-10 19:59 /var/spool/mqueue/dfn7B2xjPx014582
-rw------- 1 root smmsp 784 2009-08-10 19:59 /var/spool/mqueue/Qfn7B2xjPx014582
-rw------- 1 root smmsp 892 2009-08-10 23:24 /var/spool/mqueue/Qfn7B6OkhG013603
-rw------- 1 root smmsp 6160 2009-08-10 20:05 /var/spool/mqueue/dfn7B35ZvD015464
-rw------- 1 root smmsp 5437 2009-08-10 20:01 /var/spool/mqueue/dfn7B31ZQI014940
-rw------- 1 root smmsp 829 2009-08-10 20:05 /var/spool/mqueue/Qfn7B35ZvD015464
-rw------- 1 root smmsp 5233 2009-08-10 20:01 /var/spool/mqueue/dfn7B31bRE014929
-rw------- 1 root smmsp 877 2009-08-10 20:01 /var/spool/mqueue/Qfn7B31ZQI014940
-rw------- 1 root smmsp 3504 2009-08-10 20:07 /var/spool/mqueue/dfn7B37VlI015882
-rw------- 1 root smmsp 779 2009-08-10 20:07 /var/spool/mqueue/Qfn7B37VlI015882
-rw------- 1 root smmsp 3409 2009-08-10 20:07 /var/spool/mqueue/dfn7B37mw8015908
-rw------- 1 root smmsp 802 2009-08-10 20:07 /var/spool/mqueue/Qfn7B37mw8015908
-rw------- 1 root smmsp 4323 2009-08-11 01:16 /var/spool/mqueue/dfn7B8Gd7p031523
-rw------- 1 root smmsp 5589 2009-08-11 00:49 /var/spool/mqueue/dfn7B7nS5Z027480
-rw------- 1 root smmsp 814 2009-08-11 00:49 /var/spool/mqueue/Qfn7B7nS5Z027480
-rw------- 1 root smmsp 852 2009-08-11 01:16 /var/spool/mqueue/Qfn7B8Gd7p031523
-rw------- 1 root smmsp 832 2009-08-11 18:37 /var/spool/mqueue/Qfn7C1bPeV018193
-rw------- 1 root smmsp 2410 2009-08-11 19:23 /var/spool/mqueue/dfn7C2NwhM027036
-rw------- 1 root smmsp 781 2009-08-11 19:23 /var/spool/mqueue/Qfn7C2NwhM027036
-rw------- 1 root smmsp 5218 2009-08-11 21:37 /var/spool/mqueue/dfn7C4bOW5018745
-rw------- 1 root smmsp 811 2009-08-11 21:37 /var/spool/mqueue/Qfn7C4bOW5018745
-rw------- 1 root smmsp 3292 2009-08-11 23:01 /var/spool/mqueue/dfn7C61II4000642
-rw------- 1 root smmsp 802 2009-08-11 23:01 /var/spool/mqueue/Qfn7C61II4000642
-rw------- 1 root smmsp 19727000 2009-08-12 14:28 /var/spool/mqueue/dfn7CLSPkk029793
-rw------- 1 root smmsp 738 2009-08-12 14:28 /var/spool/mqueue/Qfn7CLSPkk029793
-rw------- 1 root smmsp 7823 2009-08-12 04:53 /var/spool/mqueue/dfn7CBrPM9023368
-rw------- 1 root smmsp 799 2009-08-12 04:53 /var/spool/mqueue/Qfn7CBrPM9023368
-rw------- 1 root smmsp 3515 2009-08-12 01:08 /var/spool/mqueue/dfn7C886kB021712
-rw------- 1 root smmsp 829 2009-08-12 01:08 /var/spool/mqueue/Qfn7C886kB021712
-rw------- 1 root smmsp 3506 2009-08-12 06:02 /var/spool/mqueue/dfn7CD2COG001711
-rw------- 1 root smmsp 779 2009-08-12 06:02 /var/spool/mqueue/Qfn7CD2COG001711
-rw------- 1 root smmsp 2546 2009-08-12 06:26 /var/spool/mqueue/dfn7CDQXcw005775
-rw------- 1 root smmsp 775 2009-08-12 06:26 /var/spool/mqueue/Qfn7CDQXcw005775
-rw------- 1 root smmsp 3911 2009-08-12 01:08 /var/spool/mqueue/dfn7C88KkB021722
-rw------- 1 root smmsp 2407 2009-08-12 07:31 /var/spool/mqueue/dfn7CEVkSw017569
-rw------- 1 root smmsp 2400 2009-08-12 09:01 /var/spool/mqueue/dfn7CG1AJu003656
-rw------- 1 root smmsp 1988 2009-08-12 20:04 /var/spool/mqueue/dfn7D346d8001850
-rw------- 1 root smmsp 838 2009-08-12 20:04 /var/spool/mqueue/Qfn7D346d8001850
-rw------- 1 root smmsp 5358 2009-08-12 20:21 /var/spool/mqueue/dfn7D3L3m4004728
-rw------- 1 root smmsp 835 2009-08-12 20:21 /var/spool/mqueue/Qfn7D3L3m4004728
-rw------- 1 root smmsp 2452 2009-08-12 21:33 /var/spool/mqueue/dfn7D4XPAN016798
-rw------- 1 root smmsp 853 2009-08-12 21:33 /var/spool/mqueue/Qfn7D4XPAN016798
-rw------- 1 root smmsp 1703 2009-08-12 21:48 /var/spool/mqueue/dfn7D4mB0x019963
-rw------- 1 root smmsp 830 2009-08-12 21:48 /var/spool/mqueue/Qfn7D4mB0x019963
-rw------- 1 root smmsp 5432 2009-08-13 06:14 /var/spool/mqueue/dfn7DDEQn5001106
-rw------- 1 root smmsp 4362 2009-08-13 05:20 /var/spool/mqueue/dfn7DCK9oO025435
-rw------- 1 root smmsp 2098 2009-08-12 21:58 /var/spool/mqueue/dfn7D4wOV0022012
-rw------- 1 root smmsp 862 2009-08-12 21:58 /var/spool/mqueue/Qfn7D4wOV0022012
-rw------- 1 root smmsp 2164 2009-08-12 21:56 /var/spool/mqueue/dfn7D4uE8s021376
-rw------- 1 root smmsp 859 2009-08-12 21:56 /var/spool/mqueue/Qfn7D4uE8s021376
-rw------- 1 root smmsp 1740 2009-08-12 22:31 /var/spool/mqueue/dfn7D5V0Iw028582
-rw------- 1 root smmsp 830 2009-08-12 22:31 /var/spool/mqueue/Qfn7D5V0Iw028582
-rw------- 1 root smmsp 886 2009-08-13 05:20 /var/spool/mqueue/Qfn7DCK9oO025435
-rw------- 1 root smmsp 968 2009-08-17 23:10 /var/spool/mqueue/Qfn7H988OA019451
-rw------- 1 root smmsp 2090 2009-08-12 22:52 /var/spool/mqueue/dfn7D5qkfH000844
-rw------- 1 root smmsp 1924 2009-08-13 00:01 /var/spool/mqueue/dfn7D71AQj012496
-rw------- 1 root smmsp 2172 2009-08-13 00:55 /var/spool/mqueue/dfn7D7tOq7020345
-rw------- 1 root smmsp 805 2009-08-13 00:55 /var/spool/mqueue/Qfn7D7tOq7020345
-rw------- 1 root smmsp 2070 2009-08-12 22:53 /var/spool/mqueue/dfn7D5r5gJ000929
-rw------- 1 root smmsp 844 2009-08-12 22:53 /var/spool/mqueue/Qfn7D5r5gJ000929
-rw------- 1 root smmsp 805 2009-08-13 09:01 /var/spool/mqueue/Qfn7DG1k60001806
-rw------- 1 root smmsp 21142 2009-08-13 10:07 /var/spool/mqueue/dfn7DH7bRw022032
-rw------- 1 root smmsp 793 2009-08-13 10:07 /var/spool/mqueue/Qfn7DH7bRw022032
-rw------- 1 root smmsp 821 2009-08-13 12:24 /var/spool/mqueue/Qfn7DJOZiX027736
-rw------- 1 root smmsp 17240 2009-08-13 13:11 /var/spool/mqueue/dfn7DKBIMt006875
-rw------- 1 root smmsp 1666 2009-08-13 12:24 /var/spool/mqueue/dfn7DJOZiX027736
-rw------- 1 root smmsp 961 2009-08-18 12:57 /var/spool/mqueue/Qfn7DKBIMt006875
-rw------- 1 root smmsp 2585 2009-08-13 13:21 /var/spool/mqueue/dfn7DKL5Bq009332
-rw------- 1 root smmsp 961 2009-08-15 12:17 /var/spool/mqueue/Qfn7AK6YqU020847
-rw------- 1 root smmsp 3724 2009-08-13 13:27 /var/spool/mqueue/dfn7DKRHBj010761
-rw------- 1 root smmsp 811 2009-08-13 13:27 /var/spool/mqueue/Qfn7DKRHBj010761
-rw------- 1 root smmsp 3093 2009-08-13 13:30 /var/spool/mqueue/dfn7DKUwEf011816
-rw------- 1 root smmsp 820 2009-08-13 13:30 /var/spool/mqueue/Qfn7DKUwEf011816
-rw------- 1 root smmsp 3668 2009-08-13 13:53 /var/spool/mqueue/dfn7DKrOx3017152
-rw------- 1 root smmsp 734 2009-08-13 13:53 /var/spool/mqueue/Qfn7DKrOx3017152
-rw------- 1 root smmsp 4523 2009-08-13 19:27 /var/spool/mqueue/dfn7E2R8CT029504
-rw------- 1 root smmsp 874 2009-08-13 19:27 /var/spool/mqueue/Qfn7E2R8CT029504
-rw------- 1 root smmsp 4189 2009-08-13 17:07 /var/spool/mqueue/dfn7E07rH0006236
-rw------- 1 root smmsp 779 2009-08-13 17:07 /var/spool/mqueue/Qfn7E07rH0006236
-rw------- 1 root smmsp 2578 2009-08-13 20:35 /var/spool/mqueue/dfn7E3ZjFq007772
-rw------- 1 root smmsp 963 2009-08-20 20:32 /var/spool/mqueue/Qfn7KNoObB021343
-rw------- 1 root smmsp 3809 2009-08-13 23:09 /var/spool/mqueue/dfn7E69ifg031105
-rw------- 1 root smmsp 820 2009-08-13 23:09 /var/spool/mqueue/Qfn7E69ifg031105
-rw------- 1 root smmsp 3652 2009-08-14 06:01 /var/spool/mqueue/dfn7ED1kob029666
-rw------- 1 root smmsp 2259 2009-08-14 15:48 /var/spool/mqueue/dfn7EMmJDf012702
-rw------- 1 root smmsp 1704 2009-08-14 10:34 /var/spool/mqueue/dfn7EHYPGf022841
-rw------- 1 root smmsp 732 2009-08-14 15:48 /var/spool/mqueue/Qfn7EMmJDf012702
-rw------- 1 root smmsp 7493 2009-08-14 10:10 /var/spool/mqueue/dfn7EHADJr016314
-rw------- 1 root smmsp 790 2009-08-14 10:10 /var/spool/mqueue/Qfn7EHADJr016314
-rw------- 1 root smmsp 4714 2009-08-14 17:11 /var/spool/mqueue/dfn7F0BoN2031074
-rw------- 1 root smmsp 1803 2009-08-14 12:47 /var/spool/mqueue/dfn7EJlJYC030212
-rw------- 1 root smmsp 853 2009-08-14 12:47 /var/spool/mqueue/Qfn7EJlJYC030212
-rw------- 1 root smmsp 1635 2009-08-19 21:36 /var/spool/mqueue/dfn7K4a8PT016512
-rw------- 1 root smmsp 2046 2009-08-14 16:29 /var/spool/mqueue/dfn7ENTF08021883
-rw------- 1 root smmsp 805 2009-08-14 17:11 /var/spool/mqueue/Qfn7F0BoN2031074
-rw------- 1 root smmsp 946 2009-08-25 12:49 /var/spool/mqueue/Qfn7KKCirI032338
-rw------- 1 root smmsp 1230 2009-08-14 21:28 /var/spool/mqueue/Qfn7F4SDtf011370
-rw------- 1 root smmsp 2168 2009-08-14 16:29 /var/spool/mqueue/dfn7ENTKdq021898
-rw------- 1 root smmsp 802 2009-08-14 16:29 /var/spool/mqueue/Qfn7ENTKdq021898
-rw------- 1 root smmsp 1679 2009-08-20 12:55 /var/spool/mqueue/dfn7KJtX1o026662
-rw------- 1 root smmsp 778 2009-08-14 21:06 /var/spool/mqueue/Qfn7F46gvh006921
-rw------- 1 root smmsp 4978 2009-08-14 20:07 /var/spool/mqueue/dfn7F376wk027503
-rw------- 1 root smmsp 799 2009-08-14 20:07 /var/spool/mqueue/Qfn7F376wk027503
-rw------- 1 root smmsp 835 2009-08-15 11:57 /var/spool/mqueue/Qfn7FIvuqJ023700
-rw------- 1 root smmsp 993 2009-08-17 11:21 /var/spool/mqueue/Qfn7HIKFWS028802
-rw------- 1 root smmsp 7901 2009-08-16 08:11 /var/spool/mqueue/dfn7GFBR60009130
-rw------- 1 root smmsp 3433 2009-08-16 08:04 /var/spool/mqueue/dfn7GF45dr008248
-rw------- 1 root smmsp 793 2009-08-16 08:11 /var/spool/mqueue/Qfn7GFBR60009130
-rw------- 1 root smmsp 2069 2009-08-16 14:19 /var/spool/mqueue/dfn7GLJNIc000976
-rw------- 1 root smmsp 823 2009-08-16 14:19 /var/spool/mqueue/Qfn7GLJNIc000976
-rw------- 1 root smmsp 980 2009-08-17 23:10 /var/spool/mqueue/Qfn7H7ixRu004112
-rw------- 1 root smmsp 2123 2009-08-16 14:32 /var/spool/mqueue/dfn7GLWcSU003650
-rw------- 1 root smmsp 2687 2009-08-16 14:40 /var/spool/mqueue/dfn7GLeZbK005081
-rw------- 1 root smmsp 877 2009-08-16 14:40 /var/spool/mqueue/Qfn7GLeZbK005081
-rw------- 1 root smmsp 970 2009-08-21 14:28 /var/spool/mqueue/Qfn7LBKcmi001794
-rw------- 1 root smmsp 2191 2009-08-16 14:32 /var/spool/mqueue/dfn7GLWe34003685
-rw------- 1 root smmsp 1842 2009-08-16 14:40 /var/spool/mqueue/dfn7GLex7t005205
-rw------- 1 root smmsp 856 2009-08-16 14:40 /var/spool/mqueue/Qfn7GLex7t005205
-rw------- 1 root smmsp 2909 2009-08-16 15:08 /var/spool/mqueue/dfn7GM8kpw010900
-rw------- 1 root smmsp 799 2009-08-16 15:08 /var/spool/mqueue/Qfn7GM8kpw010900
-rw------- 1 root smmsp 2907 2009-08-16 15:09 /var/spool/mqueue/dfn7GM9uJv011096
-rw------- 1 root smmsp 799 2009-08-16 15:09 /var/spool/mqueue/Qfn7GM9uJv011096
-rw------- 1 root smmsp 2058 2009-08-17 11:46 /var/spool/mqueue/dfn7HIkDNw004055
-rw------- 1 root smmsp 799 2009-08-18 09:33 /var/spool/mqueue/Qfn7IGXt0b027853
-rw------- 1 root smmsp 3854 2009-08-16 16:28 /var/spool/mqueue/dfn7GNSGkv023768
-rw------- 1 root smmsp 861 2009-08-16 16:28 /var/spool/mqueue/Qfn7GNSGkv023768
-rw------- 1 root smmsp 835 2009-08-17 01:14 /var/spool/mqueue/Qfn7H8EVt4010017
-rw------- 1 root smmsp 2437 2009-08-17 01:13 /var/spool/mqueue/dfn7H8DBqt009604
-rw------- 1 root smmsp 847 2009-08-17 01:13 /var/spool/mqueue/Qfn7H8DBqt009604
-rw------- 1 root smmsp 2100 2009-08-17 01:31 /var/spool/mqueue/dfn7H8VD6Q013576
-rw------- 1 root smmsp 865 2009-08-17 01:31 /var/spool/mqueue/Qfn7H8VD6Q013576
-rw------- 1 root smmsp 2226 2009-08-17 01:36 /var/spool/mqueue/dfn7H8a5EH014367
-rw------- 1 root smmsp 853 2009-08-17 01:36 /var/spool/mqueue/Qfn7H8a5EH014367
-rw------- 1 root smmsp 2182 2009-08-17 01:37 /var/spool/mqueue/dfn7H8bCPQ014526
-rw------- 1 root smmsp 859 2009-08-17 01:37 /var/spool/mqueue/Qfn7H8bCPQ014526
-rw------- 1 root smmsp 1693 2009-08-17 02:08 /var/spool/mqueue/dfn7H988OA019451
-rw------- 1 root smmsp 968 2009-08-18 06:15 /var/spool/mqueue/Qfn7H64IJ0017744
-rw------- 1 root smmsp 1700 2009-08-17 03:53 /var/spool/mqueue/dfn7HArwuX002998
-rw------- 1 root smmsp 943 2009-08-19 06:53 /var/spool/mqueue/Qfn7EDxr07006896
-rw------- 1 root smmsp 3619 2009-08-17 05:52 /var/spool/mqueue/dfn7HCqFVa020636
-rw------- 1 root smmsp 779 2009-08-17 05:52 /var/spool/mqueue/Qfn7HCqFVa020636
-rw------- 1 root smmsp 11482 2009-08-17 08:13 /var/spool/mqueue/dfn7HFD3LQ012534
-rw------- 1 root smmsp 793 2009-08-17 08:13 /var/spool/mqueue/Qfn7HFD3LQ012534
-rw------- 1 root smmsp 3481 2009-08-17 09:25 /var/spool/mqueue/dfn7HGPcD4029282
-rw------- 1 root smmsp 779 2009-08-17 09:25 /var/spool/mqueue/Qfn7HGPcD4029282
-rw------- 1 root smmsp 975 2009-08-23 01:52 /var/spool/mqueue/Qfn7MN30rw019400
-rw------- 1 root smmsp 836 2009-08-20 07:57 /var/spool/mqueue/Qfn7KEvwFv013875
-rw------- 1 root smmsp 3847 2009-08-20 03:52 /var/spool/mqueue/dfn7KAqJIo007136
-rw------- 1 root smmsp 802 2009-08-20 03:52 /var/spool/mqueue/Qfn7KAqJIo007136
-rw------- 1 root smmsp 1725 2009-08-20 08:27 /var/spool/mqueue/dfn7KFRG80019343




[root@pot mqueue]# find /var/spool/mqueue -mtime +1 -exec ls -l {} \;
[root@pot mqueue]# find /var/spool/mqueue -mtime +1 -exec rm {} \;


[root@pot mqueue]# ll
total 19048
drwxr-xr-x 2 root mail 241664 2009-09-09 10:45 ./
drwxr-xr-x 6 root root 8192 2009-09-08 10:41 ../
-rw------- 1 root smmsp 937 2009-09-07 13:29 Qfn82LiDjA012825
-rw------- 1 root smmsp 873 2009-09-07 18:29 Qfn832XASB009701
-rw------- 1 root smmsp 893 2009-09-07 20:59 Qfn8349F0c024789
-rw------- 1 root smmsp 933 2009-09-08 04:28 Qfn83BbnJF025245
-rw------- 1 root smmsp 960 2009-09-08 20:24 Qfn844TlMJ017477
-rw------- 1 root smmsp 894 2009-09-09 04:20 Qfn84BVod7013586
-rw------- 1 root smmsp 846 2009-09-09 08:06 Qfn84FFPUA016086
-rw------- 1 root smmsp 957 2009-09-09 07:39 Qfn84FrtWd023965
-rw------- 1 root smmsp 870 2009-09-07 11:23 Qfn858pwHv003138
-rw------- 1 root smmsp 984 2009-09-07 11:23 Qfn861BimA005433
-rw------- 1 root smmsp 732 2009-09-07 10:58 Qfn87Hw8Ej016301
-rw------- 1 root smmsp 852 2009-09-08 17:28 Qfn87IMh8R021199
-rw------- 1 root smmsp 830 2009-09-07 14:50 Qfn87Lo7mZ029723
-rw------- 1 root smmsp 966 2009-09-08 14:08 Qfn87MUHmO005276
-rw------- 1 root smmsp 966 2009-09-08 13:18 Qfn881aqeR003540
-rw------- 1 root smmsp 852 2009-09-08 17:28 Qfn88382Jl020169
-rw------- 1 root smmsp 785 2009-09-07 22:02 Qfn8852USc007108
-rw------- 1 root smmsp 818 2009-09-08 00:07 Qfn8877e7t028972
-rw------- 1 root smmsp 830 2009-09-08 00:07 Qfn8877g1h028979
-rw------- 1 root smmsp 851 2009-09-08 00:45 Qfn887jSWh003020
-rw------- 1 root smmsp 966 2009-09-08 17:28 Qfn888Gkuf008249
-rw------- 1 root smmsp 836 2009-09-08 01:45 Qfn888jgGs013304
-rw------- 1 root smmsp 851 2009-09-08 01:59 Qfn888xRKm015653
-rw------- 1 root smmsp 818 2009-09-08 01:59 Qfn888xRKm015663
-rw------- 1 root smmsp 812 2009-09-08 01:59 Qfn888xYKm015698
-rw------- 1 root smmsp 812 2009-09-08 02:07 Qfn8897rqS016976
-rw------- 1 root smmsp 824 2009-09-08 02:07 Qfn8897tqS016999
-rw------- 1 root smmsp 815 2009-09-08 02:22 Qfn889MgNG019595
-rw------- 1 root smmsp 815 2009-09-08 06:19 Qfn88DJPqq028889
-rw------- 1 root smmsp 818 2009-09-08 06:54 Qfn88DsOFx003182
-rw------- 1 root smmsp 777 2009-09-08 07:25 Qfn88EP0sp008882
-rw------- 1 root smmsp 806 2009-09-08 07:45 Qfn88EjhUe013582
-rw------- 1 root smmsp 809 2009-09-08 07:46 Qfn88Ek3Ue013727
-rw------- 1 root smmsp 782 2009-09-08 07:46 Qfn88EkEjl013774
-rw------- 1 root smmsp 809 2009-09-08 07:46 Qfn88EkLUe013813
-rw------- 1 root smmsp 788 2009-09-08 07:46 Qfn88EkOjl013816
-rw------- 1 root smmsp 785 2009-09-08 08:57 Qfn88FvSiD031304
-rw------- 1 root smmsp 813 2009-09-08 11:03 Qfn88I3wQS007147
-rw------- 1 root smmsp 803 2009-09-08 11:55 Qfn88ItIZk025833
-rw------- 1 root smmsp 825 2009-09-08 12:22 Qfn88JMWIQ002951
-rw------- 1 root smmsp 804 2009-09-08 13:01 Qfn88K17Au014434
-rw------- 1 root smmsp 969 2009-09-08 13:29 Qfn88KTGnC022975
-rw------- 1 root smmsp 813 2009-09-08 14:31 Qfn88LVUtR010845
-rw------- 1 root smmsp 818 2009-09-08 16:44 Qfn88NihXL018861
-rw------- 1 root smmsp 821 2009-09-08 18:03 Qfn8913HSg005245
-rw------- 1 root smmsp 809 2009-09-08 18:03 Qfn8913iSg005561
-rw------- 1 root smmsp 797 2009-09-08 18:03 Qfn8913nSg005583
-rw------- 1 root smmsp 856 2009-09-08 23:18 Qfn891Bicc006970
-rw------- 1 root smmsp 812 2009-09-08 18:23 Qfn891NmBk009391
-rw------- 1 root smmsp 791 2009-09-08 18:25 Qfn891PM33009734
-rw------- 1 root smmsp 959 2009-09-08 22:54 Qfn893Sx5f002227
-rw------- 1 root smmsp 970 2009-09-08 23:18 Qfn893phXG006589
-rw------- 1 root smmsp 842 2009-09-08 22:08 Qfn8958jLO021580
-rw------- 1 root smmsp 794 2009-09-08 23:15 Qfn896FeoJ001570
-rw------- 1 root smmsp 777 2009-09-09 00:06 Qfn8976ehR011939
-rw------- 1 root smmsp 803 2009-09-09 00:57 Qfn897vQpJ021122
-rw------- 1 root smmsp 809 2009-09-09 04:37 Qfn89BbUFf028318
-rw------- 1 root smmsp 777 2009-09-09 04:56 Qfn89BuYhZ032017
-rw------- 1 root smmsp 845 2009-09-09 05:05 Qfn89C51CG001515
-rw------- 1 root smmsp 881 2009-09-09 07:49 Qfn89EnfOG004330
-rw------- 1 root smmsp 777 2009-09-09 08:07 Qfn89F7AUR008492
-rw------- 1 root smmsp 855 2009-09-09 08:16 Qfn89FG0iR010692
-rw------- 1 root smmsp 804 2009-09-09 10:35 Qfn89HZh6p021575
-rw------- 1 root smmsp 9564 2009-09-07 10:58 dfn87Hw8Ej016301
-rw------- 1 root smmsp 1653 2009-09-07 11:22 dfn87IMh8R021199
-rw------- 1 root smmsp 2222 2009-09-07 14:50 dfn87Lo7mZ029723
-rw------- 1 root smmsp 1665 2009-09-07 15:30 dfn87MUHmO005276
-rw------- 1 root smmsp 3177 2009-09-07 15:50 dfn87MoI4n009310
-rw------- 1 root smmsp 1653 2009-09-07 18:36 dfn881aqeR003540
-rw------- 1 root smmsp 1670 2009-09-07 20:08 dfn88382Jl020169
-rw------- 1 root smmsp 16354 2009-09-07 22:02 dfn8852USc007108
-rw------- 1 root smmsp 7008 2009-09-08 00:07 dfn8877e7t028972
-rw------- 1 root smmsp 6983 2009-09-08 00:07 dfn8877g1h028979
-rw------- 1 root smmsp 9787 2009-09-08 00:45 dfn887jSWh003020
-rw------- 1 root smmsp 1663 2009-09-08 01:16 dfn888Gkuf008249
-rw------- 1 root smmsp 3474 2009-09-08 01:45 dfn888jgGs013304
-rw------- 1 root smmsp 3984 2009-09-08 01:59 dfn888xRKm015653
-rw------- 1 root smmsp 3542 2009-09-08 01:59 dfn888xRKm015663
-rw------- 1 root smmsp 3716 2009-09-08 01:59 dfn888xYKm015698
-rw------- 1 root smmsp 7812 2009-09-08 02:07 dfn8897rqS016976
-rw------- 1 root smmsp 8247 2009-09-08 02:07 dfn8897tqS016999
-rw------- 1 root smmsp 4591 2009-09-08 02:22 dfn889MgNG019595
-rw------- 1 root smmsp 3873 2009-09-08 06:19 dfn88DJPqq028889
-rw------- 1 root smmsp 3467 2009-09-08 06:54 dfn88DsOFx003182
-rw------- 1 root smmsp 3501 2009-09-08 07:25 dfn88EP0sp008882
-rw------- 1 root smmsp 3618 2009-09-08 07:45 dfn88EjhUe013582
-rw------- 1 root smmsp 1666 2009-09-08 07:45 dfn88Ejogt013624
-rw------- 1 root smmsp 4792 2009-09-08 07:46 dfn88Ek3Ue013727
-rw------- 1 root smmsp 3903 2009-09-08 07:46 dfn88EkEjl013774
-rw------- 1 root smmsp 3995 2009-09-08 07:46 dfn88EkLUe013813
-rw------- 1 root smmsp 3529 2009-09-08 07:46 dfn88EkOjl013816
-rw------- 1 root smmsp 1656 2009-09-08 08:05 dfn88F5dqX018415
-rw------- 1 root smmsp 7769 2009-09-08 08:57 dfn88FvSiD031304
-rw------- 1 root smmsp 1683 2009-09-08 09:31 dfn88GVP9J009581
-rw------- 1 root smmsp 1664 2009-09-08 10:19 dfn88HJMx9025290
-rw------- 1 root smmsp 1682 2009-09-08 11:03 dfn88I3wQS007147
-rw------- 1 root smmsp 3351 2009-09-08 16:44 dfn88NihXL018861
-rw------- 1 root smmsp 1676 2009-09-08 17:06 dfn89062bu024410
-rw------- 1 root smmsp 1676 2009-09-08 17:43 dfn890hYdm000703
-rw------- 1 root smmsp 3982 2009-09-08 18:03 dfn8913HSg005245
-rw------- 1 root smmsp 3887 2009-09-08 18:03 dfn8913iSg005561
-rw------- 1 root smmsp 3831 2009-09-08 18:03 dfn8913nSg005583
-rw------- 1 root smmsp 1676 2009-09-08 18:11 dfn891Bicc006970
-rw------- 1 root smmsp 3511 2009-09-09 00:06 dfn8976ehR011939
-rw------- 1 root smmsp 3649 2009-09-09 00:57 dfn897vQpJ021122
-rw------- 1 root smmsp 12598 2009-09-09 04:37 dfn89BbUFf028318
-rw------- 1 root smmsp 4918 2009-09-09 04:56 dfn89BuYhZ032017
-rw------- 1 root smmsp 6564 2009-09-09 05:05 dfn89C51CG001515
-rw------- 1 root smmsp 109 2009-09-09 05:55 dfn89Ct8np010685
-rw------- 1 root smmsp 101 2009-09-09 06:45 dfn89Dj8D2020437
-rw------- 1 root smmsp 116 2009-09-09 06:45 dfn89Dj8D4020437
-rw------- 1 root smmsp 116 2009-09-09 06:45 dfn89Dj8D6020437
-rw------- 1 root smmsp 104 2009-09-09 07:10 dfn89EA8FQ026864
-rw------- 1 root smmsp 2165 2009-09-09 07:49 dfn89EnfOG004330
-rw------- 1 root smmsp 3499 2009-09-09 08:07 dfn89F7AUR008492
-rw------- 1 root smmsp 1735 2009-09-09 08:16 dfn89FG0iR010692
-rw------- 1 root smmsp 916 2009-09-09 09:59 qfn84I8hkR028807
-rw------- 1 root smmsp 916 2009-09-09 09:36 qfn84JCqWN015776
-rw------- 1 root smmsp 916 2009-09-09 09:35 qfn84KIXIu032106
-rw------- 1 root smmsp 916 2009-09-09 09:35 qfn84LS2If018005
-rw------- 1 root smmsp 943 2009-09-09 10:25 qfn86329JO023341
-rw------- 1 root smmsp 873 2009-09-09 09:35 qfn867O97Q004423
-rw------- 1 root smmsp 960 2009-09-09 09:59 qfn86KBoh1018737
-rw------- 1 root smmsp 916 2009-09-09 10:25 qfn86KW9IF023968
-rw------- 1 root smmsp 1107 2009-09-09 10:24 qfn89Dj8D2020437
-rw------- 1 root smmsp 1127 2009-09-09 10:24 qfn89Dj8D4020437
-rw------- 1 root smmsp 1130 2009-09-09 10:24 qfn89Dj8D6020437
-rw------- 1 root smmsp 1126 2009-09-09 09:34 qfn89EA8FQ026864
-rw------- 1 root smmsp 908 2009-09-09 09:52 qfn89GZ5cX000590
-rw------- 1 root smmsp 1474 2009-09-09 10:21 qfn89HLUAI016593
-rw------- 1 root smmsp 1691 2009-09-09 10:45 qfn89HjWCC029618

[root@potato2 mqueue]# ll|wc -l
177




[root@webma clientmqueue]# find /var/spool/clientmqueue -mtime +1 -exec ls -l {} \;
[root@webma clientmqueue]# find /var/spool/clientmqueue -mtime +1 -exec rm -r {} \;

Tuesday, September 8, 2009

PHP magic_quotes_gpc

SkyHi @ Tuesday, September 08, 2009
PhpSecInfo Test Information

magic_quotes_gpc

Test Description

Determines if magic_quotes_gpc is enabled.
Security Implications

The magic quotes option was introduced to help protect developers from SQL injection attacks. It effectively executes addslashes() on all information received over GET, POST or COOKIE. Unfortunately this protection isn't perfect: there are a series of other characters that databases interpret as special not covered by this function. In addition, data not sent direct to databases must un-escaped before it can be used.

Recommendations

Because it's inconsistent and ineffective, it's not recommended that magic_quotes_gpc be enabled. Rely on input filtering done by your scripts.

You can disable magic_quotes_gpc in the php.ini file:

; Disable magic_quotes_gpc
magic_quotes_gpc = 'off'

The setting can also be disabled in apache's httpd.conf file, or an .htaccess file:

# Disable magic_quotes_gpc
php_flag magic_quotes_gpc off



things that should always be turned off in php.ini on a live system
register_globals
allow_url_fopen
display_errors
magic_quotes_gpc



Reference: http://phpsec.org/projects/phpsecinfo/tests/magic_quotes_gpc.html


http://www.webmasterworld.com/forum88/8688.htm

Sunday, September 6, 2009

LINUX DATA MANIPULATION cut

SkyHi @ Sunday, September 06, 2009
Consider a slight variation on the company.data file we've been playing with in this section:

406378:Sales:Itorre:Jan
031762:Marketing:Nasium:Jim
636496:Research:Ancholie:Mel
396082:Sales:Jucacion:Ed

If you want to print just columns 1 to 6 of each line (the employee serial numbers), use the -c1-6 flag, as in this command:

cut -c1-6 company.data
406378
031762
636496
396082

If you want to print just columns 4 and 8 of each line (the first letter of the department and the fourth digit of the serial number), use the -c4,8 flag, as in this command:

cut -c4,8 company.data
3S
7M
4R
0S

And since this file obviously has fields delimited by colons, we can pick out just the last names by specifying the -d: and -f3 flags, like this:

cut -d: -f3 company.data
Itorre
Nasium
Ancholie
Jucacion

Here is a summary of the most common flags for the cut command:

-c [n | n,m | n-m] Specify a single column, multiple columns (separated by a comma), or range of columns (separated by a dash).
-f [n | n,m | n-m] Specify a single field, multiple fields (separated by a comma), or range of fields (separated by a dash).
-dc Specify the field delimiter.
-s Suppress (don't print) lines not containing the delimiter.

Reference: http://lowfatlinux.com/linux-columns-cut.html