Re: Taking input line by line from a config file in Bash

[Matthew_S]

I see what you're saying.  That's interesting about cat, thanks for the heads
up.

while read line
do
{
echo
$line > /dev/null && echo $line "PASSED" || echo $line
"FAILED"
} >> $RESULTS
done < $FILE
exit 0

This does the same thing, but seems to be more streamline... cleaner.  Those
are some useful points for future reference.  Thanks again.

Matthew
-- 
View this message in context: 
http://www.nabble.com/Taking-input-line-by-line-from-a-config-file-in-Bash-tp14575394p14593790.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.

Finding out current inode size

[Matthew_S]

I've been trawilng the web trying to find out how to get the current inode
size for a file.  I now know how to change the max inode size for the
system;

mkfs -i size=xxx

which also begs the question how to find out the current limit of the
system.  I'm guessing it'll be the default 256 bytes, but I'd like to be
sure.

The reason I'd like to know the current inode size of a file is because I'd
like to create a large enough number of extended attributes in order to test
the inodes boundaries and the subsequent handling.
-- 
View this message in context: 
http://www.nabble.com/Finding-out-current-inode-size-tp14599119p14599119.html
Sent from the Gnu - Bash mailing list archive at Nabble.com.