10-05-2010
Quote:
Originally Posted by
remi75
rebooting is not an option , so no reinstall , thnx anyway
Given the bad shape of your system, rebooting is in fact your only option. Your server is doomed to crash sooner or later anyway.
Quote:
from now on i will always stick a statically linked busybox on all my servers !!
You'd rather say: from now on, I will refrain to mess with critical files on my servers ...
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
what is a critical section?why multipleprocesses or multiplethreads cant be given a chance to access the critical section?
please explain me with an example.
thanks (3 Replies)
Discussion started by: compbug
3 Replies
2. Shell Programming and Scripting
We have a batch job which runs and checks for certain files on a server and retrieves them to our server.
But from last few hours the job is not running correctly.
It gives msg file now found when there are files present on the server..
Nothing has been changed.................. (1 Reply)
Discussion started by: shikhakaul
1 Replies
3. Shell Programming and Scripting
Hello everyone !
Please have a minute and see if you know how to script this
I have a file like this:
"create table ....
...
create index n112 on ...
...
create table ...
....
create index n113 on...
...
create table ...
create index n112 on ...! duplicate
... (1 Reply)
Discussion started by: sotoc79
1 Replies
4. Shell Programming and Scripting
hi all,
Please help me with rsync.
I configured rsync to preserve timestamps using the -a option.
When i renamed fileA to fileB on source machine I have to copies at the backup server.
The aim is to keep the most recent file.
fileA & fileB has same contents.
When i renamed fileB to... (2 Replies)
Discussion started by: coolatt
2 Replies
5. Red Hat
Hello,
I'm experimenting a problem on my rh server.
Red Hat Enterprise Linux AS release 3 (Taroon Update 8)
2.4.21-47.ELsmp #1 SMP i686 i686 i386 GNU/Linux
It started with a segmentation fault on
#id root
To resolve it, I've installed
coreutils-4.5.3-28.4.i386.rpm
But, I... (6 Replies)
Discussion started by: gogol_bordello
6 Replies
6. Solaris
Let's say someone accidentally renamed the lib directory in Solaris 8, and now they cannot get into the terminal or even rename the folder via file manager.What would one do? (37 Replies)
Discussion started by: jetjaguar
37 Replies
7. UNIX for Advanced & Expert Users
Hi,
I am using Ubuntu 8.04 64-bit (Hardy Heron LTS Desktop edition) OS on a 64-bit intel hardware (x86_64). I have wrongly renamed the /lib64/libdl-2.7.so shared library file and now hardly few commands are working. My Gnome UI display has gone and I could not establish any new connection via... (12 Replies)
Discussion started by: royalibrahim
12 Replies
8. Shell Programming and Scripting
Hi All,
I connected via rlogin in testing environment (ksh ) and placed an executable with -rwxr-xr-x permission.
eg: from my own unix box used : rlogin host -l user
But the exe was renamed by somebody. since it's only renaming none of the access time , modification time etc is altered.... (2 Replies)
Discussion started by: blackcat
2 Replies
9. Shell Programming and Scripting
Hi
Am trying to move a file from one name to another
When I do "ls" to check for the moved filename
I can see the file but when I try the same with a script am unable..
I think am doing some pretty silly error.. please help..
toMove=`ls | grep -E "partition.+"`
mv $toMove partition._org... (7 Replies)
Discussion started by: Priya Amaresh
7 Replies
10. Ubuntu
Hi...I'm new to Linux and was working on a home server. I have it operational with Samba Share as my NAS system. Unfortunately, while I was on Webmin I changed the Logical Volume Group Name and now I can't find the data I had saved on my Samba Server.
Can anyone help me recover those files?
... (0 Replies)
Discussion started by: pangil
0 Replies
LEARN ABOUT FREEBSD
rescue
RESCUE(8) BSD System Manager's Manual RESCUE(8)
NAME
rescue -- rescue utilities in /rescue
DESCRIPTION
The /rescue directory contains a collection of common utilities intended for use in recovering a badly damaged system. With the transition
to a dynamically-linked root beginning with FreeBSD 5.2, there is a real possibility that the standard tools in /bin and /sbin may become
non-functional due to a failed upgrade or a disk error. The tools in /rescue are statically linked and should therefore be more resistant to
damage. However, being statically linked, the tools in /rescue are also less functional than the standard utilities. In particular, they do
not have full use of the locale, pam(3), and nsswitch libraries.
If your system fails to boot, and it shows a prompt similar to:
Enter full pathname of shell or RETURN for /bin/sh:
the first thing to try running is the standard shell, /bin/sh. If that fails, try running /rescue/sh, which is the rescue shell. To repair
the system, the root partition must first be remounted read-write. This can be done with the following mount(8) command:
/rescue/mount -uw /
The next step is to double-check the contents of /bin, /sbin, and /usr/lib, possibly mounting a FreeBSD rescue or ``live file system'' CD-ROM
(e.g., disc2 of the officially released FreeBSD ISO images) and copying files from there. Once it is possible to successfully run /bin/sh,
/bin/ls, and other standard utilities, try rebooting back into the standard system.
The /rescue tools are compiled using crunchgen(1), which makes them considerably more compact than the standard utilities. To build a
FreeBSD system where space is critical, /rescue can be used as a replacement for the standard /bin and /sbin directories; simply change /bin
and /sbin to be symbolic links pointing to /rescue. Since /rescue is statically linked, it should also be possible to dispense with much of
/usr/lib in such an environment.
In contrast to its predecessor /stand, /rescue is updated during normal FreeBSD source and binary upgrades.
FILES
/rescue Root of the rescue hierarchy.
SEE ALSO
crunchgen(1), crash(8)
HISTORY
The rescue utilities first appeared in FreeBSD 5.2.
AUTHORS
The rescue system was written by Tim Kientzle <kientzle@FreeBSD.org>, based on ideas taken from NetBSD. This manual page was written by
Simon L. Nielsen <simon@FreeBSD.org>, based on text by Tim Kientzle <kientzle@FreeBSD.org>.
BUGS
Most of the rescue tools work even in a fairly crippled system. The most egregious exception is the rescue version of vi(1), which currently
requires that /usr be mounted so that it can access the termcap(5) files. Hopefully, a failsafe termcap(3) entry will eventually be added
into the ncurses(3) library, so that /rescue/vi can be used even in a system where /usr cannot immediately be mounted. In the meantime, the
rescue version of the ed(1) editor can be used from /rescue/ed if you need to edit files, but cannot mount /usr.
BSD
July 23, 2003 BSD