Your script looks like it would send one email per ldap suffix that has a problem - and that's the issue right?
I think you are wanting one email containing a list of all the failing suffixes?
In which case, try this:
(Untested)
BTW, The linefeed between errors} and ${i}" is not accidental, you want that in there
I am hoping someone can help me with this one.
I am writing a ksh script on Solaris. I want to read in host names and some other info from a file, do an "rsh host 'shutdown'" (or any uname for now until I get it working), and then be given some options. The problem is I am using while read... (2 Replies)
Hi,
Can anyone please help me: i'm trying to read a file with directory-names , then go to that directory and read another (output) file to perform some tasks per line (second read line in the part of script below).
The problem is that after the nested while loop has finished, the first while... (7 Replies)
Hi all!
I'm really hoping you can help me out here; now i have searched and searched and have at least worked out that you can't have a nested if statement with a 'done' in it (as i have) as you're killing the parent before the child.
So here's what i have, and here's hoping someone can help... (2 Replies)
I'm trying to write case statements with 'if statements' embedded inside of them. I'm using the korn shell but it's not functioning.
If I want to see if a string exists in a file and then perform an action, what would be the best way to do this?
For file "asg51fin" to delete a line if a... (1 Reply)
I'm just having a bit of trouble running this code. It tells me that there's a syntax error on line 29. Any help appreciated.
#!/usr/bin/perl
#
# Phone Book Application
#
%phonebook = (
"Wayne", '34687368',
"Home", '378643287',
"Work", '017374637',
"School",... (2 Replies)
Hi,
Below is my script in which i am using nested while loop to read two files and move the files to a remote server.
My issue is that the 2nd while loop doesn't stop executing and it keeps on executing.
Can someone please let me know where i have gone wrong.
myFile=$ESER_TEST_FILES
... (2 Replies)
hi,
this is my script #!/bin/ksh
cat temp_file.dat | while read line
do
read test
if ]; then
break
else echo "ERROR"
fi
done
when i execute this code , the script does wait for the user input . it directly prints "ERROR" and terminates after the no. of times as there... (3 Replies)
I need to check if an entry input by the user is in a file. If so, I need to run a command, and if it does not exist then it should output entry does not exist.
So I have so far...
echo "Enter record:"
read record
//command || //command
Can I use an if statement to do this? (3 Replies)
greetings,
the following code isn't working as i expect it to. the first dbl brackets do but the second set gets ignored. ie: if i'm on t70c6n229 it echoes "Something" and i expect it not to. what am i missing?
if " ]] || " ]]; then
echo "Something"
fi
thanx! (9 Replies)
While working on awk programming, i found that it doesn't understand 'read' statement. Then what's the use of 'continue' and 'break' statement in awk.
For ex:
awk '{k=1; while (k<10) {print $0; k++}}' emp.lst
Now, please say if I want to put the logic that after priting 1 line, it will ask for... (13 Replies)
Discussion started by: ravisingh
13 Replies
LEARN ABOUT CENTOS
fsck.jfs
jfs_fsck(8) JFS utility - file system check jfs_fsck(8)NAME
jfs_fsck - initiate replay of the JFS transaction log, and check and repair a JFS formatted device
SYNOPSIS
jfs_fsck [ -afnpvV ] [ -j journal_device ] [ --omit_journal_replay ] [ --replay_journal_only ] device
DESCRIPTION
jfs_fsck is used to replay the JFS transaction log, check a JFS formatted device for errors, and fix any errors found.
device is the special file name corresponding to the actual device to be checked (e.g. /dev/hdb1).
jfs_fsck must be run as root.
WARNING
jfs_fsck should only be used to check an unmounted file system or a file system that is mounted READ ONLY. Using jfs_fsck to check a file
system mounted other than READ ONLY could seriously damage the file system!
OPTIONS
If no options are selected, the default is -p.
-a Autocheck mode - Replay the transaction log. Do not continue fsck processing unless the aggregate state is dirty or the log replay
failed. Functionally equivalent to -p. Autocheck mode is typically the default mode used when jfs_fsck is called at boot time.
-f Replay the transaction log and force checking even if the file system appears clean. Repair all problems automatically.
-j journal_device
Specify the journal device.
-n Open the file system read only. Do not replay the transaction log. Report errors, but do not repair them.
--omit_journal_replay
Omit the replay of the transaction log. This option should not be used unless as a last resort (i.e. the log has been severely
corrupted and replaying it causes further problems).
-p Automatically repair ("preen") the file system. Replay the transaction log. Do not continue fsck processing unless the aggregate
state is dirty or the log replay failed. Functionally equivalent to -a.
--replay_journal_only
Only replay the transaction log. Do not continue with a full file system check if the replay fails or if the file system is still
dirty even after a journal replay. In general, this option should only be used for debugging purposes as it could leave the file
system in an unmountable state. This option cannot be used with -f, -n, or --omit_journal_replay.
-v Verbose messaging - print details and debug statements to stdout.
-V Print version information and exit (regardless of any other chosen options).
EXAMPLES
Check the 3rd partition on the 2nd hard disk, print extended information to stdout, replay the transaction log, force complete jfs_fsck
checking, and give permission to repair all errors:
jfs_fsck -v -f /dev/hdb3
Check the 5th partition on the 1st hard disk, and report, but do not repair, any errors:
jfs_fsck -n /dev/hda5
EXIT CODE
The exit code returned by jfs_fsck represents one of the following conditions:
0 No errors
1 File system errors corrected and/or transaction log replayed successfully
2 File system errors corrected, system should be rebooted if file system was mounted
4 File system errors left uncorrected
8 Operational error
16 Usage or syntax error
128 Shared library error
REPORTING BUGS
If you find a bug in JFS or jfs_fsck, please report it via the bug tracking system ("Report Bugs" section) of the JFS project web site:
http://jfs.sourceforge.net/
Please send as much pertinent information as possible, including the complete output of running jfs_fsck with the -v option on the JFS
device.
SEE ALSO fsck(8), jfs_mkfs(8), jfs_fscklog(8), jfs_tune(8), jfs_logdump(8), jfs_debugfs(8)AUTHORS
Barry Arndt (barndt@us.ibm.com)
William Braswell, Jr.
jfs_fsck is maintained by IBM.
See the JFS project web site for more details:
http://jfs.sourceforge.net/
October 29, 2002 jfs_fsck(8)