[opensuse] 10.2: YOU resets /root/ permissions?
Greetings. How do I tell YOU to not reset my custom permissions for /root/ ? Best regards :o) Johnny :o) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-03-23 at 16:44 +0100, Johnny Ernst Nielsen wrote:
How do I tell YOU to not reset my custom permissions for /root/ ?
Could you elaborate, please? What are those permissions you are refering to? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGBACutTMYHG2NR9URAqyGAJ94fZx4e96Kb+B7YXyGG+CITngTygCggzPL OYF+47C/62elvtYHwpg3Bhw= =EqCR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Fredag 23 marts 2007 17:30 kvad Carlos E. R.:
The Friday 2007-03-23 at 16:44 +0100, Johnny Ernst Nielsen wrote:
How do I tell YOU to not reset my custom permissions for /root/ ?
Could you elaborate, please? What are those permissions you are refering to?
The permissions for the directory /root I have set it to be viewable by all. Every time YOU runs it resets the permissions so that only root can view the directory. Best regards :o) Johnny :o) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Fri, Mar 23, 2007 at 05:43:27PM +0100, Johnny Ernst Nielsen wrote:
Fredag 23 marts 2007 17:30 kvad Carlos E. R.:
The Friday 2007-03-23 at 16:44 +0100, Johnny Ernst Nielsen wrote:
How do I tell YOU to not reset my custom permissions for /root/ ?
Could you elaborate, please? What are those permissions you are refering to?
The permissions for the directory /root I have set it to be viewable by all. Every time YOU runs it resets the permissions so that only root can view the directory.
Check out the entry for /root in /etc/permissions. (It's not YOU that resets the permissions, but SuSEconfig). I think you can overwrite this entry with a custom entry in the /etc/permissions.local file. Cheers, Michael -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Fredag 23 marts 2007 17:49 kvad Michael Schroeder:
The Friday 2007-03-23 at 16:44 +0100, Johnny Ernst Nielsen wrote:
How do I tell YOU to not reset my custom permissions for /root/ ?
Check out the entry for /root in /etc/permissions. (It's not YOU that resets the permissions, but SuSEconfig). I think you can overwrite this entry with a custom entry in the /etc/permissions.local file.
It works. Thank you Michael :o) (And you too, Carlos :o)) Best regards :o) Johnny :o) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 23 March 2007, Michael Schroeder wrote:
On Fri, Mar 23, 2007 at 05:43:27PM +0100, Johnny Ernst Nielsen wrote:
Fredag 23 marts 2007 17:30 kvad Carlos E. R.:
The Friday 2007-03-23 at 16:44 +0100, Johnny Ernst Nielsen wrote:
How do I tell YOU to not reset my custom permissions for /root/ ?
Could you elaborate, please? What are those permissions you are refering to?
The permissions for the directory /root I have set it to be viewable by all. Every time YOU runs it resets the permissions so that only root can view the directory.
Check out the entry for /root in /etc/permissions. (It's not YOU that resets the permissions, but SuSEconfig). I think you can overwrite this entry with a custom entry in the /etc/permissions.local file.
Cheers, Michael
I'm amazed at Michael's ability to hand out this information (apparently with a straight face) to a user who didn't know how to do this (suggestive of someone fairly new to linux), without even once pointing out what a dumb idea this is. -- _____________________________________ John Andersen -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
John Andersen wrote:
On Friday 23 March 2007, Michael Schroeder wrote:
Fredag 23 marts 2007 17:30 kvad Carlos E. R.:
The Friday 2007-03-23 at 16:44 +0100, Johnny Ernst Nielsen wrote:
How do I tell YOU to not reset my custom permissions for /root/ ? Could you elaborate, please? What are those permissions you are refering to? The permissions for the directory /root I have set it to be viewable by all. Every time YOU runs it resets the permissions so that only root can view the directory. Check out the entry for /root in /etc/permissions. (It's not YOU
On Fri, Mar 23, 2007 at 05:43:27PM +0100, Johnny Ernst Nielsen wrote: that resets the permissions, but SuSEconfig). I think you can overwrite this entry with a custom entry in the /etc/permissions.local file.
Cheers, Michael
I'm amazed at Michael's ability to hand out this information (apparently with a straight face) to a user who didn't know how to do this (suggestive of someone fairly new to linux), without even once pointing out what a dumb idea this is.
please, don't be so harsh, given you don't add either any info :-( May I say (in my poor english) that: * the /root permissions are setup by Yast for very good reason (security... too many to be discussed shortly) * it's possible to make the modification said in the permissions file * this must not be done without extreme caution. May I also say that the OP didn't post the very reason he have to try to do so. For whatever reason he have decided to modify root permissions. Can he give us this very reason (if it's possible to discuss it in a public list), there are _certainly_ more adequate solutions, without the security drawbacks. jdd -- http://www.dodin.net Lucien Dodin, inventeur http://lucien.dodin.net/index.shtml -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Fredag 23 marts 2007 19:56 kvad jdd:
John Andersen wrote:
On Friday 23 March 2007, Michael Schroeder wrote:
On Fri, Mar 23, 2007 at 05:43:27PM +0100, Johnny Ernst Nielsen wrote:
Fredag 23 marts 2007 17:30 kvad Carlos E. R.:
The Friday 2007-03-23 at 16:44 +0100, Johnny Ernst Nielsen wrote:
How do I tell YOU to not reset my custom permissions for /root/ ?
Could you elaborate, please? What are those permissions you are refering to?
The permissions for the directory /root I have set it to be viewable by all. Every time YOU runs it resets the permissions so that only root can view the directory.
Check out the entry for /root in /etc/permissions. (It's not YOU that resets the permissions, but SuSEconfig). I think you can overwrite this entry with a custom entry in the /etc/permissions.local file.
Cheers, Michael
I'm amazed at Michael's ability to hand out this information (apparently with a straight face) to a user who didn't know how to do this (suggestive of someone fairly new to linux), without even once pointing out what a dumb idea this is.
please, don't be so harsh, given you don't add either any info :-(
May I say (in my poor english) that:
* the /root permissions are setup by Yast for very good reason (security... too many to be discussed shortly) * it's possible to make the modification said in the permissions file * this must not be done without extreme caution.
May I also say that the OP didn't post the very reason he have to try to do so. For whatever reason he have decided to modify root permissions. Can he give us this very reason (if it's possible to discuss it in a public list), there are _certainly_ more adequate solutions, without the security drawbacks.
It can be discussed, if people are interested. This is a desktop computer. I have my ordinary user account for my daily work. My printer's ink level program is unable to display ink level as well as print when either one of the four cartridges are empty. The cartridges are opaque and the printer itself only lights up one single light to signal that one of the cartridges are empty. So I have written a small service script to check the ink level every 60 seconds, and log that to a file in /root/. /root is where I keep all my system setting notes and system scripts, and I considder the ink level log a system wide "thing". I wish for alle users to be able to see the ink level log. Thus the changed permissions of /root. There is nothing "secret" in /root that I am aware of. I also wish to keep the number of directories to back up to a minimum -- /root and /home. Thus I have opted _not_ to put the ink level log in a directory outside /root or /home. The discussion is hereby open. Best regards :o) Johnny :o) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-03-23 at 21:36 +0100, Johnny Ernst Nielsen wrote:
So I have written a small service script to check the ink level every 60 seconds, and log that to a file in /root/. /root is where I keep all my system setting notes and system scripts, and I considder the ink level log a system wide "thing". I wish for alle users to be able to see the ink level log. Thus the changed permissions of /root. There is nothing "secret" in /root that I am aware of. I also wish to keep the number of directories to back up to a minimum -- /root and /home. Thus I have opted _not_ to put the ink level log in a directory outside /root or /home.
I think it would be better to log things to the log directory, which exist for that very purpose ;-) Ie, log to somewhere under /var/log, and give the file the appropiate permission to be read by all. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFGBEH7tTMYHG2NR9URAgY0AKCRVl6ynAZyNaayQ+l3RB4zSkNO0gCeNuRS K2SZSKgIUbeEEh45sykbogU= =NaMW -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
So I have written a small service script to check the ink level every 60 seconds,
Point 1: Is there a better way to get this information (I'm just asking)?
and log that to a file in /root/. /root is where I keep all my system setting notes and system scripts, and I considder the ink level log a system wide "thing".
Point 2. The ink level log would be a "a system wide "thing"" (for you), but /root is not. Can you log to a more appropriate place - /var/log/linklog, for example (process logs most often go in /var/log)? If you don't like /var/log for some reason, there are other places - /pub, /tmp, /usr/local - even make a whole new folder /inklog and put it there.
I wish for alle users to be able to see the ink level log.
Understood. But do they need to see everything else in /root? At this time you probably think you know everyone who uses the system, but what if an unauthorized, or for that matter even an unexpected (childeren, guests) person ever gets on? Do you want them to see your privet ssh keys and other encryption information? Your shell history?
Thus the changed permissions of /root. There is nothing "secret" in /root that I am aware of.
Is this system ever on the internet? Maybe you don't care if the system in question is broken into, but is it connected via network to other machines that you do care about? Maybe other workstations that have sensitive or personal information?
I also wish to keep the number of directories to back up to a minimum -- /root and /home.
I understand. But if that's your reason, why would you be backing up a log file that's being overwritten every 60 seconds anyway? -JW -- ---------------------- jw@mailsw.com - System Administrator - Cedar Creek Software www.cedarcreeksoftware.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Fredag 23 marts 2007 22:13 kvad Jonathan Wilson:
So I have written a small service script to check the ink level every 60 seconds,
Point 1: Is there a better way to get this information (I'm just asking)?
I have tried to find out if it is possible to have a program, like my ink level check script, run after each print job. After all, ink level only drops when something is actually printed. I have not found any such solution though :o(
and log that to a file in /root/. /root is where I keep all my system setting notes and system scripts, and I considder the ink level log a system wide "thing".
Point 2. The ink level log would be a "a system wide "thing"" (for you), but /root is not. Can you log to a more appropriate place - /var/log/linklog, for example (process logs most often go in /var/log)?
Sure, but I do not want to as long as I do not deem the current solution insecure for my usage situation. :o)
I wish for alle users to be able to see the ink level log.
Understood. But do they need to see everything else in /root?
No, but they are welcome to if they want to. There is nothing secret there. The only thing people might deem "secret" is an ssh key in /root/.ssh -- which is not readable by anyone but root.
Thus the changed permissions of /root. There is nothing "secret" in /root that I am aware of.
Is this system ever on the internet?> Maybe you don't care if the system in question is broken into, but is it connected via network to other machines that you do care about?
No. It is not in a network (apart from the "big" internet). In order to keep crackers from abusing my computer to bother other internet users, I have tried to make sure that no programs I use listen for connections from the internet. I have no internet servers or internet services running. My firewall (SuSEFirewall2) is set up to drop all connection attempts from outside, as well as all packages that are not part of sessions initiated my me. I have even disabled ping reply, which was enabled by default. Port scanning my computer from outside, I am not able to see it at all. I do care about security.
I also wish to keep the number of directories to back up to a minimum -- /root and /home.
I understand. But if that's your reason, why would you be backing up a log file that's being overwritten every 60 seconds anyway?
Because I need to be able to see the latest ink level at all times. When I install a new version of OpenSUSE I need to transfer the ink level log from the old version to the new version. I need to be able to see which cartridge has run dry on the last print job on the old version. And I want to be able to continue the ink level history noted in the log. Best regards :o) Johnny :o) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Johnny Ernst Nielsen wrote:
It can be discussed, if people are interested.
sure, they are :-). Don't forget many people read the list (and never write) to be ahead of possible problems, having solutions at hand. We can have one day the very same problem you have and be very glad to remember it has been already discussed :-))
So I have written a small service script to check the ink level
if you happen to have time (and want) to do so, giving on the wiki (even here) a copy of your script could certainly be of interest for many users.
changed permissions of /root. There is nothing "secret" in /root that I am aware of.
are you aware of all that is stored in "." files? like ssh keys, as other said? don't you have there a /root/bin folder with some root executables?
I also wish to keep the number of directories to back up to a minimum -- /root and /home.
better create a folder in /home where most users can read (can be a link to /var/log). However I'm not a security guru :-() jdd -- http://www.dodin.net Lucien Dodin, inventeur http://lucien.dodin.net/index.shtml -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Lørdag 24 marts 2007 06:58 kvad jdd:
Johnny Ernst Nielsen wrote:
So I have written a small service script to check the ink level
if you happen to have time (and want) to do so, giving on the wiki (even here) a copy of your script could certainly be of interest for many users.
I will try to remember to do that. I also need to add to the hardware database.
changed permissions of /root. There is nothing "secret" in /root that I am aware of.
are you aware of all that is stored in "." files? like ssh keys, as other said?
It is locked, as everything else I do not want everyone to see.
don't you have there a /root/bin folder with some root executables?
It is empty, so everyone can look in it all they want. :o)
I also wish to keep the number of directories to back up to a minimum -- /root and /home.
better create a folder in /home where most users can read (can be a link to /var/log).
I prefer to keep my custom system stuff collected under /root. But thank you for the suggestion. Best regards :o) Johnny :o) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Johnny Ernst Nielsen wrote:
My printer's ink level program is unable to display ink level as well as print when either one of the four cartridges are empty. The cartridges are opaque and the printer itself only lights up one single light to signal that one of the cartridges are empty. Would this be some sort of Epson all-in-one device, by any chance ?
Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com http://www.iba-worldwide.com The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.
Mandag 26 marts 2007 15:05 kvad Philippe Andersson:
Johnny Ernst Nielsen wrote:
My printer's ink level program is unable to display ink level as well as print when either one of the four cartridges are empty. The cartridges are opaque and the printer itself only lights up one single light to signal that one of the cartridges are empty.
Would this be some sort of Epson all-in-one device, by any chance ?
No. Printer only. Epson Stylus C66. Best regards :o) Johnny :o) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Johnny, Johnny Ernst Nielsen wrote:
Mandag 26 marts 2007 15:05 kvad Philippe Andersson:
Johnny Ernst Nielsen wrote:
My printer's ink level program is unable to display ink level as well as print when either one of the four cartridges are empty. The cartridges are opaque and the printer itself only lights up one single light to signal that one of the cartridges are empty. Would this be some sort of Epson all-in-one device, by any chance ?
No. Printer only. Epson Stylus C66. Well, maybe the printer part of the all-in-one uses the same driver. My kid sister has one of those, and faces the same troubles managing the ink. I'd be interested in your scripts, if you agree to share them.
TIA Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com http://www.iba-worldwide.com The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.
Mandag 26 marts 2007 15:21 kvad Philippe Andersson:
Hi Johnny,
Johnny Ernst Nielsen wrote:
Mandag 26 marts 2007 15:05 kvad Philippe Andersson:
Johnny Ernst Nielsen wrote:
My printer's ink level program is unable to display ink level as well as print when either one of the four cartridges are empty. The cartridges are opaque and the printer itself only lights up one single light to signal that one of the cartridges are empty.
Would this be some sort of Epson all-in-one device, by any chance ?
No. Printer only. Epson Stylus C66.
Well, maybe the printer part of the all-in-one uses the same driver. My kid sister has one of those, and faces the same troubles managing the ink. I'd be interested in your scripts, if you agree to share them.
Sure. It's basically just a loop that calls the printer driver's command line ink level function, appends the answer to a file, and goes to sleep for 60 seconds. Please note that this script is hardcoded for my printer and the specific proprietary printer driver I use. Please also note that the posted code is translated from danish, so typing errors may have been introduced. Here is the Python code: ---o--- #!/usr/bin/python # -*- coding: utf8 -*- #IMPORT PRACTICAL MODULES FOR DATA HANDLING. #Handling of sub processes/calls of programs to have their output directly readable in the script. import subprocess #Handling of files. import os #For suspending the script for a given time. import time #Date and time. import datetime #String manipulation: import string #PRACTICAL VARIABLES. #The place and name for the ink level log. inklevellogfile="/root/Inklevellog.txt" #The place and name of the ink level log error file. inklevellogerrorfile="/root/Inklevellogerror.txt" #HERE STARTS THE SCRIPT. #Make a list to keep the previous result. previousresult=[] #Get the latest log entry. if os.path.isfile(inklevellogfile): file=open(inklevellogfile, 'rU') #Read all the file's lines into a result list. previousresult=file.readlines() #Close the file. file.close() #If the file was not brand new. if len(previousresult) > 1: #Remove all lines, except the last four, which contains the latest ink level. I.e. keep from the 5Th last line to 2Nd last line. previousresult=previousresult[len(previousresult)-5:-1] #Make the list into a string. previousresult=repr(previousresult) #Remove alle encoded line breaks. previousresult=string.replace(previousresult,"\\n","") #Remove all double spacing. while " " in previousresult: previousresult=string.replace(previousresult," "," ") #There was no ink level log. else: #Make an empty log file. file=open(inklevellogfile, "w") file.close() #Assume all cartridges are 100% filled. previousresult="['Black : 100%', 'Cyan : 100%', 'Magenta : 100%', 'Yellow : 100%']" #Never ending loop... while True: #List USB-devices. process=subprocess.Popen("/usr/sbin/lsusb", shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE) result=process.stdout.read() #See if the printer is among the USB devices. if "Seiko Epson Corp. Stylus Printer" in result: #See if the printer is idle/not engaged in printing. process=subprocess.Popen("lpstat -p", shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE) result=process.stdout.read() #If the printer is idle. if " is idle." in result: #Get date and time. time=datetime.datetime.now() #Check ink level. process=subprocess.Popen("/usr/bin/tpconfig --ink", shell=True, stdout=subprocess.PIPE, stderr=subprocess.PIPE) result=process.stdout.readlines() errorresult=process.stderr.read() #Make the result into a string. result=repr(result) #Remove all encoded line breaks. result=string.replace(result,"\\n","") #Remove all double spaces. while " " in result: result=string.replace(result," "," ") #If an ink level is reported... if "Black :" in result: #...and the ink level is different from the previous ink level; we must add a log entry. if not result==previousresult: #Make the string into a list, so we can write the four lines of ink levels in the log. result=eval(result) #Append date, time and ink level to the log file. file=open(inklevellogfile, "aw") file.write(time.strftime("Day: %d, month: %m, year: %Y, time: %H. %M\n")) for line in result: file.write(line+'\n') #Dividing line. file.write("---o---\n") file.close() #Remember the new result for the next comparison. previousresult=repr(result) #If no ink level is reported, we must log an error. else: #Open the error log. file=open(inklevellogerrorfile, "aw") #Write date and time. file.write(time.strftime("Day: %d, month: %m, year: %Y, time: %H. %M\n")) #Write the error. file.write(errorresult) #Dividing line. file.write("---o---\n") file.close() #Wait 60 seconds before next ink level check. time.sleep(60) #[END OF SCRIPT] ---o--- Best regards :o) Johnny :o) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Johnny Ernst Nielsen wrote:
Mandag 26 marts 2007 15:21 kvad Philippe Andersson:
Hi Johnny,
Johnny Ernst Nielsen wrote:
Mandag 26 marts 2007 15:05 kvad Philippe Andersson:
Johnny Ernst Nielsen wrote:
My printer's ink level program is unable to display ink level as well as print when either one of the four cartridges are empty. The cartridges are opaque and the printer itself only lights up one single light to signal that one of the cartridges are empty. Would this be some sort of Epson all-in-one device, by any chance ? No. Printer only. Epson Stylus C66. Well, maybe the printer part of the all-in-one uses the same driver. My kid sister has one of those, and faces the same troubles managing the ink. I'd be interested in your scripts, if you agree to share them.
Sure. It's basically just a loop that calls the printer driver's command line ink level function, appends the answer to a file, and goes to sleep for 60 seconds.
Please note that this script is hardcoded for my printer and the specific proprietary printer driver I use.
Please also note that the posted code is translated from danish, so typing errors may have been introduced. Thanks a lot (and especially for translating it from danish -- I may not have been up to it ;-) ).
Cheers. Bye. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan@iba-group.com http://www.iba-worldwide.com The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.
Hello, On Mar 26 15:11 Johnny Ernst Nielsen wrote (shortened):
My printer's ink level program is unable to display ink level as well as print when either one of the four cartridges are empty. The cartridges are opaque and the printer itself only lights up one single light to signal that one of the cartridges are empty. ... Epson Stylus C66.
I do not understand what exactly you mean. Ususally it cannot work when one process (your ink level program) communicates with the printer to query its ink levels while another process (the CUPS backend) sends print-data at the same time. You need to implement mutual exclusion. By the way: Do you know about /usr/bin/escputil (see "man escputil")? Perhaps it works for your specific model. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Mandag 26 marts 2007 16:29 kvad Johannes Meixner:
On Mar 26 15:11 Johnny Ernst Nielsen wrote (shortened):
My printer's ink level program is unable to display ink level as well as print when either one of the four cartridges are empty. The cartridges are opaque and the printer itself only lights up one single light to signal that one of the cartridges are empty.
... Epson Stylus C66.
I do not understand what exactly you mean.
Sorry. I see I did not manage to explain clearly. If one of the four cartridges is empty, a red light is on on the printer, showing "out of ink" mode. The printer will not print anything untill the empty cartridge is replaced. Not even if it is one of the colour cartridges that is empty, and I try to print pure black with the black cartridge. So, I can see that one of the cartridges is empty, but the printer itself does not show which one. Since the cartridges are opaque, I can not look directly at the cartridges to find out. Currently I use the TurboPrint proprietary driver (for full resolution printing). It has an ink level check command. However, that command does not work when the printer is in "out of ink" mode.
Ususally it cannot work when one process (your ink level program) communicates with the printer to query its ink levels while another process (the CUPS backend) sends print-data at the same time. You need to implement mutual exclusion.
I know. And I have done my best to do so. My script asks the printer status from the printing system, to see that the printer is idle, before it attempts to check the ink level.
By the way: Do you know about /usr/bin/escputil (see "man escputil")?
I had no idea about it's existence.
Perhaps it works for your specific model.
It does! Thank you very much Johannes! :o) Now I just need to wait for a cartridge to run empty, to see if it can report the ink level with an empty cartridge. Thank you again. :o) Best regards :o) Johnny :o) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Fredag 23 marts 2007 19:46 kvad John Andersen:
On Friday 23 March 2007, Michael Schroeder wrote:
On Fri, Mar 23, 2007 at 05:43:27PM +0100, Johnny Ernst Nielsen wrote:
Fredag 23 marts 2007 17:30 kvad Carlos E. R.:
The Friday 2007-03-23 at 16:44 +0100, Johnny Ernst Nielsen wrote:
How do I tell YOU to not reset my custom permissions for /root/ ?
Could you elaborate, please? What are those permissions you are refering to?
The permissions for the directory /root I have set it to be viewable by all. Every time YOU runs it resets the permissions so that only root can view the directory.
Check out the entry for /root in /etc/permissions. (It's not YOU that resets the permissions, but SuSEconfig). I think you can overwrite this entry with a custom entry in the /etc/permissions.local file.
Cheers, Michael
I'm amazed at Michael's ability to hand out this information (apparently with a straight face) to a user who didn't know how to do this (suggestive of someone fairly new to linux), without even once pointing out what a dumb idea this is.
Dumber than critisising a working solution without suggesting a better solution nor explaining why the working solution is dumb? (This is where you have your chance to explain why Michael's solution is "dumb", AND present a better solution -- don't miss that chance) Johnny (The original poster) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (8)
-
Carlos E. R. -
jdd -
Johannes Meixner -
John Andersen -
Johnny Ernst Nielsen -
Jonathan Wilson -
Michael Schroeder -
Philippe Andersson