Paul Ackerman skrev:
Do you mean the samba installation or the distro installation? I'm getting on the dabian list for more info.
The signal 11 means that you have a memory allocation fault. This could be due to a number of things, including incorrect libraries linked into binaries, or faulty memory.
If other Debian users are using the same Samba version as you with success, and it's a Debian package, then signal 11 would tend to point to faulty hardware (RAM).
SIGHUP is simply a signal to a daemon to re-read its config file(s).
--Tonni
--
Tony Earnshaw wrote:
Paul Ackerman skrev:
I'm new to the list and pretty much a newbie to linux and samba. I'm quick learner though.
You'd bloody well better be ;)
I have been losing my samba share upon ocasion recently, below is a portion of the syslog from the time period that I think is when the share goes down. A reboot of the server or a restart of the smbd fixes the problem (....until it happens again)
I don't know what SIGUP is or why this happens, any help would be great.
It's not so much the SIGHUP. which could be normal.
It's more the signal 11, which shows either that your installation is crap or your hardware is crap.
Whichever one depemds on your skills as Linux system administrator to fathom out. Which means for you catch 22. Get onto your distro mailing list and ask tehere.
--Tonni
!DSPAM:425ca127314251200581864!
No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.9.6 - Release Date: 4/11/2005
!DSPAM:425ca127314251200581864!
--
mail: [EMAIL PROTECTED] http://www.billy.demon.nl
They love us, don't they, They feed us, won't they ... -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
