Sponsored Content
Full Discussion: I just did something bad....
Top Forums UNIX for Dummies Questions & Answers I just did something bad.... Post 71344 by RTM on Tuesday 10th of May 2005 08:33:23 AM
Old 05-10-2005
Restore from your backups OR update your resume.

If for some reason you don't have backups, you might be able to get the appropriate lib files from your development server.
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

bad if test

:confused: Bad if test: if returns an error I have changed filename to "filename"s su "$filename" 'filename'' '$filename'' "./filename" "./$filename" error is usually why cant I test the filename? Thanks (4 Replies)
Discussion started by: sharkze
4 Replies

2. UNIX for Advanced & Expert Users

Script to search a bad record in a file then put the record in the bad file

I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file. Example: File1 Name designation dateOfJoining... (1 Reply)
Discussion started by: shilendrajadon
1 Replies

3. Shell Programming and Scripting

Script to search a bad record in a file then put the record in the bad file

I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file. Example: File1 Name designation dateOfJoining... (2 Replies)
Discussion started by: shilendrajadon
2 Replies

4. UNIX for Dummies Questions & Answers

Does this look like a bad drive to anyone?

Jun 19 02:45:28 scsi: WARNING: /pci@8,600000/scsi@1/sd@c,0 (sd42): Jun 19 02:45:28 Error for Command: read Error Level: Retryable Jun 19 02:45:28 scsi: Requested Block: 713232 Error Block: 713244 Jun 19 02:45:28 scsi: Sense Key: Media Error (1 Reply)
Discussion started by: jgentile
1 Replies

5. UNIX for Advanced & Expert Users

Bad emulation

I am using mpc8xx processor with linux-2.4.20 kernel. These prints are getting flooded to my console almost consistenly. 14 06:29:17 MC4L-TP01 syslog.warn klogd: pte @ 0x10113d88: (0xc51cc100)->(0xc4bd144c)->0x01eec889 Oct 14 06:29:17 MC4L-TP01 syslog.warn klogd: RPN: 01eec PP: 2 SPS: 1 SH:... (1 Reply)
Discussion started by: subratasaharia
1 Replies

6. Shell Programming and Scripting

Bad Interpreter

Hi. My name is Caleb (a.k.a RagingNinja) form the whited00r forums. (Whited00r makes custom firmware for iOS devices). I have been learning and creating simple shells scripts. I have been recently using VIM for Windows or using VirtualBox to run the UBUNTU OS within VirtualBox to create my shell... (2 Replies)
Discussion started by: RagingNinja
2 Replies

7. Shell Programming and Scripting

Why I get bad bad substitution when using eval?

Why I get bad replace when using eval? $ map0=( "0" "0000" "0") $ i=0 $ eval echo \${map$i} 0000 $ a=`eval echo \${map$i}` !!!error happens!!! bash: ${map$i}: bad substitution How to resolve it ? Thanks! (5 Replies)
Discussion started by: 915086731
5 Replies

8. Solaris

bad options(s)

Hi Folks, I am seeing an issue in solaris, while running a script.. Script contents #!/usr/bin/bash echo $HOME echo "********** RUNNING props on test ********" . /opt/home/weblogic/.profile > /dev/null echo "****** CURRENT BRANCH: $BRANCH *********"; .... (3 Replies)
Discussion started by: ganga.dharan
3 Replies

9. Shell Programming and Scripting

Bad substitution

Cant undestand :) why i have an error on line 2.it is working on my other boxes #!/bin/bash ret=$(echo Q | timeout 5 openssl s_client connect "${1`hostname`}:${2-443}" -ssl3 2> /dev/null) if echo "${ret}" | grep -q 'Protocol.*SSLv3'; then if echo "${ret}" | grep -q 'Cipher.*0000'; then ... (7 Replies)
Discussion started by: kenshinhimura
7 Replies
update-fonts-dir(8)					      System Manager's Manual					       update-fonts-dir(8)

NAME
update-fonts-dir - compile fonts.dir files SYNOPSIS
update-fonts-dir [OPTION] directory ... DESCRIPTION
update-fonts-dir creates a fonts.dir file in an X font directory by invoking mkfontdir(1x) with the appropriate arguments. It is typically invoked only from the post-installation and post-removal scripts of a package containing fonts for the X Window System, but may be invoked at any time to reconstruct fonts.dir files. For each directory, which is simply the last component of its path (such as '75dpi' or 'misc'), update-fonts-dir will generate either /usr/lib/X11/fonts/directory/fonts.dir or /usr/share/fonts/X11/directory/fonts.dir from the fonts.scale and font files found within it. This enables multiple packages to provide names for fonts in the same directory. No font package actually provides the fonts.dir file in the X font directory itself, so there is no danger of overwriting one package's font names with those of another. For instance, the two packages 'xfonts-base' (real) and 'xfonts-nifty' (hypothetical) may both install fonts into the directory /usr/lib/X11/fonts/misc, and update-fonts-dir will ensure that the fonts.dir file in that directory contains information about the font files provided by both packages. The format of fonts.dir files is described in the mkfontdir(1x) manual page. An example of how to use update-fonts-dir in package maintainer scripts is provided in the Debian Policy Manual. OPTIONS
-h, --help displays a brief usage message and exits. -7, --x11r7-layout switches the font layout to the one introduced in X11R7: fonts in /usr/share/fonts/X11/directory (default is: fonts in /usr/lib/X11/fonts/directory) OPERANDS
update-fonts-dir takes one or more X font directory names to operate on as operands. Only the final path component of the directory name should be specified; e.g., update-fonts-dir 75dpi is correct, while 'update-fonts-dir /usr/X11R6/lib/X11/fonts/75dpi' and 'update-fonts-dir /usr/lib/X11/fonts/75dpi' are not. ENVIRONMENT
COLUMNS indicates the width of the terminal device in character cells. This value is used for formatting diagnostic messages. If not set, the terminal is queried using stty(1) to determine its width. If that fails, a value of '80' is assumed. DIAGNOSTICS
Errors usage error: one or more font directories must be provided update-fonts-dir was invoked without operands. Supply one or more X font directory names to operate on. usage error: unrecognized option update-fonts-dir was invoked with an unrecognized option argument. Use only the options documented in "OPTIONS", above. fatal error: path to X font directory must be used A directory name was supplied that was not an X font directory name. Supply X font directory names only. Warnings warning: absolute path directory was provided Usage of absolute paths is deprecated. Use only the final component of the X font directory name for directory. warning: directory does not exist or is not a directory The supplied directory was invalid. update-fonts-dir skipped it. EXIT STATUS
0 update-fonts-dir ran successfully. 1 update-fonts-dir experienced a fatal error; see the section on diagnostic messages above. 2 update-fonts-dir was invoked with invalid arguments. BUGS
See the Debian Bug Tracking System <http://bugs.debian.org/xfonts-utils>. If you wish to report a bug in update-fonts-dir, please see /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command. AUTHOR
update-fonts-dir was written by Branden Robinson. SEE ALSO
mkfontdir(1x) Debian Project 2004-11-11 update-fonts-dir(8)
All times are GMT -4. The time now is 02:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy