Black Hole
May contain traces of nut
What's that? It's not listed in the repo.Is nohup installed or installable? (not near my boxes, so I can't try it myself at the moment)
Last edited:
What's that? It's not listed in the repo.Is nohup installed or installable? (not near my boxes, so I can't try it myself at the moment)
I just tried it through webshell; the session is terminated by closing the web page (or, at least, if it isn't terminated connecting to the web server opens a new page with no idea what happened to the old session).It could probably do with a fix-disk, but I don't have any way to keep a session open. Maybe running it through webshell keeps the session open even without something on the other end?
What's that? It's not listed in the repo.
No, it's nothing to do with the package.Would a force reinstall be better than an uninstall and reinstall?
You could always run e2fsck manually on the big partition and divert the output to file. Something like this:It could probably do with a fix-disk, but I don't have any way to keep a session open.
humax# umount /mnt/hd2
humax# dd if=/dev/zero of=/mnt/hd3/.swap bs=1M count=1024
humax# mkswap /mnt/hd3/.swap
humax# swapon /mnt/hd3/.swap
humax# e2fsck -y /dev/sda2 </dev/null >/mnt/hd3/manual.log 2>&1 &
humax# swapoff /mnt/hd3/.swap
humax# rm /mnt/hd3/.swap
humax# cat /mnt/hd3/manual.log
humax# rm /mnt/hd3/manual.log
Yes, it would be nice.I think it would be very useful to arrange fixdisk to run unattended and have the output buffered for next connection.
That'a what happens when you don't give the exact commands and responses.In fact, it's all been a red herring.
Why don't you say what you were trying? Then somebody will tell you why it didn't work.This time I noticed a small report at the bottom of the dialogue saying that the string I was trying to rename the recycle bin to was invalid, and that's why it wasn't taking. I tried a different modification and it worked fine. What are the requirements?
I didn't notice the message appear last week. It's pretty small, not in an obvious place, and I was working under difficult circumstances.That'a what happens when you don't give the exact commands and responses.
Again, I'm reporting some hours after the event. If you can't remember the circumstances exactly, it's better not to guess something.Why don't you say what you were trying? Then somebody will tell you why it didn't work.
I think that means it's not allowed to start with a space. I would have been trying to make it start with a space, because I seem to recall recently a folder being deliberately created with a leading space so it gets pushed to the bottom of the media list. I was trying to move the dustbin out of the user's view.Code:if {![regexp -nocase {^\[?[- a-z_]+\]?$} $name]} { puts "Invalid dustbin name." exit }
It can at the Linux level, but it's a completely ridiculous thing to do IMHO.Can a folder name be just spaces??
Not if it effectively hides it in plain view.It can at the Linux level, but it's a completely ridiculous thing to do IMHO.
I tried that, too, but no joy :-(It's working on ours OK.
One stopped a few weeks ago but that was because it was disabled following two crashes in quick succession - a fix-flash-packages command sorted it.
Run thefix-flash-package
diagnostic from the web interface diagnostics screen.
This can be a bit tricky. Try uninstalling the undelete package then reboot. Then reinistall undelete and reboot again.Already did this, more than once :-(
This can be a bit tricky. Try uninstalling the undelete package then reboot. Then reinistall undelete and reboot again.