This link show how to use the command ps on linux.
Sometimes you need to know the process id and then kill him 🙂
This link show how to use the command ps on linux.
Sometimes you need to know the process id and then kill him 🙂
When Domino will have this feature?
I have 3 Domino Servers installed on top of Linux.
Eight months without logon as a root. After 15 days of vacation and then i forgot the password 🙂
This link show how to reset the root password
Today me and some colleagues saw the OGS using the internet.
Good image and sound
Some new features was addet to calendar profile. After convert some users from 7.0.4 to 8.5.2 some problems arrived.
I deleted the profile using the LotusScript and instruct the user to recreate the profile.
Just put the code bellow in a button and send to the user.
Sub Click(Source as Button)
Dim session As New NotesSession
Dim db As NotesDatabase
Dim doc As NotesDocument
Set db=session.CurrentDatabase
Set doc=db.GetProfileDocument(“CalendarProfile”)
Call doc.remove(True)
If doc Is Nothing Then
MsgBox “Profile Document Was Successfully Removed”
Else
MsgBox “Profile Document WAS NOT Removed”,48
End if
End Sub
From TN 1449358
tell daosmgr prune <#_of_days_since _last_full_backup>
In order to ensure you have all data saved in a disaster recovery situation you must not set your “defer object deletion” less than the largest number of days between full saves.
tell daosmgr prune <#_of_days_to_retain_nlo_files>
If you wish to recompile all the LotusScript you need Notes 8.5.2
Title: | Recompile all LotusScript does not recompile all LotusScript in Domino Designer 8.5.1 |
Product: | Lotus Domino > Lotus Domino Designer > Version 8.5.1 |
Platform(s): | Windows |
Date: | 10/01/2011 |
Doc Number: | 1452121 |
Problem |
The “Recompile All LotusScript” function does not work as expected in Domino Designer 8.5.1.
Content |
This issue is fixed in 8.5.2
Fix details: SPR# BHUY84SEG9 Refer to the Upgrade Central site for details on upgrading Notes/Domino. |
Mario Costa tweet about this
http://twitter.com/mariocosta/statuses/20978463695437824
It’s a problem for us outside of the US or UK
This TechNote solve the problem
From TN 1424677
The Sametime Information Center topic Enabling chat logging contains the steps to enable chat logging in Lotus® Sametime® 8.5 Server. The steps below, while similar, also contain information for what to do if not using the Sametime System Console.
This procedure differs from earlier versions of Sametime. For instructions on enabling chat logging for previous versions of Sametime or for client side logging, see the related technote #1086729. Step 1: Updating the sametime.ini and creating the chatlogging.ini In Sametime 8.5, you can configure chat logging black box library names by using the sametime.ini file. This configuration is controlled by a new section called [ST_BB_NAMES], and the value that controls the chat logging black box is ST_CHAT_LOG. Note: The StChatLogFile library (or libstchatlogfile.so on AIX, Linux,and Solaris platforms) is a sample of how to implement a chat logging black box using the Sametime SDK. The StChatLogFile sample is not supported, and is not recommended for use on deployment environments. 1. Use a text editor to edit the sametime.ini file, which is located in the Lotus Sametime Community Server installation directory (for example: C:Program Fileslotusdomino). a. Set ST_CHAT_LOG to file in the sametime.ini file under the ST_BB_NAMES section. ST_CHAT_LOG=File Examples: For Windows: [ST_BB_NAMES] For IBM i: [ST_BB_NAMES] b. Create chatlogging.ini in the same directory as sametime.ini. c. Move all the attributes from sametime.ini related to [ChatLogging] to chatlogging.ini. For example: [ChatLogging] Note: If you want to use BB_CL_LIBRARY_PATH to change the default location of where the chat logs are stored, then move the [Library] section from sametime.ini to the chatlogging.ini file. Also, the directory you specify with BB_CL_LIBRARY_PATH, or the default CLData directory, must exist before you start the server after making this change. If the directory does not exist, then chat logging and chat services can fail. The directory or folder is not created by the system on startup. Example: Step 2: Updating the stconfig.nsf database There are two ways to enable chat logging, depending on your environment. If using the Sametime System Console (SSC), changes MUST be made through the SSC. Using the Sametime System Console If you have configured Sametime 8.5 using the Sametime System Console, perform these steps: 1. Log in to the Integrated Solutions Console. Using a Notes client to access stconfig.nsf If you have configured Sametime 8.5 without the Sametime System Console, perform these steps: 1. Stop the Sametime 8.5 server. Refer to the technote titled, “Shutting down a Sametime server without shutting down the Domino server” (#1088677Link). 2. Use a Lotus Notes client to open the Sametime Configuration database (stconfig.nsf) on the Sametime server. 3. In the right hand pane, open the CommunityServices document by double-clicking on the date associated with the document. 4. Double-click on the CommunityServices document to put the document in edit mode. 5. For the “Chat Logging Flag” parameter, select either “relax” or “strict” for the chat logging mode. “strict” indicates that chat should be disallowed if it is not possible to log chats for any reason. 6. Update the “Capture Service Type” parameter.
Note: If the Chat Logging service becomes unavailable for any reason when “Chat Logging Flag” is set to “strict” and “Capture Service Type” is set to “0x1000” in the CommunityServices document, users will receive “Chat services unavailable” when attempting to chat. This is by design; the strict setting is being enforced. 7. Save and close the CommunityServices document. 8. Restart the Lotus Sametime Community Server for changes to take effect. . |