First I need to start off by saying I've been a tech for Windows environment for almost 20 years now. With that being said, I've never touched unix/linux/aix before so all of this is new to me. If you can bare with me, I'll gladly provide any configs/logs you may need to help me.
I'm having an issue with SAMBA where the file contents are not refreshed immediately after the server (aix) changes the file. I have a program in windows that is reading a file across a SAMBA share. When I make changes to the file from the server side, the next file read still contains the old stale data content. If I read the file about 30 seconds later, the new content is displayed. My question is, is there any way to force these data to update immediately?
I've read somewhere that adding "refresh = 1" to the config file would do the trick but that doesn't seem to be working and isn't recognized by "testparm" anyway. I've also read that adding "kernel oplocks = yes" would do the trick but no go on that either.
Here is everything I can think to include:
I need to add that this is a centrify modified version of SAMBA to allow direct integration into their product, but they're saying this isn't their problem because the portion they modify for this doesn't affect this issue.
If there is more information necessary, please let me know and I'll add it.
Moderator's Comments:
Please use code tags. You got a PM with an explanation.
Hi all
I want to know how do I create a print queue using samba on AIX enviroment to print to file. Setup step require. Anyone please help me on this.
Vincent (2 Replies)
Hi All,
Great forums, a wealth of knowledge. We have just replaced our server room screen with a nice 15" LCD. We run CDE as the gui at the console. I think the refresh rate is too high for the LCD as I get an out of range error message on the screen.
Can anyone point me in the right... (1 Reply)
I'd like to make my AIX 5.3 box a member of my Windows 2003 AD. Is this possible? If so, what are the steps? What I'm really after is a way for my windows users to access files on my Samba shares with the exact same permissions, owner, etc. as they use when accessing files on a windows directory. (1 Reply)
I am looking for a way to issue a command or string of commands to repeatedly display new files that are written to the directory. I usually use ls -ltr to see the newest files at the bottom of the screen. I would like to automate this command to refresh what is displayed every second or so. Can... (3 Replies)
I have never installed Samba before and am having trouble. I downloaded the opt-samba-base.tar and the opt-samba-3.0.26a-AIX5 file as well and while it appears they both installed okay but it never created the /etc/samba or /usr/local/samba directories - just the /opt/pware/samba directory. I... (2 Replies)
I have 11 AIX (a mix of 4.3.3.0 and 4.3.2.0) on which I succesfully installed a Samba server. On two other systems, the smbd start command generates the following error message. Anybody ?
itocroot@TAGEN010: /usr/local/samba/bin $ ./smbd start
exec(): 0509-036 Cannot load program ./smbd because... (0 Replies)
Hello, I need assistance installing Samba on AIX 5.3 TL06. Smitty Install produces the following error message:
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
geninstall -I "a -cgNQqwXY -J" -Z -d... (5 Replies)
Please help, I'm wicked... :confused:
I'm trying to get Samba to work on an IBM pseries machine (AIX 5.3) to provide access to the server for a user to retrieve reports from her WinXP desktop. I've made the proper entires in the smb.conf file and tried runing the smbpasswd command to add the user... (4 Replies)
Hello,
I am trying to update Samba on my AIX 7.1 system as there is an issues with it, the smbd process coredumps and I have had no luck figuring it out why.
My approach is to try to re-install a newer samba and I have found the latest 3.x package for samba in ppc.rpm format at perlz.org
... (6 Replies)
I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users.
The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
LEARN ABOUT CENTOS
cupsaddsmb
cupsaddsmb(8) Apple Inc. cupsaddsmb(8)NAME
cupsaddsmb - export printers to samba for windows clients
SYNOPSIS
cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] -a
cupsaddsmb [ -H samba-server ] [ -U samba-user[%samba-password] ] [ -h cups-server[:port] ] [ -v ] printer [ ... printer ]
DESCRIPTION
cupsaddsmb exports printers to the SAMBA software (version 2.2.0 or higher) for use with Windows clients. Depending on the SAMBA configura-
tion, you may need to provide a password to export the printers. This program requires the Windows printer driver files described below.
OPTIONS
cupsaddsmb supports the following options:
-H samba-server
Specifies the SAMBA server which defaults to the CUPS server.
-U samba-user[%samba-password]
Specifies the SAMBA print admin username which defaults to your current username. If the username contains a percent (%) character,
then the text following the percent is treated as the SAMBA password to use.
-a
Exports all known printers. Otherwise only the named printers are exported.
-h cups-server[:port]
Specifies a different CUPS server to use.
-v
Specifies that verbose information should be shown. This is useful for debugging SAMBA configuration problems.
SAMBA CONFIGURATION
cupsaddsmb uses the new RPC-based printing support in SAMBA 2.2.x to provide printer drivers and PPD files to Windows client machines. In
order to use this functionality, you must first configure the SAMBA smb.conf(5) file to support printing through CUPS and provide a printer
driver download share, as follows:
[global]
load printers = yes
printing = cups
printcap name = cups
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
public = yes
guest ok = yes
writable = no
printable = yes
[print$]
comment = Printer Drivers
path = /etc/samba/drivers
browseable = yes
guest ok = no
read only = yes
write list = root
This configuration assumes a FHS-compliant installation of SAMBA; adjust the [printers] and [print$] share paths accordingly on your system
as needed.
MICROSOFT POSTSCRIPT DRIVERS FOR WINDOWS
The base driver for Windows 2000 and higher is the Microsoft PostScript driver, which is available on any system running Windows 2000 or
higher in the %WINDIR%SYSTEM32SPOOLDRIVERSW32X863 folder for 32-bit drivers and %WINDIR%SYSTEM32SPOOLDRIVERSX643 folder for
64-bit drivers.
The CUPS printer driver is preferred over the Microsoft driver since it supports the page-label, job-billing, and job-hold-until options
fully on all printers. However, currently only Windows 2000 and higher is supported by the Microsoft driver, so you will also need to get
the Adobe driver to support Windows 95, 98, and Me clients. The Adobe and Microsoft drivers for Windows 2000 are identical.
Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the
/usr/share/cups/drivers/x64 directory exactly as named below:
[Windows 2000 and higher]
ps5ui.dll
pscript.hlp
pscript.ntf
pscript5.dll
Note: Unlike Windows, case is significant - make sure that you use the lowercase filenames shown above, otherwise cupsaddsmb will fail to
export the drivers.
CUPS POSTSCRIPT DRIVERS FOR WINDOWS
cupsaddsmb can use the CUPS v6 PostScript printer driver for Windows, which is available for download from the CUPS web site.
The CUPS printer driver is preferred over the Adobe and Microsoft drivers since it supports the page-label, job-billing, and job-hold-until
options fully on all printers. However, currently only Windows 2000 and higher is supported by the CUPS driver, so you will also need to
get the Adobe driver to support Windows 95, 98, and Me clients.
Once you have extracted the driver files, copy the 32-bit drivers to the /usr/share/cups/drivers directory and the 64-bit drivers to the
/usr/share/cups/drivers/x64 directory exactly as named below:
[Windows 2000 and higher]
cups6.inf (from www.cups.org)
cups6.ini (from www.cups.org)
cupsps6.dll (from www.cups.org)
cupsui6.dll (from www.cups.org)
ps5ui.dll (from your Windows system)
pscript.hlp (from your Windows system)
pscript.ntf (from your Windows system)
pscript5.dll (from your Windows system)
Note: Unlike Windows, case is significant - make sure that you use the lowercase filenames shown above, otherwise cupsaddsmb will fail to
export the drivers.
ADOBE POSTSCRIPT DRIVERS FOR WINDOWS 95, 98, AND ME
cupsaddsmb can use the Adobe PostScript printer driver for Windows 95, 98, and ME, which are available for download from the Adobe web site
(http://www.adobe.com).
The Adobe driver does not support the page-label, job-billing, or job-hold-until options.
Once you have installed the driver on a Windows system, copy the following files to the /usr/share/cups/drivers directory exactly as named
below:
[Windows 95, 98, and Me]
ADFONTS.MFM
ADOBEPS4.DRV
ADOBEPS4.HLP
ICONLIB.DLL
PSMON.DLL
Note: Unlike Windows, case is significant - make sure that you use the UPPERCASE filenames shown above, otherwise cupsaddsmb will fail to
export the drivers.
KNOWN ISSUES
Getting the full set of Windows driver files should be easier.
SEE ALSO smbd(8), smb.conf(5), http://localhost:631/help
http://www.cups.org/windows/
COPYRIGHT
Copyright 2007-2013 by Apple Inc.
25 July 2007 CUPS cupsaddsmb(8)