UNIX for Advanced & Expert Users

Hi.

Given that information, I would try:

Code:

cp test.log back.log
sed '1,100d' test.log>temp.log 
# mv temp.log test.log
cp temp.log test.log

(comment, "#", only for illustration, not needed in the sequence)
that should preserve the inode for test.log ... cheers, drl

Truncating an app's logfile only works if the application supports it. If it doesn't, you're stuck with restarting the application.

Does cp explicitly guarantee the same inode? Looking at

cp

-- explains how open will be called on the target file, which would imply the same inode.

IMHO @drl's solution in post #15 nearly fulfils the requirement.

Reading between the lines, we are again presented with a faulty solution without a definition of the actual problem.

Taking into account Corona688's comment about inodes, this code would be safer on most unix/Linux Operating Systems:

Code:

cp test.log back.log
sed '1,100d' test.log>temp.log 
cat temp.log > test.log

I have used a similar code construct (albeit with grep -v)to remove persistent irrelevant entries from a system log where it was causing unwanted alerts (pending a fix).

Thanks for your reply. inode problem is resolved.