MP hanya menyediakan viewer history untuk member saja. jadi kita tidak tahu dengan pasti berapa banyak orang yang telah membaca Mp kita. dengan sedikit trik kita bisa mengakali agar kita tahu seberapa sering Mp kita diakses oleh temen, kolega, pacar, selingkuhan bahkan musuh kita (hehehe..... jadi inget kata cak nur tentang gus dur "satu kawan cukup seribu lawan kurang"). info yang kita dapet memang berupa Ip, jenis browser dan apa saja yang mereka akses di mp kita. tetapi jangan salah dengan IP kita bisa tahu lebih banyak.
untuk melakukan hal tersebut kita butuh pihak ketiga yang menyediakan layanan counter gratis dan kita akan menempelkan source code nya di MP kita.
step by step ( "NKOTB kali yeee')
1. register ke http://www.statcounter.com (dan ikutin aja apa mau nya namanya juga numpang dan gratis lagi)
2. bikin porject dari menu yang disediakan oleh statcounter (disini kita akan mendapatkan source code yang akan kita tempel di MP kita.
3 buka MP> custumize my site >
edit welcome page > paste source code dari statcounter di welcome massage > save
4 selesai sudah dan report dari statcount akan dikirim ke email per week.
so kita bisa lacak pengemar berat kita deh.
met mencoba . jika kurang paham silahkan tanya.
Tuesday, January 29, 2008
Setting SMTP server di SME Server
Jika sme server berada dibelakang firewall dan hanya punya satu card, maka set sme server sebagai "server only" dan masukkan gatewaynya pada ip firewall nya. trus masukkan juga ip name servicenya (ini biasanya kita ikut ISP saja). so... jadilah sme box kita sebagai SMTP server. semua jaringan internal kita bisa memanfaatkan smtp ini.
tambahan jika sme nya sudah running dan untuk measuk modus configurasi. silahkan login as user "admin"
selamat mencoba .......
tambahan jika sme nya sudah running dan untuk measuk modus configurasi. silahkan login as user "admin"
selamat mencoba .......
Tuesday, January 22, 2008
SME backup with DAR
What is e-smith-backup with dar ?
e-smith-backup with dar is an upgrade of current e-smith-backup sme core rpm which provides panels for daily full or incremental backup on LAN workstation (via nfs, smbfs or cifs) or local usb disk, and full or selective restore with use of dar program.
What provides e-smith-backup with dar ?
e-smith-backup with dar completes core e-smith-backup with four panels :
New backup options are provided with additional perl functions included in backup panel script, a new perl backup script /etc/e-smith/events/actions/workstation-backup-dar, and a new backupwk record in configuration db. All are written with the same logic as present backup scripts.
What are specific problems of SME Server LAN backups managed by e-smith with dar ?
With experience of more than four years backuping sme servers with dar on LAN workstations (in production environments) the most important of encountered problems is that, when the backup session is started, you cannot rely upon a perfect working of the LAN or the distant workstation.
Inevitably, one day the LAN is too busy and/or the connection to the distant share hacks. After the failure sme may keep zombies backup or mount processes, and with some contribs you can be left with incomplete or buggy backup until hopped next good daily backup. These problems are problems of real world with LAN, that backup scripts must take into account.
Another common problem with backup through a LAN is that your lan disponibility for backup flow is not 24/24, but more probably something like "only from 20h to 6h, except on sunday where nobody works on the LAN..." So in case of large volume of data to backup, beeing able to backup all the datas during the week-end and doing only incremental backup on the week days really makes sense.
All these problems are considered with e-smith-backup with dar.
Scripts verify the absence of old share mounts, and alert admin about such situation. Test is made that the distant backup share is available and writable. Of course with daily backup a maximum backup session time of only 24 h is available, but if this limit occurs e-smith-backup with dar cleanly stops the backup session (maybe all is ok and the backup has not enough time to complete), the lan share is unmounted, and daily process can restart anyway. If you have enabled incremental backup and the last backup (full or incremental) was not completed because of a timeout, the backup can then safely restart and complete in an incremental way.
The admin can also set a timeout limit which keeps the session inside a specified number of hours, excluding traffic of LAN backup sessions when users work on the LAN.
Admin user can also set backup configuration so that this time limit occurs only on incremental backup sets. Then if you have a lot of data and your full backup time exceeds time of LAN inactivity, you can always backup all your data each end of week and preserve LAN bandwith for users. If you program a full backup on saturday night, you get 24 hours to do full backup and even if the full backup time exceeds 24 hours, the first incremental backup on sunday night will backup remaining data. You begin your week with full data saved, and incremental backup session time is limited to 6 or 8 hours during week days.
Full backup sessions can also be allowed on every day, or limited to a specific day of week.
Are other new functions provided ?
Yes. Aside use of session timeout, the first is incremental backup.
This means that you can backup and restore data for the period of time you want : one day, three days, one week, one month, 100 days... and restore your system at any state it was during this period of time. This probably has no utility to do full restore of the system as it was one month ago, but restoring a file lost by a user two or three weeks ago can be useful. And restoring a safe system more than one day old can be needed.
The second function is keeping more than one set of backup (a set is full backup data and all datas of next daily incremental backups) with automatic rotation. e.g. you can do only nightly full backups but keep three sets of backup for security reason (as being able to restore the system as it was 72h ago).
The third function is selective restore of any backuped file or directory, exactly as it was for any of the backuped days in your sets. Not only you can restore a lost file at his last state, but also say : make restore of the most recent version of the file before this given date... Selective restore is not an easy thing to manage by hand, and providing this in a simple way with panels is useful. Dar permits to manage selective restore and e-smith-backup with dar panels tries to keep this function as simple as possible to use.
Where to find e-smith-backup with dar ?
Presently beta version of e-smith with dar can be uploaded at http://beta.free-eos.org/sme/RPMS/e-smith-backup-1.14.0-16eos1.el4.sme.noarch.rpm
SRPMS available at http://beta.free-eos.org/sme/RPMS/e-smith-backup-1.14.0-16eos1.el4.sme.src.rpm
Dar rpm is available at http://beta.free-eos.org/sme/RPMS/dar-2.3.2-1.i386.rpm or mirrored at http://mirror.contribs.org/smeserver/contribs/dmay/smeserver/7.x/dar-2.3.2-1.i386.rpm
e-smith-backup with dar is an upgrade of current e-smith-backup sme core rpm which provides panels for daily full or incremental backup on LAN workstation (via nfs, smbfs or cifs) or local usb disk, and full or selective restore with use of dar program.
What provides e-smith-backup with dar ?
e-smith-backup with dar completes core e-smith-backup with four panels :
- - configure daily full or incremental backup to smbfs/cifs/nfs share on a LAN workstation or on local usb disk
- verify backup on LAN workstation or local usb disk
- restore full backup from LAN workstation or local usb disk
- selective restore of files or directories from LAN workstation or local usb disk
New backup options are provided with additional perl functions included in backup panel script, a new perl backup script /etc/e-smith/events/actions/workstation-backup-dar, and a new backupwk record in configuration db. All are written with the same logic as present backup scripts.
What are specific problems of SME Server LAN backups managed by e-smith with dar ?
With experience of more than four years backuping sme servers with dar on LAN workstations (in production environments) the most important of encountered problems is that, when the backup session is started, you cannot rely upon a perfect working of the LAN or the distant workstation.
Inevitably, one day the LAN is too busy and/or the connection to the distant share hacks. After the failure sme may keep zombies backup or mount processes, and with some contribs you can be left with incomplete or buggy backup until hopped next good daily backup. These problems are problems of real world with LAN, that backup scripts must take into account.
Another common problem with backup through a LAN is that your lan disponibility for backup flow is not 24/24, but more probably something like "only from 20h to 6h, except on sunday where nobody works on the LAN..." So in case of large volume of data to backup, beeing able to backup all the datas during the week-end and doing only incremental backup on the week days really makes sense.
All these problems are considered with e-smith-backup with dar.
Scripts verify the absence of old share mounts, and alert admin about such situation. Test is made that the distant backup share is available and writable. Of course with daily backup a maximum backup session time of only 24 h is available, but if this limit occurs e-smith-backup with dar cleanly stops the backup session (maybe all is ok and the backup has not enough time to complete), the lan share is unmounted, and daily process can restart anyway. If you have enabled incremental backup and the last backup (full or incremental) was not completed because of a timeout, the backup can then safely restart and complete in an incremental way.
The admin can also set a timeout limit which keeps the session inside a specified number of hours, excluding traffic of LAN backup sessions when users work on the LAN.
Admin user can also set backup configuration so that this time limit occurs only on incremental backup sets. Then if you have a lot of data and your full backup time exceeds time of LAN inactivity, you can always backup all your data each end of week and preserve LAN bandwith for users. If you program a full backup on saturday night, you get 24 hours to do full backup and even if the full backup time exceeds 24 hours, the first incremental backup on sunday night will backup remaining data. You begin your week with full data saved, and incremental backup session time is limited to 6 or 8 hours during week days.
Full backup sessions can also be allowed on every day, or limited to a specific day of week.
Are other new functions provided ?
Yes. Aside use of session timeout, the first is incremental backup.
This means that you can backup and restore data for the period of time you want : one day, three days, one week, one month, 100 days... and restore your system at any state it was during this period of time. This probably has no utility to do full restore of the system as it was one month ago, but restoring a file lost by a user two or three weeks ago can be useful. And restoring a safe system more than one day old can be needed.
The second function is keeping more than one set of backup (a set is full backup data and all datas of next daily incremental backups) with automatic rotation. e.g. you can do only nightly full backups but keep three sets of backup for security reason (as being able to restore the system as it was 72h ago).
The third function is selective restore of any backuped file or directory, exactly as it was for any of the backuped days in your sets. Not only you can restore a lost file at his last state, but also say : make restore of the most recent version of the file before this given date... Selective restore is not an easy thing to manage by hand, and providing this in a simple way with panels is useful. Dar permits to manage selective restore and e-smith-backup with dar panels tries to keep this function as simple as possible to use.
Where to find e-smith-backup with dar ?
Presently beta version of e-smith with dar can be uploaded at http://beta.free-eos.org/sme/RPMS/e-smith-backup-1.14.0-16eos1.el4.sme.noarch.rpm
SRPMS available at http://beta.free-eos.org/sme/RPMS/e-smith-backup-1.14.0-16eos1.el4.sme.src.rpm
Dar rpm is available at http://beta.free-eos.org/sme/RPMS/dar-2.3.2-1.i386.rpm or mirrored at http://mirror.contribs.org/smeserver/contribs/dmay/smeserver/7.x/dar-2.3.2-1.i386.rpm
PDBedit running on SME Server
do the below step on putty
1 mkdir -p /etc/e-smith/templates-custom/etc/smb.conf
2 cp /etc/e-smith/templates/etc/smb.conf/11passdbBackend
3 /etc/e-smith/templates-custom/etc/smb.conf/
4 smb restart service
5 expand-template /etc/smb.conf
6 pdbedit -i smbpasswd
next ... read the below
Domain Account Policy Managment
To view the domain account access policies that may be configured execute:
root# pdbedit -P ?
No account policy by that name
Account policy names are :
min password length
password history
user must logon to change password
maximum password age
minimum password age
lockout duration
reset count minutes
bad lockout attempt
disconnect time
refuse machine password change
The following command execution will achieve these settings:
root# pdbedit -P "min password length" -C 8
account policy value for min password length was 5
account policy value for min password length is now 8
root# pdbedit -P "password history" -C 4
account policy value for password history was 0
account policy value for password history is now 4
root# pdbedit -P "maximum password age" -C 90
account policy value for maximum password age was 4294967295
account policy value for maximum password age is now 90
root# pdbedit -P "minimum password age" -C 7
account policy value for minimum password age was 0
account policy value for minimum password age is now 7
root# pdbedit -P "bad lockout attempt" -C 8
account policy value for bad lockout attempt was 0
account policy value for bad lockout attempt is now 8
root# pdbedit -P "lockout duration" -C -1
account policy value for lockout duration was 30
account policy value for lockout duration is now 4294967295
1 mkdir -p /etc/e-smith/templates-custom/etc/smb.conf
2 cp /etc/e-smith/templates/etc/smb.conf/11passdbBackend
3 /etc/e-smith/templates-custom/etc/smb.conf/
4 smb restart service
5 expand-template /etc/smb.conf
6 pdbedit -i smbpasswd
next ... read the below
Domain Account Policy Managment
To view the domain account access policies that may be configured execute:
root# pdbedit -P ?
No account policy by that name
Account policy names are :
min password length
password history
user must logon to change password
maximum password age
minimum password age
lockout duration
reset count minutes
bad lockout attempt
disconnect time
refuse machine password change
The following command execution will achieve these settings:
root# pdbedit -P "min password length" -C 8
account policy value for min password length was 5
account policy value for min password length is now 8
root# pdbedit -P "password history" -C 4
account policy value for password history was 0
account policy value for password history is now 4
root# pdbedit -P "maximum password age" -C 90
account policy value for maximum password age was 4294967295
account policy value for maximum password age is now 90
root# pdbedit -P "minimum password age" -C 7
account policy value for minimum password age was 0
account policy value for minimum password age is now 7
root# pdbedit -P "bad lockout attempt" -C 8
account policy value for bad lockout attempt was 0
account policy value for bad lockout attempt is now 8
root# pdbedit -P "lockout duration" -C -1
account policy value for lockout duration was 30
account policy value for lockout duration is now 4294967295
Friday, January 18, 2008
Nothing gonna change my love for you
if i had to live without you near me
The days would all be empty
The nights would seem so long
With you i see forever oh, so clearly
I might have been in love before
But it never felt this strong
Our dreams are young and we both know
They’ll take us where we want to go
Hold me now, touch me now
I don’t want to live without you.
Nothings gonna change my love for you
You oughta know by now how much i love you
One thing you can be sure of
I’ll never ask for more than your love.
Nothing’s gonna change my love for you
You ought to know by now how much i love you
The world may change my whole life through but nothing’s gonna change my
Love for you.
If the road ahead is not so easy
Our love will lead the way for us like a guiding star
I’ll be there for you if you should neeed me
You don’t have to change a thing
I love you just the way you are.
So come with me and share this view
I’ll help you see forever too
Hold me now, touch me now
I don’t want to live without you.
The days would all be empty
The nights would seem so long
With you i see forever oh, so clearly
I might have been in love before
But it never felt this strong
Our dreams are young and we both know
They’ll take us where we want to go
Hold me now, touch me now
I don’t want to live without you.
Nothings gonna change my love for you
You oughta know by now how much i love you
One thing you can be sure of
I’ll never ask for more than your love.
Nothing’s gonna change my love for you
You ought to know by now how much i love you
The world may change my whole life through but nothing’s gonna change my
Love for you.
If the road ahead is not so easy
Our love will lead the way for us like a guiding star
I’ll be there for you if you should neeed me
You don’t have to change a thing
I love you just the way you are.
So come with me and share this view
I’ll help you see forever too
Hold me now, touch me now
I don’t want to live without you.
Wednesday, January 16, 2008
Falling in love
... be carefull...
Take care your heart.
go to everywhere you want...
because only your heart that how knows yourself
for kepala peang
Take care your heart.
go to everywhere you want...
because only your heart that how knows yourself
for kepala peang
Monday, January 14, 2008
Friday, January 11, 2008
Belajar compiere lagi
1. download java 1.6
2. download enterpriceDB
3. download compiere
catatan pastikan password untuk database compierenya sama dengan compiere untuk tahap awal
setelah itu bisa diganti.
akirnya udah jalan juga compierenya.
duuuh susah juga klo g ada manualnya. mw beli manual pi g d hepeng
2. download enterpriceDB
3. download compiere
catatan pastikan password untuk database compierenya sama dengan compiere untuk tahap awal
setelah itu bisa diganti.
akirnya udah jalan juga compierenya.
duuuh susah juga klo g ada manualnya. mw beli manual pi g d hepeng
Belajar cisco router dengan cisco emulator
1. Cukup download paket installer Windows, sudah termasuk Dynamips dan Dynagen yang terkompilasi.
2. Install winpcap
3. Install Dynagen yang udah didonlot di point 1 diatas.
4. Download IOS image
mudahkan??????
2. Install winpcap
3. Install Dynagen yang udah didonlot di point 1 diatas.
4. Download IOS image
mudahkan??????
Subscribe to:
Posts (Atom)