CatBus;193990 Wrote:
>
> However, that does bring up an interesting point. If rebooting the
> server always brings it back after it suffers an episode, I could
> schedule a periodic "therapeutic/preventative reboot". Just like
> managing a Windows server...
Flawed logic.
That would apply in a case where the server crashed with a given period
of, say, X. Reboot at X-1 and you would not have the crash.
In an event-driven failure, that would not stop the event from
happening and therefore would have no positive impact.
"No space left on device" is from libc (well, from something calling
perror() in libc). It is what is returned when errno is ENOSPC. (Most
obvious example is a write() system call to, well, a full device. "man
2 write" for example.) This can also happen if you run out of inodes
("df -i" to show the current inode count, usually not a problem since
music files tend to be large and therefore not use many inodes... much
more likely on a file system with lots of small files like a mail or
usenet server), or on non-native filesytems, running into limitations
of the file system (ie, running out of "clusters" on fat32). Again,
not likely to be the problem.
The SB has no mechanism to log to the server.
--
snarlydwarf
------------------------------------------------------------------------
snarlydwarf's Profile: http://forums.slimdevices.com/member.php?userid=1179
View this thread: http://forums.slimdevices.com/showthread.php?t=34229
_______________________________________________
unix mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/unix
