Search Results

Search found 3 results on 1 pages for 'amicitas'.

Page 1/1 | 1 

• Get name (address) of computer from which from which SSH login was made.

  - by amicitas

  After logging onto a linux machine via SSH, I would like to be able to retrieve the name of the computer from which the connection was made. Ideally I am looking for some command like hostname or uname but that would retrieve the name of the client instead of the host. This information must be accessible somewhere, since when I log on I get a message that contains the clinent name from the last login: Last login: Thu Mar 11 18:42:01 2010 from my.address.com The reason for wanting to do this is to be able to take different action in my .login file depending on which computer I am using for connection is from.

  Read the article

• How to run a command in a process that is not a child of the current process?

  - by amicitas

  I am having a library conflict issue with calling an external program from within a interpreted programming environment (IDL). The issue seems to be that since the program I am calling ends up as a child of IDL, libraries are not being reloaded. From within IDL I can launch sub-processes either directly or using a shell. Is there a good way that I can cause my program to be run without ending up as a child process? The only solution I have found so far is to use ssh localhost my_program. This works perfectly but I would like a more direct solution.

  Read the article

• Error using \Glsentrytext{} in section title.

  - by amicitas

  When using the glossaries package in a LaTeX document I occasionally want to use a glossary entry as part of section or chapter title. For example: \section{\Glsentrytext{big}} This however results in an error. Trying to use \protect\Glsentrytext{} does not solve the the problem. Note that using the non-capitalized version (\glsentrytext) does not produce any problems. Does anyone know of a way to get this to work? I use the glossaries package occasionally as way to format specific strings in a consistent way. For example \gls{big} turns into 'beam-into-gas'. Obviously I could create two glossary entries, with and without caps, to achieve this and only include one in the final glossary. That is an ugly solution though.

  Read the article

1