12-21-2001
Well, I assume the lecture on performing too many duties as root (for just this reason) wouldn't be welcome...
It looks like you'll have to grab the file from the latest good backup... You DO have backups, right?
I remember I did this with the first Linux box I ever set up... I was playing with my first few shell scripts as root, and managed to overwrite /bin/echo...
I didn't have a backup, but since it's GNU software, I just got a new one from their site!
You MAY (last resort) be able to find a machine that's EXACTLY like yours, and copy a binary over, although I would test it thouroghly before letting anyone use it... (YMMV on that one...)
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi all,
I can add a network printer with ADMINTOOL. However, I have a problem to add a network printer using lpadmin on my Sparc Solaris 8 box.
Here's the detail:
===============
lpadmin -p printername
lpadmin: ERROR: Missing -U or -v option.
To Fix: Local printer must have a port... (2 Replies)
Discussion started by: andrec
2 Replies
2. Solaris
Can some one tell me how to configure the printer on solaris
printer name = A
printer server address : 172.21.19.6 (3 Replies)
Discussion started by: krishan
3 Replies
3. UNIX for Dummies Questions & Answers
Hi Guys.
I moved my root partition, deleted the old one and set GRUB up using Yast.
It all booted OK when I tested it but the second reboot has just brought me straight onto a GRUB promt
GRUB > _
Any help much appreciated. I don't know anything about GRUB and the stuff I find on google is... (1 Reply)
Discussion started by: d11wtq
1 Replies
4. UNIX for Dummies Questions & Answers
Hi - Dummy question #1....
We either use the Hewlett Packard HPPI too or LPADMIN command to setup out printers. Is there an LPADMIN command that will show you the default config of a particular printer.
Ideally looking to see default font, CPI settings etc.
Thanks.
BravehearT1326 ... (1 Reply)
Discussion started by: BravehearT1326
1 Replies
5. Shell Programming and Scripting
I apologize for the long post. I have a lot of info...
I am trying to write a script that will add a network printer (or several) to a system using information read in from a text file. My problem is the spaces in the PPD file name, I'm not sure how to put the file name in or how to read it back... (2 Replies)
Discussion started by: HalfNube
2 Replies
6. HP-UX
When we executed a lpadmin command, the following error was output.
# lpadmin -phsaprinter -v/home/hoge/lpfile -mrmodel -ocmrcmodel
-osmrsmodel -ormhsaprinter -orphsaprinter
lpadmin: can't access file "/home/hoge/lpfile"
/home/hoge/lpfile is the file other user made.
The... (1 Reply)
Discussion started by: madhurtripathi
1 Replies
7. Solaris
lpadmin configuration issues on Solaris 10 Zone. I have configured a print queue using lpadmin command to print to print file server.
Source server is a Solaris Zone running Solaris 10.
Destination file print server is running OS AIX 5.3.
I do not get errors when issuing the lp command to... (0 Replies)
Discussion started by: primeaup
0 Replies
8. UNIX for Advanced & Expert Users
the problem i encountered is that lpadmin when encounters a failure doesn't cleanup properly .so the next time i use the same printer name it doesn't allow me to do so .saying interface directory can't be created .what can be done to solve this out ?please help .. (3 Replies)
Discussion started by: rahulpatro
3 Replies
9. Shell Programming and Scripting
Hi All,
I'm new to shell scripts.
I have the following LPADMIN script that runs ok when I run in in OSX Automator "Run shell Scripts":
Shell: /bin/bash
here is the line:
/usr/sbin/lpadmin -p Copy-room-ljetP4015 -E -v lpd://192.168.1.1 -m /Library/Printers/PPDs/Contents/Resources/HP\... (3 Replies)
Discussion started by: abk
3 Replies
LEARN ABOUT DEBIAN
expire_backups
EXPIRE_BACKUPS(1) S3QL EXPIRE_BACKUPS(1)
NAME
expire_backups - Intelligently expire old backups
SYNOPSIS
expire_backups [options] <age> [<age> ...]
DESCRIPTION
The expire_backups command intelligently remove old backups that are no longer needed.
To define what backups you want to keep for how long, you define a number of age ranges. expire_backups ensures that you will have at least
one backup in each age range at all times. It will keep exactly as many backups as are required for that and delete any backups that become
redundant.
Age ranges are specified by giving a list of range boundaries in terms of backup cycles. Every time you create a new backup, the existing
backups age by one cycle.
Example: when expire_backups is called with the age range definition 1 3 7 14 31, it will guarantee that you always have the following
backups available:
1. A backup that is 0 to 1 cycles old (i.e, the most recent backup)
2. A backup that is 1 to 3 cycles old
3. A backup that is 3 to 7 cycles old
4. A backup that is 7 to 14 cycles old
5. A backup that is 14 to 31 cycles old
Note If you do backups in fixed intervals, then one cycle will be equivalent to the backup interval. The advantage of specifying the age
ranges in terms of backup cycles rather than days or weeks is that it allows you to gracefully handle irregular backup intervals.
Imagine that for some reason you do not turn on your computer for one month. Now all your backups are at least a month old, and if
you had specified the above backup strategy in terms of absolute ages, they would all be deleted! Specifying age ranges in terms of
backup cycles avoids these sort of problems.
expire_backups usage is simple. It requires backups to have names of the forms year-month-day_hour:minute:seconds (YYYY-MM-DD_HH:mm:ss) and
works on all backups in the current directory. So for the above backup strategy, the correct invocation would be:
expire_backups.py 1 3 7 14 31
When storing your backups on an S3QL file system, you probably want to specify the --use-s3qlrm option as well. This tells expire_backups
to use the s3qlrm command to delete directories.
expire_backups uses a "state file" to keep track which backups are how many cycles old (since this cannot be inferred from the dates con-
tained in the directory names). The standard name for this state file is .expire_backups.dat. If this file gets damaged or deleted,
expire_backups no longer knows the ages of the backups and refuses to work. In this case you can use the --reconstruct-state option to try
to reconstruct the state from the backup dates. However, the accuracy of this reconstruction depends strongly on how rigorous you have been
with making backups (it is only completely correct if the time between subsequent backups has always been exactly the same), so it's gener-
ally a good idea not to tamper with the state file.
OPTIONS
The expire_backups command accepts the following options:
--quiet
be really quiet
--debug
activate debugging output
--version
just print program version and exit
--state <file>
File to save state information in (default: ".expire_backups.dat")
-n Dry run. Just show which backups would be deleted.
--reconstruct-state
Try to reconstruct a missing state file from backup dates.
--use-s3qlrm
Use s3qlrm command to delete backups.
EXIT STATUS
expire_backups returns exit code 0 if the operation succeeded and 1 if some error occured.
SEE ALSO
expire_backups is shipped as part of S3QL, http://code.google.com/p/s3ql/.
COPYRIGHT
2008-2011, Nikolaus Rath
1.11.1 August 27, 2014 EXPIRE_BACKUPS(1)