please note:
"/etc/init.d/samba stop" ...SYSVinit command using "pkill smbd ; pkill nmbd"
so such command issued in global zone will kill all Samba's running in
non-global zones!!!
Currently this issue is solved tracking the smbd.pid, nmbd.pid and winbind pid
's by "start method" called from s
The blastwave.org Samba distribution doesn't have this issue: its shutdown
(/etc/init.d/cswsamba stop) uses the pid IDs for smbd, nmbd, and winbindd
stored in /opt/csw/var/locks/.
A quick FYI on using the blastwave distribution: If you are using sparse zones
and need to run Samba with winbind,
On 10/13/06, Jiri Sasek <[EMAIL PROTECTED]> wrote:
please note:
"/etc/init.d/samba stop" ...SYSVinit command using "pkill smbd ; pkill nmbd"
so such command issued in global zone will kill all Samba's running in non-global zones!!!
Currently this issue is solved tracking the smbd.pid, nmbd.pid
Jiri Sasek wrote:
please note: "/etc/init.d/samba stop" ...SYSVinit command using "pkill smbd ;
pkill nmbd" so such command issued in global zone will kill all Samba's running
in non-global zones!!!
Currently this issue is solved tracking the smbd.pid, nmbd.pid and winbind pid
's by "start meth
