'lp' question
in [Solaris]
|
Prev: ftp c++ client on solaris
Next: Scriptable method to determine if user is local (/etc/passwd) user or LDAP user on Sol10 server
From: Wil on 12 May 2010 11:21 On May 10, 12:01 pm, Michael Vilain <vil...(a)NOspamcop.net> wrote: > In article <WqOdnToVbJMivHXWnZ2dnUVZ_qidn...(a)giganews.com>, > "Richard B. Gilbert" <rgilber...(a)comcast.net> wrote: > > > > > Wil wrote: > > > On May 10, 7:46 am, mlstarkey <ukelu...(a)yahoo.com> wrote: > > >> On May 8, 12:55 pm, groen...(a)cse.psu.edu (John D Groenveld) wrote: > > > >>> In article > > >>> <a5e18f31-9cfb-44c2-8cbf-218977da7...(a)24g2000yqy.googlegroups.com>, > > >>> Wil <WilArt...(a)comcast.net> wrote: > > >>>> Does anyone have any idea what would cause the change? Is it just the > > >>>> upgrade? If so, is there a method to revert? > > >>> I'm not sure which patch changed the behavior but you're probably > > >>> going to have to open a service request with Solaris support to > > >>> determine the how and why. > > >> you could do that if you have a contract and they will explain how > > >> much the print system changed after U5 and that the latest print patch > > >> should be applied, but they cannot fix the custom lp scripts. > > > >>> If you used LiveUpgrade to upgrade to the recent S10 update, > > >>> you can revert easily and then use Martin Paul's PCA to only > > >>> apply those patches which don't touch the Solaris print system. > > >>> You might also be able to replace the packages which make up > > >>> the print system with those from the older media. > > >> I strongly recommend against that. It creates a mess and doesn't > > >> work. > > > >> Printing changed big time b/t Solaris 10 U3 and Solaris 10 U8. Start > > >> here: > > > >>http://docs.sun.com/app/docs/doc/819-7355/printconcept-42?a=view > > > >> since the question/issue seems to revolve around file ownerships and > > >> privileges > > > >>> Happy hacking, > > >> OTOH, if that is the goal, then have at it and enjoy : ) > > > >>> John > > >>> groenv...(a)acm.org > > > > Many thanks for the feedback. It surely sounds like the best course of > > > action is actually two-fold. 1) Open a call with Sun/Oracle about the > > > changes and 2) review and modify the local interface files and scripts > > > to accommodate the new LP system. > > > > Wil > > > This sounds as if somebody just installed a software upgrade without > > understanding what was involved. ANY software upgrade changes > > something. Sometimes a lot of somethings get changed. You're supposed > > to understand the effects of the upgrade *before* installing it in > > production! Ideally you should have a means to easily restore the > > status quo ante in case the change breaks something. > > > On rare occasions the upgrade is transparent but you can't count on it! > > Sometimes, the upgrade is worse than what you had to begin with!! > > > Many IT departments will build a test system on their second best > > hardware just to make sure that: they can install it properly, and that > > the new software works at least as well as what they have been running! > > > Doing it right costs more money up front but, in the long run, it will > > save you a good deal of money and embarrassment! > > Unfortunately, many IT departments are viewed as an overhead cost and a > clueless manager will just give the order "do the upgrade during the > Easter 3-weekend". That leaves IT to scramble to figure out what's > affected and not affected, plan the impact on various systems and > minimize that, create a fallback plan if things go pear-shaped (this > sometimes gets dropped by Windows admins drafted into running a Solaris > system after the real admin left), and having various groups test their > applications on the new OS prior to "live" primetime on Monday. > > Yeah, "just do the upgrade this weekend, OK?" is often all IT > departments get for direction. Now that manager has to deal with the > consequences. > > -- > DeeDee, don't press that button! DeeDee! NO! Dee... > [I filter all Goggle Groups posts, so any reply may be automatically ignored] Hmmmm.... appears that some feel that appropriate research was not conducted prior to upgrades... this upgrade was put on a development system, for testing!!!!! prior to any production deployments. Yes, the 'lp' print services changed. Yes, I could revert to Sol10u3 (not really a good idea). I could replace the print server packages with the old ones (not good either). Best bet is to update the printer interface files dealing with the new functionality, test on development and QA, and then be ready when the production systems are upgraded,. |