yes, a local flag is appropriate, I'll add that. I have to admit I haven't read the entire man pages of each tool I use, preferring to stick with what works until I actually am forced to learn more due to some bug.

The real question is if this patch fixed it? I can see a circumstance where one of the directories is mounted on a remote machine, but that would be odd, but if it's now working I think I'll leave it as is.

Does inxi -plou hang as well? that uses a similar method to get the initial data, and I've never seen a hang on nfs or smb, nor has any such hang been reported yet, except for your case. Do you have anything unusual or non standard in your setup or network?

The problem, of course, with man pages, is they tend to assume you already know the answer and just need a reminder. For example, -P as in posix output format I'm sure means something to someone, but sadly, I am not in that set, but I guess I could google it, as everything, lol...

Oh, ok, found it: www.math.utah.edu/docs/info/fileutils_8.html

Some day man authors will realize that it's just as easy to write: the output per mount will be all on one line, no breaks, as it is to write: posix output format, or even better, to just write both and be done with it.

That's quite useful, I'll add that to inxi too.

<update>Added -l and -P to smxi df. Easier that way, less error prone.
Back to top

I think it has, but it's hard to be sure, because the hang is intermittent, as is the problem with smxi.


It did just now when I tested it, but then I put the fix in, and it worked, so I took it out again, and it still worked.


Doesn't everybody? :-)
I have one machine running Squeeze, one with Lenny (drives mounted via NFS), and a notebook with MS Windows 7 (wireless LAN, and drives mounted via SMB). I blame Windows for most problems, but that may be just prejudice ... ;-D
though it does have a habit of randomly dropping the network connection for no good reason that I can find. I think it's at those times that the Squeeze system hangs, trying to access the SMB drives that are no longer reachable. There must be a network timeout parameter somewhere that's set way too high.
Back to top

That fix is in inxi now too, the -P part, and in smxi, so no need to do/undo anything as long as you have the latest inxi, and smxi of course updates itself automatically, so that will always be the latest.

Given the number of users (vast) of both inxi and smxi over the years, I'm assuming there is something glitching in your systems, otherwise that type of hang would have been reported many years ago.

However, in smxi, having it be -P and -l for the partition information is fine, since that's all that's needed, and it does help tighten it up a bit.

If inxi hangs once then not the second time, i'm guessing the data gets cached, sort of, then the second access it's there.

Issues like this can be so many things, networking, routers, hardware, whatever, but there's not much more that can be done on this end. Well, no, let me rephrase that, this is the most that can be done.

If you're seeing smxi hangs, I'm guessing you're getting some type of network lag on smxi, because it's downloading chunks that need updating. inxi lags would only be due to the network itself, or the machine/hardware, and should be considered as warning signs of something wrong in your systems or network is my guess.
Back to top