Sponsored Content
Operating Systems SCO Visionfs printing Windows2003 printserver Post 302363226 by jpradley on Monday 19th of October 2009 06:02:36 PM
Old 10-19-2009
This is straight out of the VFS manual:

Code:
Example
A Windows 2000 server meringue shares a printer named color. If the UNIX
superuser types this:
visionfs print --install salesprinter meringue color
Then any UNIX user may print the file report.ps to \\meringue\color using this
command:
lp -d salesprinter report.ps
The Windows 2000 server meringue must have a user account vfsprint, with
password vfsprint, and that account must have printing privileges, for
printing to succeed. Alternatively, the user may supply different credentials,
for example:
lp -d salesprinter -o user=rod -o passwd=hull report.ps

 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

VisionFS error

I have a Unix SCO 5.0 connected to the Windows 2000 domain, the administrator was able to access any share folders from the Unix server until I changed the administrator password. When the administrator user tries to connect to the Unix Share a message comes up: Incorrect password or unknown... (0 Replies)
Discussion started by: gonzalez109
0 Replies

2. SCO

VISIONFS Print Problems

Hello there, I have a problem with the "visionfs print" command on Sco Open Server. I am able to print to matrix printers, attached to windows workstations, but when I send a file to a laser jet (HP 1020 for example) the printer hangs. If any one of you have any idea why this happen please... (1 Reply)
Discussion started by: zaxos
1 Replies

3. UNIX for Dummies Questions & Answers

Joining UNIX to a Windows2003 Domain

Hey everyone, We have a Windows2003 Domain here at my workplace. I'm getting ready to switch over our bottom floor to the new domain. Will they still be able to see our UNIX machine that is setup now (on our workgroup) or will I need to join the UNIX machine to the domain. If that is the case... (4 Replies)
Discussion started by: Duki
4 Replies

4. SCO

Visionfs & subnet problem

Hi everybody, i'm a french guy (so excuse my english),we've got a SCO server with visionFS installed and i need to access to the file shared on the SCO server from a NT4 Server which is on a different subnet but it doesn't work. I obtain a message like this "impossible to join the server". ... (1 Reply)
Discussion started by: zounours-69
1 Replies

5. AIX

Add printer connected to a axis printserver

Hi guys, I have a AIX 4.3 system, and I need to configure a printer, but that printer it's connected to a axis print server. I have lot of years working with unix, but never added a printer in a AIX system. I need to add using "remote print queue", and add the hostname and ip to the /etc/hosts?... (2 Replies)
Discussion started by: uadm26
2 Replies

6. SCO

Visionfs configuration problem!

I have re-installed sco unix 7.1.1 box, and Visionfs is installed and configured successful but when i run the "sh /usr/vision/bin/visionfs print --install PRINTERNAME PC-NAME PRINTERNAME" command the system gives me the usage instruction as if i am giving the wrong syntax! any help please! (1 Reply)
Discussion started by: titino
1 Replies

7. Shell Programming and Scripting

Help: how to convert perl script to awk in windows2003 server environment

For the following perl script, can anyone help to convert it to awk statement in windows2003 server environment ? Code: foreach $k (sort {$a <=> $b} keys %psnum) (1 Reply)
Discussion started by: tojzz
1 Replies

8. UNIX for Advanced & Expert Users

Printserver in linux

Hi, Could anyone please find any good tutorials for me on how to implement printserver in linux, how to make its automation and how to configure it with command line?? I've searched google and the net to find this things out but nothing comes as a useful result ..... Any help is highly... (2 Replies)
Discussion started by: andirrashi
2 Replies

9. AIX

SMC multi port Printserver setup on AIX 6.1

Hi Guys, I have SMC 3 port print server would liek to create 3 queues for each port , please advice what port name or number should be used while creating the quues , I have hpjetdirect and I have tried raw1, raw2 and raw3 on it and it works but it doesnt work for SMC , please advice. ... (1 Reply)
Discussion started by: Valeed
1 Replies

10. SCO

sco visionfs vs smb

i need to copy the entire contents of my sco server 5.0.5 it says its running vision fs 2.01.905 if i access it from windows i would like to be able to access it like a normal file share instead of only thru an ftp service i cannot find vison software on the server /usr/vision does not exist ... (1 Reply)
Discussion started by: crosbymook
1 Replies
FOOMATIC-RIP(1) 					      General Commands Manual						   FOOMATIC-RIP(1)

NAME
foomatic-rip - Universal print filter/RIP wrapper SYNOPSIS
General Options: foomatic-rip [-v] [-q] <spooler-specific options> Spooler-less printing/CPS (older versions) filter: foomatic-rip [-P <printer> | --ppd <ppdfile> ] [-J <jobtitle> ] [-o <option>=<value> [...]] [<files>] CUPS filter: foomatic-rip <jobid> <user> <jobtitle> <numcopies> <options> [<file>] LPRng filter: foomatic-rip --lprng [-J<jobtitle>][-Z<option>=<value>[,<option>=<value>[, ...]] <ppdfile> foomatic-rip [-J<jobtitle>][-Z<option>=<value>[,<option>=<value>[, ...]] (printcap :pdd=<ppdfile>) foomatic-rip --ppd <ppdfile>[-J<jobtitle>] [-Z<option>=<value>[,<option>=<value>[, ...]] LPD/GNUlpr filter: foomatic-rip [-w <number>] [-l <number>] [-x <number>] [-y <number>] [-i <number>] [-c] [-n <string>] [-h <string>] [-j|-J <jobti- tle>|<options>] <ppdfile> PPR RIP: foomatic-rip [<option>=<value> [...]] PPR interface: foomatic-rip <queue> <destaddress> <options> <jobbreak> <feedback> <codes> <jobname> <routing> <for> <filetype> [<file>] PDQ driver file generation: foomatic-rip [--ppd <ppdfile>] [-o <option>=<value> [...]] --genpdq|--appendpdq|--genrawpdq|--appendrawpdq PDQ filter: foomatic-rip --pdq --ppd <ppdfile>] [-o <option>=<value> [...]] <file> CPS (newer versions) filter: foomatic-rip --cps -P <printer> [-J <jobtitle>] [-o <option>=<value> [...]] [<files>] DESCRIPTION
foomatic-rip is a universal print filter which works with every known free software printer spooler. It has the following features: It translates PostScript and PDF (and also other file formats) from standard input to the printer's native language (usually put to stan- dard output). The translation is done with an external renderer, usually Ghostscript (gs(1)). If no translation is needed (PostScript printer) the ren- derer's command line reduces to cat(1). The way how this translation is done is described in a PPD file. Printer capabilities, how to handle user options, and how to build the renderer command line is always described by PPD files, these PPD files usually come from Foomatic or can be the ones supplied by the manufacturers of PostScript printers. The PPD files are the same for all spoolers. foomatic-rip works with every known spooler (CUPS, LPRng, LPD, GNUlpr, PPR, PDQ, CPS, and without spooler). It auto-detects the spooler from which it was called by the command line options and environment variables which were supplied by the spooler. Non-PostScript/PDF files are translated to PostScript before they are passed to the renderer. This is usually done by a2ps(1), enscript(1), or mpage(1). foomatic-rip auto-detects which program is installed, but manual configuration is also possible. foomatic-rip does not only apply option settings supplied by the user through the command line of the printing command, but also searches the entire job for embedded option settings (only PostScript jobs). Here not only settings affectimg the whole job are taken into account, but also settings in the page headers, which are only valid for the page where they were found, so applications which produce PostScript code with page-specific printer option settings are fully supported. SPOOLER-LESS PRINTING Options -v verbose mode for debugging. WARNING: This will create a file in /tmp that contains the debugging information. This opens a security loophole and should not be used in production. -q quiet mode - minimal information output -P <printer> <printer> is the configured printer which should be used for this job. --ppd <ppdfile> The PPD file <ppdfile> should be applied for processing this job. -J <jobtitle> The <jobtitle> will be printed in the head line of every page of a plain text job. -o <option>=<value> Option settings for this job, do foomatic-rip -P <printer> -o docs <file> (<file> can be an arbitrary existing file, as .bashrc, will not be printed) to print a list of available options for the speci- fied <printer>. <files> The file(s) to be printed. foomatic-rip will print from standard input unless at least one file to be printed is specified on the command line. If your printer PPD file is stored as /etc/direct/<printer>.ppd or ~/.foomatic/direct/<printer>.ppd you can use it by simply specifying "-P <printer>". Put a line *FoomaticRIPPostPipe: "| <command>" into the PPD file, right after *PPD-Adobe: "4.3", where <command> is a command into which you wnat to re-direct the output data. Due to the restrictions of PPD files <, >, and " are not allowed in the <command>, replace them as follows: Character Replacement --------------------- < &lt; > &gt; " &quot; ' &apos; & &amp; This way you can print directly to your printer, use *FoomaticRIPPostPipe: "| cat &gt; /dev/lp0" or *FoomaticRIPPostPipe: "| cat &gt; /dev/usb/lp0" for local parallel or USB printers. To make normal users able to print this way add them to the group lp and make sure that the appropriate printer device file /dev/... is group-writable for the lp group. for a TCP/Socket/JetDirect printer with the host name printer listening on port 9100 you need this: *FoomaticRIPPostPipe: "| /usr/bin/nc -w 1 printer 9100" Note the "-w 1" in the "nc" command line, it makes "nc" exiting immediately after the data is transferred to the printer. *FoomaticRIPPostPipe: "| rlpr -Plp@printserver" directs your jobs to the LPD printer queue lp on the machine named printserver. See also http://www.openprinting.org/direct-doc.html PRINTING WITH SPOOLER
See the documentation on the OpenPrinting Web site: http://www.openprinting.org/ CONFIGURATION FILE
The file /etc/foomatic/filter.conf is read whenever foomatic-rip is executed. It allows to configure the behavior of foomatic-rip as follows (lines beginning with # are comments and therefore get ignored): textfilter: <command> Selects the filter for input files which are not PostScript or PDF. <command> is one of a2ps, enscript, or mpage. foomatic-rip auitomatically selects the needed command line options. debug: 0|1 Turns on (1) or off (0) the debug mode. This is equivalent to supplying the --debug command line option. Default setting is 0. ps_accounting: 0|1 Turns on (1) or off (0) inserting PostScript code for page accounting into PostScript jobs. The inserted PostScript code makes Ghostscript generating accounting output on stderr and CUPS can this way log each page which got printed. The code will only be inserted if CUPS is the spooler. Default setting is 1. echo: [<path>/]<executable> Sets the path to an echo(1) executable which supports -n. gspath: [<path>/]<executable> Sets the path to the Ghostscript (gs(1)) executable. To be used if Ghostscript is at a non-standard location or if an alternative Ghostscript should be used. execpath: <path>[:<path>]... Sets the $PATH variable to be used by foomatic-rip. cupsfilterpath: <path>[:<path>]... Sets the directories (colon-separated) in which foomatic-rip searches for CUPS filters. preferred_shell: [<path>/]<executable> Sets the preferred shell to use when executing FoomaticRIPCommandLine and friends. Several PPD files use shell constructs that require a more modern shell like bash, zsh, or ksh. FILES
/etc/cups/ppd/<printer>.ppd /etc/lpd/<printer>.ppd /etc/ppr/<printer>.ppd /etc/pdq/<printer>.ppd /etc/direct/<printer>.ppd The PPD files of the currently defined printers /etc/foomatic/filter.conf Configuration file for foomatic-rip EXIT STATUS
foomatic-rip returns 0 unless something unexpected happens. AUTHOR
Till Kamppeter <till.kamppeter@gmail.com> with parts of Manfred Wassmanns's <manolo@NCC-1701.B.Shuttle.de> man pages for the Foomatic 2.0.x filters. BUGS
None so far. Please send bug reports to the Foomatic mailing list: http://lists.freestandards.org/mailman/listinfo/printing-foomatic Foomatic Project 2002-11-26 FOOMATIC-RIP(1)
All times are GMT -4. The time now is 04:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy