*shut

If you drop to the command line and run *shut it completely fubars the networking stack.
It’s not often I need to use it, but if there is a file left open and I need to shut it the only option is to reboot as far as I can see.
The network stack should recover from this really shouldn’t it?
This is on an Pandaboard ES, using 5.21 – but It’s had this issue since I started using RISC OS again (from Oct last year)
I’m guessing it’s the Ethernet over USB that gets fried, as that completely disappears from the configuration options if you run shut.
I accept I shouldn’t leave open files etc. etc.
which I don’t deliberately obviously, but there are times that I’ve missed dealing with abnormal conditions and my program exits without shuting files, and when I find them I’d prefer to fix it run *shut and retry rather than rebooting if possible.

I have a program called ListOpen that displays a list of open files, then in BASIC a quick CLOSE#xx.

If it’d be a help to you, I could put together a command line program to do this in one go?

There are many, many programs which will deal with this problem for you properly. You should never, ever need to use *Shut.

http://www.starfighter.acornarcade.com/mysite/utilities.htm#wimpdrain

I use an app called !ResRec written by Andrew Pullan (1999), but is seems to have disappeared off the interweb….
It runs on the Pi and the Beagle as well.

Thanks guys, that’s great!
!WimpDrain looks ideal, pain gone!
I always used shut in the RO 2/3 days…bad habits die hard i guess!
***blush***

On the other hand, something that can’t cope with its files being closed ought to trap OS_Find and not allow this…

I use an app called !ResRec written by Andrew Pullan (1999), but is seems to have disappeared off the interweb….

http://wayback.archive.org/web/20081202232700/http://www.users.zetnet.co.uk/apullan/apps/index.html

Somethings never truly go away. I like big libraries, particularly ones with proper books but this one has a fast index :-)

I think we use !CloseFiles. Though that only works locally. If I open a zip file on a remote machine using sharefs it can sometimes leave the file open.
Does anyone know of a utility to shut files on a remote computer?

You should never, ever need to use *Shut.

…in an ideal world. If everything always went according to plan and never went wrong. Meanwhile, on planet Earth…

The corollary is that though it might break some applications, the OS itself should definitely be able to cope with using one of its own commands!

This isn’t some third party hack, it’s a very long standing bit of functionality that always used to be benign. For example, the FontManager specifically copes with its files being closed.

The network stack ought to too.