Is there any tool (or maybe registry configuration, whatever) that turns a Windows XP machine into a multicast ntp server? I am looking for a freeware solution preferable.
I have two networks: 192.168.13.0/24 (blue) and 192.168.15.0/24 (green).
Computer A is connected to the 13-net, only. Computer B has two interfaces, one in each network.
There is third computer that acts like a router and connects the 13-net to the 15-net (only in this direction).
Now, I'd like to ping 192.168.15.100 from computer A to B. Unfortunately there is never a reply. But when I use a hub instead of a switch it works.
In my opinion the ping packet travels through the switch to the router (which is the default route/gateway for A). The router sends the packet back to the switch to B. Probably B receives it on its 15-net interface but answers with it's 15th interface? Is this possible?
The problem is, that B may have only a gateway 192.168.13.50 - but I am not really sure of it (B is a embedded system with limited configuration possibilities).
Can anyone explain what happens here? Thank you!
I started a long running background-process (dd with /dev/urandom) in my ssh console. Later I had to disconnect. When I logged in, again (this time directly, without ssh), the process still seemed to to run.
I am not sure what happened - I did not use disown. When I logged in later, the process was not listed in top at first, but after a while it reclaimed a high CPU percentage, as I expected. So I assume dd is still running.
Now, I'd like to see the progress. I use kill -USR1 <pid> but nothing is printed. Is there any way to get the output again?
I am wondering what's the purpose of a BBU. My first understanding was, that it enables the cache to write the data to the disc during a power failure. But some specifications say that a BBU can hold its data for up to 72h. I'd expect the data to be written to the disc within milliseconds (given, that the disc still has power, too).
So should a BBU not just protect the cache, but the whole disc for some seconds, too? Wouldn't that be even more secure, because the cache data is written to the disc instead of being around in the cache and waiting for power again? After a second or so, the disc could be shut down.
I have a server (debian etch) that sometimes prompts the following message (right after starting/rebooting the computer):
The system is going down on <time in past>
Running a shutdown -c results in:
Cannot find pid of running shutdown.
Because of this problem normal users can no longer login, only root access is possible.
Has anyone seen this problem or has anyone a suggestion for me? thx.