Sponsored Content
Full Discussion: ssh issue
Operating Systems Solaris ssh issue Post 302401702 by jlliagre on Sunday 7th of March 2010 05:28:10 PM
Old 03-07-2010
Quote:
Originally Posted by h@foorsa.biz
any idea
I'm missing why you are filling this thread with Solaris clients ssh verbose outputs all showing a correctly running session. There is no much point in trying to debug/fix something that works.
As the problem only shows up with putty, enable and get some logs from it and came back with this.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

ssh issue

Im using the default ssh program on a solaris 9 system to connect to another server. When connecting to the other host it make me type my password in 3 to 4 times before letting me in. Is anyone familar with this? (4 Replies)
Discussion started by: meyersp
4 Replies

2. UNIX for Advanced & Expert Users

An issue with SSH

Hey Guys! I got two PCs at my place. In the beginning, one of my PCs had RHEL3( say PC1 ) and one had RHEL4 ( say PC2 ). I was able to ssh from PC1 to PC2 and vice-versa. But recently I've upgraded PC1 from RHEL3 to RHEL4. Now when i am trying to ssh from PC2 to PC1, it is not allowing... (1 Reply)
Discussion started by: chakri.penguin
1 Replies

3. Solaris

SSH/Firewall issue

I am a complete UNIX neophyte with the unenviable task of trying to pseudo manage two SUN boxes with an unknown past. I was not responsible for setting them up, anything that was done on them previously, and have no means of figuring out anything that was done to them. So far I have changed the... (4 Replies)
Discussion started by: tawnos42
4 Replies

4. Shell Programming and Scripting

SSH issue

I want to run a program on remote server by using unauthenticated ssh. It works when I ssh from command line however, it does not work when I try to invoke ssh script with other application. Any clue? (6 Replies)
Discussion started by: sam101
6 Replies

5. Solaris

SSH issue

Facing a SSH issue while creating passwordless login. unix> ./create_ssh In the program, you will be asked and providing 1. SSH private key filename (twice) 2. key passcode (twice) Enter private key filename: id_ss81dev ld.so.1: ssh-keygen: fatal: relocation... (5 Replies)
Discussion started by: flinders1323
5 Replies

6. UNIX for Advanced & Expert Users

ssh issue

Hi I have a annoying situation here . Our non prod server connect to informatica to run the work flow. But since yest some jobs are getting failed due ssh to informatica server been unsuccessfull. please look into this. successful log for job fiusdcacct_ios_price_venld: SSH... (2 Replies)
Discussion started by: ptappeta
2 Replies

7. Fedora

ssh issue

Hello, I have two computers at my desk, let's call them A and B. I have some tasks that can only be performed on one of them and some on the other, so I need to be able to ssh from one to the other and vice versa to transfer files, etc. A can ssh to B without problem: I even copied the public key... (6 Replies)
Discussion started by: Leo_Boon
6 Replies

8. Solaris

SSH issue

Hi guys. I just installed Solaris 10 and want to enable ssh on it So that i can remotely use it from another location. I read a post on this forum an it was written that SSH is enabled by default. I did a ps -ef | grep ssh and nothing showed up meaning that it isnt running. I even tried... (11 Replies)
Discussion started by: Junaid Subhani
11 Replies

9. UNIX for Beginners Questions & Answers

Issue with SSH key

Hello All , I am trying to set up the keys to login seamless on to two diff environment server(s). i used to have it couple of years back , but somehow never worked and didn`t concentte much , but when i want to setup again . facing a challange while copying the id_rsa.pubfile to... (4 Replies)
Discussion started by: radha254
4 Replies

10. UNIX for Advanced & Expert Users

Ssh issue

Hi All, I am trying to connect between two system , I am facing the issue with -SSH-t-l userid systemname exit ( this is the syntax) It suppose to ask for password , but it throws the error as mentioned below Error is received disconnect from system and remote login for the... (1 Reply)
Discussion started by: sudhainit
1 Replies
CUTTER(1)							  Cutter's manual							 CUTTER(1)

NAME
cutter - xUnit family unit testing framework for C and C++ SYNOPSIS
cutter [option ...] test-directory cutter --mode=analyze [option ...] log-directory DESCRIPTION
Cutter is a xUnit family unit testing framework for C and C++. Cutter provides programmers two important interfaces: 1. easy to write API 2. easy to debug UI Cutter helps programmers to write their new tests, run their existing tests, get feedbacks from ran their tests. test-directory is a directory which has test_*.so. test_*.so are searched recursively. log-directory is a directory which has Cutter log files. Cutter logs test results when --stream-directory option is specified. OPTIONS
--version Cutter shows its own version and exits. --mode=[test|analyze] It specifies run mode. Cutter runs tests when run mode is test. Cutter analyzes test results when run mode is analyze. The default is test. -s DIRECTORY, --source-directory=DIRECTORY Cutter prepends DIRECTORY to file name when test fails. This is for tolls (like Emacs) which have function jumping to error line. -t TEST_CASE_NAME, --test-case=TEST_CASE_NAME Cutter runs test cases that are matched with TEST_CASE_NAME. If TEST_CASE_NAME is surrounded by "/" (e.g. /test_/), TEST_CASE_NAME is handled as regular expression. This option can be specified n times. In the case, Cutter runs test cases that are matched with any TEST_CASE_NAME. (OR) -n TEST_NAME, --name=TEST_NAME Cutter runs tests that are matched with TEST_NAME. If TEST_NAME is surrounded by "/" (e.g. /test_/), TEST_NAME is handled as regular expression. This option can be specified n times. In the case, Cutter runs test that are matched with any TEST_NAME. (OR) -m, --multi-thread Cutter runs a test case in a new thread. The default is off. --max-threads=MAX_THREADS Run test cases and iterated tests with MAX_THREADS threads concurrently at a maximum. -1 means no limit. The default is 10. --disable-signal-handling Disable signal handling that provides aborting test by C-c, provides backtrace on SEGV and so on. If your test target uses signal, Cutter's signal handling may cause a problem. In the case, you should disable Cutter's signal handling by this option. The default is enabled. --test-case-order=[none|name|name-desc] It specifies test case order. If 'none' is specified, Cutter doesn't sort. If 'name' is specified, Cutter sorts test cases by name in ascending order. If 'name-desc' is specified, Cutter sorts test cases by name in descending order. The default is none. --exclude-file=FILE Cutter doesn't read FILE on test collecting. --exclude-directory=DIRECTORY Cutter doesn't search tests under DIRECTORY. --fatal-failures Cutter treats failures as fatal problem. It means that Cutter stops test run. The default is off. --keep-opening-modules Cutter keeps opening loaded modules to resolve symbols for debugging. The default is off. --enable-convenience-attribute-definition It enables convenience but danger "#{ATTRIBUTE_NAME}_#{TEST_NAME - 'test_' PREFIX}" attribute set function. The default is off. --stop-before-test It sets a breakpoint immediately before each test. You can dive into test function easily by running cutter on your debugger and stepping into the next function. The default is off. -u[console|gtk], --ui=[console|gtk] It specifies UI. The default is console UI. -v[s|silent|n|normal|v|verbose], --verbose=[s|silent|n|normal|v|verbose] It specifies verbose level. This option is only for console UI. -c[yes|true|no|false|auto], --color=[yes|true|no|false|auto] If 'yes' or 'true' is specified, Cutter uses colorized output by escape sequence. If 'no' or 'false' is specified, Cutter never use colorized output. If 'auto' or the option is omitted, Cutter uses colorized output if available. This option is only for console UI. --pdf-report=FILE Cutter outputs a test report to FILE as PDF format. --xml-report=FILE Cutter outputs a test report to FILE as XML format. --stream=[xml] It specifies stream backend. Stream backend streams test results. There is only XML stream backend for now. --stream-fd=FILE_DESCRIPTOR It specifies output file descriptor. The XML stream backend streams to FILE_DESCRIPTOR. This option is only for XML stream backend. --stream-directory=DIRECTORY It specifies output directory. The XML stream backend streams to a file under DIRECTORY. This option is only for XML stream backend. -?, --help Cutter shows common options. --help-stream Cutter shows stream related options. --help-report Cutter shows report related options. --help-ui Cutter shows UI related options. --help-all Cutter shows all options. EXIT STATUS
The exit status is 0 if all tests are passed and non-0 otherwise. Omission test result and notification test result are not treated as failure. FILES
/usr/local/share/doc/cutter/ The directory has Cutter documents. e.g. reference manual, tutorial and so on. EXAMPLE
In the following example, cutter runs tests under tests/ directory and shows test progress verbosely. % cutter -v v test/ In the following example, test results are saved under logs/ directory: % cutter --stream=xml --stream-directory=logs/ test/ SEE ALSO
GLib's reference manual. Cutter February 2011 CUTTER(1)
All times are GMT -4. The time now is 02:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy