s2.misc,comp.os.os2.networking.misc
e60649d1
18:28:58
s2.setup.misc:374 de.comp.os.os2.misc:1117 comp.os.os2.networking.misc:186
3ca1b5e8
From: "Herr Willms"
Am Fri, 23 Apr 2010 15:37:12 UTC, schrieb Herwig Bauernfeind
auf comp.os.os2.misc :
> smbprint checks which printer it should print to and prints the file to
> this printer in the OS/2 printing subsystem. Not more, not less. It
> requires exactly 5 parameters in the following order:
>
> %s = "spoolfile including path"
>
> %p = "printerqueue"
>
> %J = "jobname"
>
> %c = "pages"
>
> %z = "jobsize"
>
> The variables are filled with appropriate values from the Samba daemon
> when smbprint is executed.
My diagnosis is that this does not happen correctly, otherwise the
actual OS/2 would not complain about an "unknown Job-ID". I guess that
some of the quote characters are forgotten, or vanish by some of those
magic substitution rules of REXX or C.
On the other hand, when I execute smbprint.exe from the command
line, the printer driver does not complain about an "unknown Job-ID",
but does apparently not really get the print file. SMBPRINT.EXE also
deletes the print file when it works on it; maybe it is lost before
the printer driver can get hold of it...
Maybe I should mention that this is pure OS/2 4.5 (or 4.52, the one
found on the eCS 1.0 installtion discs).
> The variables are documented in the smb.conf documentation for the print
> command, look here
>
> http://samba.org/samba/docs/man/manpages-3/smb.conf.5.html
I'll have a look.
> 2.) smbprint.exe is not the only possibility to achieve printing
> capabilities with Samba. The variables provided by Samba provide a
> toolset to deal with.
My alternative would be to leave SAMBA completely out of the
equation, and try a pure TCP/IP LPR/LPD solution, but then,
unfortunately, I don't see (yet) how to configure this.
> It is perfectly acceptable to build a print command like in smb.conf
>
> print command = cmd.exe /c copy "%s" LPT2
I tried, and got a system choking which had to be reloaded via a
hard reset.
> 3.) sscc.exe, the "Samba Configuration Center", is able to create an
> appropriate printcap file. Menu "File" - "Create printcap". Printcap is
> located in %ETC%.
It can be found in various ETCs... but nevertheless I find this at
the end of the file log.smbd:
------- cut ----------------------
[2010/04/23 10:40:10, 1] lib/util_unistr.c:init_valid_table(260)
could not load C:\APPS\SAMBA/lib/valid.dat
[2010/04/23 10:40:10, 1] lib/util_unistr.c:init_valid_table(262)
creating default valid table
[2010/04/23 10:40:10, 3] printing/pcap.c:pcap_cache_reload(117)
reloading printcap cache
[2010/04/23 10:40:10, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2010/04/23 10:40:10, 3] printing/pcap.c:pcap_cache_reload(223)
reload status: error
[2010/04/23 10:40:10, 3] printing/pcap.c:pcap_cache_reload(117)
reloading printcap cache
[2010/04/23 10:40:10, 0] printing/pcap.c:pcap_cache_reload(159)
Unable to open printcap file /etc/printcap for read!
[2010/04/23 10:40:10, 3] printing/pcap.c:pcap_cache_reload(223)
reload status: error
----------------------- off --------------------------
[extra line breaks added to enhance readability]
> Hope this helps.
Not really...
Cheers,
L.W.
-------------------------------------------------------
--- Internet Rex 2.31
* Origin: Keine (1:261/20.999)
|
