Sponsored Content
Full Discussion: Diagnostic Software
Top Forums UNIX for Dummies Questions & Answers Diagnostic Software Post 38875 by Neo on Tuesday 29th of July 2003 01:23:04 PM
Old 07-29-2003
Your situation sounds like a BIOs level tool associate with your motherboard would be a better choice than an OS level tool.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix Equivalent of Windows NT Diagnostic (Winmsd) report

Hi Guys, Is there a way I can generate a Diagnostic Report for Unix app server/database server (for sun solaris and aix) similar to the system diagnostic report in Windows NT(winmsd). Basically I am looking for the following details below in a single comprehensive report. If there is no... (2 Replies)
Discussion started by: neer
2 Replies

2. Red Hat

RedHat diagnostic commands

Dear all Can anyone tell me what commands I can run on a RedHat linux server to gain some diagnostic information, e.g. checking for disk errors or other related problems. Regards (1 Reply)
Discussion started by: soliberus
1 Replies

3. Solaris

Solaris Diagnostic Reporter Logs

I have 3510 Disk Array attached to T2000 sever running Solaris 10 and I have set up Diagnostic Reporter to send status update via email once a day. Since logs are growing everyday, my email is getting big too. I cannot recall what file I need to echo > , so that only new logs are sent. Kindly... (1 Reply)
Discussion started by: Tirmazi
1 Replies

4. Solaris

Solaris10..Open boot diagnostic failed

Hi all, when am rebooting the server (SF v890) we are facing "open boot diagnostic failed". Thanks in Adv. (5 Replies)
Discussion started by: arjunreddy3
5 Replies

5. AIX

AIX5L diagnostic process question

I am an Oracle DBA with some strange IO performance problems. Between 04:00 and 06:00 AM local time each day I see a degrading of IO performance (to a SAN). I see that the AIX diagnostics seem to begin at 04:00. Is it likely that AIX diagnostics might be affecting IO? Additional... (2 Replies)
Discussion started by: sink
2 Replies

6. HP-UX

HP-UX stops on boot; DIAGNOSTIC SYSTEM WARNING

Hi all, I have an HP-UX server that halts during boot. Below is CO output. Any ideas how to solve this? Any help would be appreciated. Thank you. HP-UX Boot Loader for IPF -- Revision 2.027 Press Any Key to interrupt Autoboot \EFI\HPUX\AUTO ==> boot vmunix -lq Seconds left till... (0 Replies)
Discussion started by: MazenH
0 Replies
GIT-MERGETOOL(1)						    Git Manual							  GIT-MERGETOOL(1)

NAME
git-mergetool - Run merge conflict resolution tools to resolve merge conflicts SYNOPSIS
git mergetool [--tool=<tool>] [-y | --[no-]prompt] [<file>...] DESCRIPTION
Use git mergetool to run one of several merge utilities to resolve merge conflicts. It is typically run after git merge. If one or more <file> parameters are given, the merge tool program will be run to resolve differences on each file (skipping those without conflicts). Specifying a directory will include all unresolved files in that path. If no <file> names are specified, git mergetool will run the merge tool program on every file with merge conflicts. OPTIONS
-t <tool>, --tool=<tool> Use the merge resolution program specified by <tool>. Valid values include emerge, gvimdiff, kdiff3, meld, vimdiff, and tortoisemerge. Run git mergetool --tool-help for the list of valid <tool> settings. If a merge resolution program is not specified, git mergetool will use the configuration variable merge.tool. If the configuration variable merge.tool is not set, git mergetool will pick a suitable default. You can explicitly provide a full path to the tool by setting the configuration variable mergetool.<tool>.path. For example, you can configure the absolute path to kdiff3 by setting mergetool.kdiff3.path. Otherwise, git mergetool assumes the tool is available in PATH. Instead of running one of the known merge tool programs, git mergetool can be customized to run an alternative program by specifying the command line to invoke in a configuration variable mergetool.<tool>.cmd. When git mergetool is invoked with this tool (either through the -t or --tool option or the merge.tool configuration variable) the configured command line will be invoked with $BASE set to the name of a temporary file containing the common base for the merge, if available; $LOCAL set to the name of a temporary file containing the contents of the file on the current branch; $REMOTE set to the name of a temporary file containing the contents of the file to be merged, and $MERGED set to the name of the file to which the merge tool should write the result of the merge resolution. If the custom merge tool correctly indicates the success of a merge resolution with its exit code, then the configuration variable mergetool.<tool>.trustExitCode can be set to true. Otherwise, git mergetool will prompt the user to indicate the success of the resolution after the custom tool has exited. --tool-help Print a list of merge tools that may be used with --tool. -y, --no-prompt Don't prompt before each invocation of the merge resolution program. --prompt Prompt before each invocation of the merge resolution program. This is the default behaviour; the option is provided to override any configuration settings. TEMPORARY FILES
git mergetool creates *.orig backup files while resolving merges. These are safe to remove once a file has been merged and its git mergetool session has completed. Setting the mergetool.keepBackup configuration variable to false causes git mergetool to automatically remove the backup as files are successfully merged. GIT
Part of the git(1) suite Git 1.8.3.1 06/10/2014 GIT-MERGETOOL(1)
All times are GMT -4. The time now is 07:19 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy