But I guess all this is irrelevant for the moment, as apparently there is no basis to expect to be able to use the Scan feature, at least for the time being.
I just ran this again (as su)… you’ll see where I hit ctrl-C to terminate (this is the point where as I said, it “hangs”). When this is a very new type you bought, support may eerge in the future of course (does not help you now :(). And when it is very long, at least the first 10-20 lines or so (of course between CODE tags). Tells much, much more with far less words to type by you.Īlso in this case it could be usefull to post the script. Then we would have seen what your working directory is, if you are root, what exactly you typed (that is about the only thing you gave), what came out of it (even if it is nothing, there would at least be he ^C when you aborted it). It is better to copy/paste from the terminal window the prompt, the command, the output and the next prompt between CODE tags in your post (CODE tags you get by clicking the # button in the toolbar of the post editor). , is that invented by yourself, or from some docs? Are you doing this as root? I ask because you do not post very many computer facts. In any case, it is still strange that the script “hangs” as you say. Yes, when you would have known that, you wouln t have tried of course.
0 kommentar(er)
