Thanks for the pointer Adam, it got me to look at the calling program a bit more which showed that the LD_LIBRARY_PATH variable was being set to "", and was then exported. After exporting the variable in my script, pop-up messages began to appear on my users desktops. All I need now is get the message and logfile to show the real file name of the job and not the Samba name - but that's another issue...
Peter -----Original Message----- From: Adam Nielsen [mailto:[EMAIL PROTECTED] Sent: Thursday, 8 June 2006 11:26 AM To: Peter Oram Cc: [email protected] Subject: Re: [Samba] Sending popup message via smbclient to w2k and winxpmachines > I added the following line to the script: > > LD_LIBRARY_PATH=/usr/lib:/usr/local/lib:/lib > > but still received the same message as below in the logfile. Try running "set > env-cmd.txt" from the command line and then run "set > env-script.txt" from within the script and then compare the list of environment variables, as it may not be LD_LIBRARY_PATH at fault. grep them for 'lib' perhaps. Oh - the script isn't running in a chroot jail or anything is it? It could be that smbclient can find the library, but it doesn't have permission to access it. Cheers, Adam. -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
