MS Access Long Date to Word Short Date

Microsoft office word have trouble at this day, when i trying to make mail merge from word with access database and i've got a small problem with date. How it's can be? The Problem is from microsoft office word 2007 that can't read long date from access, word translate long date to short date.

How i can resolve this problem? first time, i had ask my friend, why this problem can do? my friend just tell, hah.. it's a small bug from office, try to search at microsoft forum. After that i trying to search at Internet with my best friend (google is my best friend to learn something that i don't know because google is more smart from me, hehehe) with google i found a problem resolve.

MS Access Long Date to Word Short Date problem resolve :

Open your word document that have short date problem :
1. select the mergefield;
2. press Shift-F9 to expose the field coding. It should look something like {MERGEFIELD YourDate} where 'YourDate' is your mergefield's name;
3. After the mergefield's name you must add \@ "d MMMM yyyy" to the field, as in {MERGEFIELD MyDate \@ "d MMMM yyyy"}.
4. With this switch your date will come out like '2 August 2008'. Other possible date formatting switches include :
a. \@ "dddd, d MMMM yyyy"
b. \@ "ddd, d MMMM yyyy"
c. \@ "d MMM yyyy"
d. \@ "dd/MMM/yyyy"
. \@ "d-MM-yy";

Note: you can swap the d, M, y expressions around, but you must use uppercase 'M's for months - lowercase 'm's are for minutes.

5. position the cursor anywhere in this field and press F9 to update it;
6. run your mailmerge.

Have a fun with your long date mailmerge in the word without a problem.

Read full articles story »»  

Active detect and close network linux redhat ports

Most important tasks is to detect and close network ports that are needed.

To get a list of listening network ports (TCP and UDP sockets), you can run the following command:

# netstat -tulp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
tcp        0      0 *:auth                      *:*                         LISTEN      2328/xinetd
tcp        0      0 localhost.localdomain:smtp  *:*                         LISTEN      2360/sendmail: acce
tcp        0      0 *:ssh                       *:*                         LISTEN      2317/sshd

From the output you can see that xinetd, sendmail, and sshd are listening.

On all newer Red Hat Linux distributions sendmail is configured to listen for local connections only. Sendmail should not listen for incoming network connections unless the server is a mail or relay server. Running a port scan from another server will confirm that (make sure that you have permissions to probe a machine):

# nmap -sTU 

Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2004-12-10 22:51 CST
Interesting ports on jupitor (172.16.0.1):
(The 3131 ports scanned but not shown below are in state: closed)
PORT    STATE         SERVICE
22/tcp  open          ssh
113/tcp open          auth

Nmap run completed -- 1 IP address (1 host up) scanned in 221.669 seconds
#

Note that the above nmap command can take a while. If you remove the UDP port scan (without the option "-U"), then nmap will finish the port scan immediately. If you run it on the local machine it will also complete very fast. Also note that nmap might not show all listening network sockets if a firewall is being used to block ports.
From the output above you can see that the xinetd daemon is listening on port auth (port 113) for IDENT (for more information on this service, see below). You can also see that sendmail is not listening for remote incoming network connections, see also Securing Sendmail.

Another method to list all of the TCP and UDP sockets to which programs are listening is lsof:

# lsof -i -n | egrep 'COMMAND|LISTEN|UDP'
COMMAND    PID USER   FD   TYPE DEVICE SIZE NODE NAME
sshd      2317 root    3u  IPv6   6579       TCP *:ssh (LISTEN)
xinetd    2328 root    5u  IPv4   6698       TCP *:auth (LISTEN)
sendmail  2360 root    3u  IPv4   6729       TCP 127.0.0.1:smtp (LISTEN)
#

Read full articles story »»  

KSysguard Real-time Systems Reporting and Graph

 What is KSysguard ? This tool is a network enabled task and system monitor application for KDE desktop. This tool can be run over ssh session. It provides lots of features such as a client/server architecture that enables monitoring of local and remote hosts.

The graphical front end uses so-called sensors to retrieve the information it displays. A sensor can return simple values or more complex information like tables.

For each type of information, one or more displays are provided. Displays are organized in worksheets that can be saved and loaded independently from each other.

So, KSysguard is not only a simple task manager but also a very powerful tool to control large server farms.

See the KSysguard handbook for detailed usage.

Read full articles story »»