03-30-2015
Usually, the interpretation of color is done by the terminal emulator (konsole, gnome-terminal, etc.). So usually that's a setting of those programs. There is also a way to set the color palette for vt's as well.
Does that make sense?
8 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
How to I write to a log file all the output that is displaying on the screen? with time stamp.
thankx. (3 Replies)
Discussion started by: laila63
3 Replies
2. Solaris
Does anyone have a simple method of logging all shell commands typed by a user (csh in our case)?
- I could enable auditing, but this would be overkill
- I could enable process accounting, but AFAIK, this does not log arguments
Thanks all. (2 Replies)
Discussion started by: minkie
2 Replies
3. UNIX for Advanced & Expert Users
I wanted to point this out. It took me a long time figure out how to find what color schemes I have.
How to use a vi color scheme | vi vim color scheme colorscheme | devdaily.com
I recommend just using this command. Every system that I have tried has desert.vim so that is why I searched for... (0 Replies)
Discussion started by: cokedude
0 Replies
4. SuSE
SUSE Linux Enterprise Server v11
Hi guys,
I don't have root access. So, I can't change the default colorscheme for my vim editor.
I do have an environment variable for my id that says:
EDITOR=/usr/bin/vi
export EDITOR
I tried adding /usr/share/vim/vim72/colors/desert.vim to it.... (2 Replies)
Discussion started by: dexter126
2 Replies
5. UNIX and Linux Applications
I have an Ubuntu 12.04 LTS server running GNOME shell,that I occassionly have to remotely access to perform some maintenance. I usually vpnc into the network and then simply use vncviewer to access the Gnome GUI desktop for testing,given that the account is logged in. The other day I had to reboot... (4 Replies)
Discussion started by: metallica1973
4 Replies
6. Shell Programming and Scripting
If I run the below code... it will login into the router and then changes to privilege mode and then stores the running configuration information to an array.
In this program, I have included the username and password .
In case the username and password is wrong.. it will re login for 2 times... (0 Replies)
Discussion started by: scriptscript
0 Replies
7. Shell Programming and Scripting
Below is the code.
I need to login into the router if the 1st set of credentials are correct..
if wrong... then it has to check with 2nd set of credentials..
=> if the credentials are correct... then it should continue..
=> if the credentials are wrong(should not check for 2nd time... then... (0 Replies)
Discussion started by: scriptscript
0 Replies
8. Shell Programming and Scripting
Hi,
I am looking for a shell script which serves the below purpose.
Please find below the algorithm for the same and any help on this would be highly appreciated.
1)set of strings need to be replaced among set of files(directory may contain different types of files)
2)It should search for... (10 Replies)
Discussion started by: Amulya
10 Replies
LEARN ABOUT OSF1
vollogcnvt
vollogcnvt(8) System Manager's Manual vollogcnvt(8)
NAME
vollogcnvt - Logical Storage Manager BCL-to-DRL logging conversion utility
SYNOPSIS
/usr/sbin/vollogcnvt [-g diskgroup]
OPTIONS
Limits the conversion of logging subdisks to volumes in the specified disk group.
DESCRIPTION
The vollogcnvt script is a migration tool for Logical Storage Manager (LSM) administrators who are currently using the block-change logging
(BCL) feature. Beginning with the Version 5.0 release of Tru64 UNIX, the BCL feature of LSM is being replaced with the dirty-region logging
(DRL) feature.
The vollogcnvt script attempts to convert volumes with BCL enabled to volumes with DRL enabled. If called without specifying a disk group,
vollogcnvt attempts the BCL-to-DRL conversion for all volumes across all disk groups.
If logging cannot be re-enabled in the DRL scheme, a warning is sent to the console.
For volumes whose BCL subdisks will not work in the DRL scheme, logging is disabled.
Log subdisks that cannot be converted to DRL will be disassociated from its volume only if at least one of the log subdisks for that volume
could be converted. Otherwise, the configuration will not change and logging will be disabled. Those volumes that could not be converted,
for example all of its log subdisks are too small, will have logging disabled.
At system startup, the vollogcnvt script runs automatically and logs such errors to binlog and sends mail to root. This happens at each
reboot until the DRL is manually converted or when logging is disabled. If the script runs at startup or manually, warnings are sent to
the console.
For details and guidelines on using DRL, refer to the Logical Storage Manager guide.
SEE ALSO
binlogd(8), dia(8), volintro(8)
vollogcnvt(8)