Information for users using screen reader software to work with eTouch SamePage. To repeat this information, press ALT+R key.

eTouch SamePage supports Internet Explorer 6 and Mozilla Firefox 1.5 and above on Windows 2000 and Windows XP Platforms. You need to enable Javascript, CSS and Images to work with eTouch SamePage. eTouch SamePage supports several global accesskeys to support keyboard navigation. These keys are

 Welcome guest
 Advanced Search
Help Sign in 
 
View   Discussion   Edit   Attachments  
Knowledgebase and FAQs      
 

Previous | Next


eTouch SamePage can serve as an ideal platform to allow people to contribute ideas and raise questions. Instead of getting lost in individual emails and documents, these nuggets of information get securely stored and indexed within the eTouch SamePage repository which acts as a KnowledgeBase. Information can be categorized by Topics or easily searched within the repository.









Frequently Asked Questions


1. What can I do with eTouch SamePage?
You can create wikis for multiple projects (or team) which allow collaboration among project members.

2. Who can create a project ?
 By default any, registered user can create a new project. The user who creates the project becomes administrator of it, and can assign members/administrators in the project.

3. How do I register ?
You can register as user in wiki server by completing the registration page. Once you register, you get a login to eTouch SamePage.

4. How do I create a Project ?
When you login to the eTouch SamePage, you will see a Create New Project link, which will take you to the project creation page. When you create a new project, by default a home page is created for the project wiki.

5. What type of access permission can I set in a Project ?
There are two pre-defined roles in eTouch Wiki, Member and Administrator. All the non members are considered as Guest/Visitor.
  • Member - all members can add, delete, edit wiki pages and news in a project.
  • Administrator - all administrators in a project can do what members can do plus they can manage user permissions in the project.
6. What is Guest User Access field ?
All the users (logged in/ or not logged in) who are not members of the project are considered as Guest for the project. This field allows you to set the access level for these users in your project.
  • None - Guests can not see any wiki page/news for the project,
  • Visitor - Guests can browse the wiki/news pages, but can not do any editing/commenting etc
  • Visitor + Comments - Guests can add comments in the Discussion tab for any wiki page.
  • Member - Guests get member access, so they can also edit/add wiki pages, news
  • Administrator - Guests can administor the project (add/delete users to the project) other than having all the member access
7. Can I restrict access to specific pages in eTouch SamePage ?
Yes, you can override the page level access, if you are the page owner. By default the user who created the page becomes owner of the page. To set the permissions you need to edit the page, and click the Permissions button. On the permissions dialog, you can grant Read, Edit and Comment permissions to individual users. When you grant any of these permissions, it overrides the Project level permission for that page. So you need to add all the users who you want to allow access to Read/Edit/Comment permission.

Known Problems with threads on Linux

  1. (Claimed fixed when using NPTL with 2.5.36 kernel.) It doesn't handle signals correctly.  

    Signals sent via kill() from other processes are delivered to single individual threads rather than to the process as a whole.  This makes it difficult to manually SIGSTOP a process, causes job control to operate incorrectly, and makes it hard to implement debuggers that can freeze a whole process.  

  2. (Claimed fixed when using NPTL with 2.5.36 kernel.) A multithreaded process cannot perform asynchronous I/O with SIGIO, handling the signal in a separate thread.  

  3. (Not addressed by NPTL.) ps shows every thread in a process, and moreover shows each thread as if it were a process.  The traditional Unix semantics are that ps lists processes, not threads.  

    Commercial Unices get this right.  Their ps commands list processes.  Details of individual threads are simply another sort of additional information about a process that can be printed if desired.  (See the -L option to ps on Solaris, for example.)  

  4. (Still outstanding, albeit unacknowledged, as of NPTL 0.19 and kernel 2.5.36.) Core dumps of multi-threaded programs don't contain all the threads (or even necessarily the crashing one !).   

  5. (Claimed fixed when using NPTL with 2.5.36 kernel.) getpid() doesn't return the same value for all threads in a single process.  In fact, there is no value provided by the Linux kernel to applications corresponding to the standard Unix concept of process ID.




How to set up a wildcard DNS

I like to use a wildcard DNS entry for my localhost. The reason? If I want to establish a new virtual domain in Apache for testing, I need only go in and create my own arbitrary virtual domain (like railsdev.localhost), and the DNS side will "just work." On Linux machines, you can just edit /etc/hosts and put a *.localhost entry in. This didn't appear to work on OS X, so I instead enabled a local nameserver and went down that path.



I gathered hints from various parts of the net when it came to enabling DNS on OS X Tiger, and I think I have found the most efficient way to do that.

First up, run the following commands to generate a rndc.conf and key file. You can disable this stuff in /etc/named.conf if you like; otherwise:

$ rndc-confgen > /etc/rndc.conf 

$ head -n 6 /etc/rndc.conf > /etc/rndc.key


Now you need to add the wildcard record to the localhost zone file. To do this, add the following line to the end of /var/named/localhost.zone:

*       IN      A       127.0.0.1



Previous | Next


Tags : SamePage 
  
Short Link: http://sandbox.spwiki.com/cm/wiki/?id=764