I'm still having problems with that memory issue using 3.0.10 with v.2
of the printing patch + the one line patch from Jerome Borsboom. My
production server has completely frozen a couple times in the past
couple weeks, and did so again this morning. This time before
restarting samba I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Schlenk wrote:
| I'm still having problems with that memory issue
| using 3.0.10 with v.2 of the printing patch + the
| one line patch from Jerome Borsboom. My production
| server has completely frozen a couple times in the past
| couple weeks,
| I'm still having problems with that memory issue
| using 3.0.10 with v.2 of the printing patch + the
| one line patch from Jerome Borsboom. My production
| server has completely frozen a couple times in the past
| couple weeks, and did so again this morning.
| This time before restarting
On Jan 26, 2005, at 10:46 AM, Adam Tauno Williams wrote:
Our central print server runs 3.0.10 and several times a day one of the
smbd processes starts to grow. We simply keep an eye on it and can
kill
-9 the offender, the rest of the smbd processes seem oblivious to the
event and trundle along
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Schlenk wrote:
|
| Not so much. It's the main smbd process, the one running as root.
Every smbd process runs as root unless it is doing
something on behalf of the user. But I'm assuming you
really do mean the parent smbd process. This is a
On Jan 26, 2005, at 11:27 AM, Gerald (Jerry) Carter wrote:
top reports a VSZ number (process' total amount of virtual memory
allocated) for each process. What does that say?
It was under a MB for the process that was pegged, and I didn't get a
chance to check for the total of all the other smbd
On Wed, Jan 26, 2005 at 11:46:32AM -0500, Adam Tauno Williams wrote:
Our central print server runs 3.0.10 and several times a day one of the
smbd processes starts to grow. We simply keep an eye on it and can kill
-9 the offender, the rest of the smbd processes seem oblivious to the
event
