2015年4月30日 星期四

可以解決IBM Notes 9.0.1 java 處理上的一些問題

Edit your jvm.properties file
Open the {Notes}/framework/rcp/deploy/jvm.properties file in a text editor and add the following lines:
 
vmarg.Djmxremoteport=-Dcom.sun.management.jmxremote.port=8123
vmarg.Djmxremotessl=-Dcom.sun.management.jmxremote.ssl=false
vmarg.Djmxremoteauth=-Dcom.sun.management.jmxremote.authenticate=false
 
The first line tells the Notes client JVM to listen on port 8123 for JMX clients like JConsole (feel free to use a different port if you’d like). 
 
The second line tells it not to use SSL for the connection (which it would do by default).
 
 And the third line tells it not to require a username and password for the connection.
 
 

2015年4月13日 星期一

Full Text Index on separate Drive

Since 8.5.3 (available as of today) we have the option to put the Full Text Index on another drive. We have asked about it many times for many years and finally got this functionality.
The notes.ini parameter e.g. FTBasePath=d:\full_text can be used to switch the starting directory for the full text index from data directory to a different directory or drive.

It makes a lot of sense to separate the FT Index from the NSF data in larger environments.
There are a couple of reasons

- FT Index causes a lot of file-system fragmentation
- At some point even with DAOS on larger environments the file-system for NSF data can be quite big and separating FT and NSF would make sense.
- When using snap-shot backup reducing the size of the file-system containing NSF would make a lot of sense
- From I/O point of view on larger servers with a lot of FT data this can also improve performance

This setting does only make sense for larger environments

To migrate your FT index to a separate drive you need the following steps:

- Set the notes.ini FTBasePath=d:\full_text
- Run updall -f to rebuild all FT indexes.

This will automatically delete the old FT index and re-create it on the new drive.


轉載自:http://blog.nashcom.de/nashcomblog.nsf/dx/full-text-index-on-separate-drive.htm?opendocument&comments

2014年12月2日 星期二

Linux vsftpd變更預設目錄作法

As we know by default vsftpd will configure the anonymous directory to /var/ftp/pub which is great to share files with users 

After trying a lot of different configurations this is what worked for me:


Code:
mkdir /home/pub
mv /var/ftp/pub/* /home/pub/
rm -rf /var/ftp/pub
mount --bind /home/pub/ /var/ftp/pub/
I have a feeling that vsftpd does not lets you browse symlinks but will work with mounted filesystems (bind method).