Depends, in this case it doesn't matter since we are just trying to
protect the white space. Normally single quotes are more predictable as
they are always literal.
The difference between them is pretty big when talking about scripting
though. Variables will expand within double quotes, will not inside of
single quotes.
i.e.
bash-3.00# echo "$USER"
root
bash-3.00# echo '$USER'
$USER
Why does this matter? Let's say you did...
Driver=`some utdesktop command to query a field in the SRDS`
then you did -r printer:myprinter='$Driver' uttsc would literally pass
the word $Driver to windows.
Let's say same scenario, but instead of passing your args right to uttsc
you pass them to another script which then called uttsc.
If you just did -r printer:myprinter="$Driver" which expanded out to -r
printer:myprinter="HP LaserJet", your second script would fail (if it
didn't protect the args, that is) with a uttsc usage error because uttsc
wasn't expecting "LaserJet" on it's own.
So you could -r printer:myprinter='"$Driver"' to solve that problem.
Of course you'd have to the Driver variable.
Protecting positional values and white space from script to script can
get messy, and if you drop the quotes, you're dead See Art's email. ;)
On 5/13/11 1:18 PM, Brad Lackey wrote:
Should it not be single quotes?
On May 13, 2011, at 12:22 PM, Craig Bender wrote:
That's not the correct usage for printer mapping.
It's -r printer:printername
where printername is a valid "Raw" print queue on your Sun Ray Server,
not the ip of a printer.
This will use a postscript driver and will pretty much only work with
post script printers
If you need to pass the actual driver name up, it's -r
printer:printername="Windows Printer Driver Name"
Where printer name is a valid Raw print queue on your Sun Ray Server
and "Windows Printer Driver Name" is *exactly* how it is shown on the
Windows server. Double quotes *are* needed to protect the white space.
On 5/13/11 11:06 AM, Paul Whitener wrote:
Greetings all,
I have a RHEL5 server setup and running srss 5.2. I have a printer on
our network setup on the Sun Ray server and can print from a standard
srss session just fine.
In the end, I am going to use it to connect to a Windows RDP session. I
am not able to get the Windows printing to work. The connector attaches
to the server just fine. I use the -r printer:myprinter <IP of windows
server> on the option line. On the Win 2008 server, I do not have any
printers installed. I have read everything I can on the wikis and from
the latest docs. My understanding is that if the printer is installed
locally on the SRSS box, and I use the -r printer: option, the uttswc
will present that as a printer to Windows. Now granted, I am sure I am
missing something in the reading of the docs, but I have not found a
good step by step on this one.
Any help would be greatly appreciated!
Thanks in advance!
/paul
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org <mailto:SunRay-Users@filibeto.org>
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org <mailto:SunRay-Users@filibeto.org>
http://www.filibeto.org/mailman/listinfo/sunray-users
Brad Lackey | Technical Enablement Manager
Mobile: +13038758616 <tel:+13038758616>
Oracle Global Desktop Virtualization
San Diego , CA
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
SunRay-Users@filibeto.org
http://www.filibeto.org/mailman/listinfo/sunray-users