This is likely another permissions issue.  Verify that ./ is the correct
directory for the pid file and that the Samba !JOB user has write access.

- Mark B.

Donna Garverick wrote:

> hi all!
>
> i seem to have the newest (supported) version of samba
> running :-)  i changed my samba startup jobs to match the
> supplied jobs.  problem is -- how to stop the jobs with
> resorting to abortjob?
>
> the relevant line from the new job (for nmb) is:
> !xeq nmbd207.samba.sys "-D -p 137"
> what i had been using is:
> !sh.hpbin.sys "-c '/SYS/SAMBA/NMBD -D&; echo $! >./nmbd.pid;
> wait'"
>
> see?  no .pid file is being created now.  is there a way to
> get the .pid file created using the new way?             - d

--
[log in to unmask]
Remainder of .sig suppressed to conserve expensive California electrons...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *