Sponsored Content
Operating Systems Linux Sabayon - KDE4.2 Problems accessing system management - all greyed out Post 302315102 by mark54g on Monday 11th of May 2009 01:15:46 PM
Old 05-11-2009
This is not a system that was designed for only single users, and they don't know how you live. The system assumes that you have an idea of how to use it, as you are intuitive, and the system is not.

Also, the use of root vs a normal (underprivileged user) is to prevent the normal user from destroying the machine. Also, it is a protective measure that ensures that as a normal user, under normal circumstances, should you get compromised, minimal damage to the system can be done. If you, as a normal user, gets infected by a rootkit or uses a script that is malicious, you should do minimal damage (assuming that the attacks are not using a code exploit that is unpatched, etc). Under previous versions of Windows, for example, the code would be run as administrator, as that is what Windows assumed, and the machine/OS could be compromised as a result.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Accessing the internet through another system

I have a group of Solaris machines being logged in locally but accessing the internet through a dhcp connection. I am short 2 network drops and ports and need to get these machines accesssing the internet. I cannot add a hub or switch because of administrative reasons. Is there a way to connect... (3 Replies)
Discussion started by: meyersp
3 Replies

2. SuSE

SUSE 9 - problems accessing CD ROM drive

I've got SUSE 9 installed on a removable hard drive and the system is up and running fine. I'm trying to copy stuff off a CD onto one of my Linux partitions but I am getting an errors : * Could not read /media/cdrom/file1.tar.tar I can browse to the file location on the CD by using the... (11 Replies)
Discussion started by: GandalfWhite
11 Replies

3. UNIX for Dummies Questions & Answers

Limit number of user accessing to SCO UNIX System

Hi, In my company, we are using SCO UNIX system and Informix database. Recently, there have been a lot of users accessing to server and sometimes it has made server run very slow. So, I intend to limit number of users of 30 only. Although I have tried to search on the Internet for several days,... (1 Reply)
Discussion started by: trinhnguyen
1 Replies

4. Red Hat

Central Configurations Management System for Linux

hi all, i am currently implementating project scope for a future enterprise solution provider in the storage area. I was hoping if anyone could help me to answer questions regarding the Central Configurations Management System in the RedHat or other linux distro. In the Unix env. , most of... (2 Replies)
Discussion started by: furrahs@yahoo.c
2 Replies

5. Infrastructure Monitoring

All Things System Management (Blog)

Topics in the System Management blog include the Sun x86 SNMP Hardware Monitoring Agent, Microsoft Integration Updates posted, Sun Integration 1.0 for Microsoft SCOM 2007, Sun Installation Assistant adds 2 more platforms, etc. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies

6. AIX

Accessing files on AIX system from Linux system

I have a following requirement in production system 1 : LINUX User: abcd system 2: AIX (it is hosting a production DB) Requirement user abcd from system 1 should have read access on archive log files created by DB on system 2. The log files are created with permissions 540 by user ora ,... (2 Replies)
Discussion started by: amitnm1106
2 Replies

7. HP-UX

Problems creating and accessing with user

Hi, I have created the user 'mastersa' in several servers. I need to change the user ID to '0'. However, after doing this, I am not able to login (Access denied). Even after I change the password, I still get this error. Why is this? Also, when I attempt to delete the user account, I get... (5 Replies)
Discussion started by: anaigini45
5 Replies
TUNELP(8)						       System Administration							 TUNELP(8)

NAME
tunelp - set various parameters for the lp device SYNOPSIS
tunelp device [-i IRQ] [-t TIME] [-c CHARS] [-w WAIT] [-a {on|off}] [-o {on|off}] [-C {on|off}] [-r] [-s] [-q {on|off}] [-T {on|off}] DESCRIPTION
tunelp sets several parameters for the /dev/lp? devices, for better performance (or for any performance at all, if your printer won't work without it...) Without parameters, it tells whether the device is using interrupts, and if so, which one. With parameters, it sets the device characteristics accordingly. The parameters are as follows: -i IRQ specifies the IRQ to use for the parallel port in question. If this is set to something non-zero, -t and -c have no effect. If your port does not use interrupts, this option will make printing stop. The command tunelp -i 0 restores non-interrupt driven (polling) action, and your printer should work again. If your parallel port does support interrupts, interrupt-driven printing should be somewhat faster and efficient, and will probably be desirable. NOTE: This option will have no effect with kernel 2.1.131 or later since the irq is handled by the parport driver. You can change the parport irq for example via /proc/parport/*/irq. Read /usr/src/linux/Documentation/parport.txt for more details on parport. -t TIME is the amount of time in jiffies that the driver waits if the printer doesn't take a character for the number of tries dictated by the -c parameter. 10 is the default value. If you want fastest possible printing, and don't care about system load, you may set this to 0. If you don't care how fast your printer goes, or are printing text on a slow printer with a buffer, then 500 (5 seconds) should be fine, and will give you very low system load. This value generally should be lower for printing graphics than text, by a factor of approximately 10, for best performance. -c CHARS is the number of times to try to output a character to the printer before sleeping for -t TIME. It is the number of times around a loop that tries to send a character to the printer. 120 appears to be a good value for most printers in polling mode. 1000 is the default, because there are some printers that become jerky otherwise, but you must set this to `1' to handle the maximal CPU effi- ciency if you are using interrupts. If you have a very fast printer, a value of 10 might make more sense even if in polling mode. If you have a really old printer, you can increase this further. Setting -t TIME to 0 is equivalent to setting -c CHARS to infinity. -w WAIT is the number of usec we wait while playing with the strobe signal. While most printers appear to be able to deal with an extremely short strobe, some printers demand a longer one. Increasing this from the default 1 may make it possible to print with those print- ers. This may also make it possible to use longer cables. It's also possible to decrease this value to 0 if your printer is fast enough or your machine is slow enough. -a {on|off} This is whether to abort on printer error - the default is not to. If you are sitting at your computer, you probably want to be able to see an error and fix it, and have the printer go on printing. On the other hand, if you aren't, you might rather that your printer spooler find out that the printer isn't ready, quit trying, and send you mail about it. The choice is yours. -o {on|off} This option is much like -a. It makes any open() of this device check to see that the device is on-line and not reporting any out of paper or other errors. This is the correct setting for most versions of lpd. -C {on|off} This option adds extra ("careful") error checking. When this option is on, the printer driver will ensure that the printer is on- line and not reporting any out of paper or other errors before sending data. This is particularly useful for printers that normally appear to accept data when turned off. NOTE: This option is obsolete because it's the default in 2.1.131 kernel or later. -s This option returns the current printer status, both as a decimal number from 0..255, and as a list of active flags. When this option is specified, -q off, turning off the display of the current IRQ, is implied. -T {on|off} This option is obsolete. It was added in Linux 2.1.131, and removed again in Linux 2.3.10. The below is for these old kernels only. This option tells the lp driver to trust or not the IRQ. This option makes sense only if you are using interrupts. If you tell the lp driver to trust the irq, then, when the lp driver will get an irq, it will send the next pending character to the printer uncon- ditionally, even if the printer still claims to be BUSY. This is the only way to sleep on interrupt (and so the handle the irq printing efficiently) at least on Epson Stylus Color Printers. The lp driver automagically detects if you could get improved per- formance by setting this flag, and in such case it will warn you with a kernel message. NOTE: Trusting the irq is reported to corrupt the printing on some hardware, you must try to know if your printer will work or not... -r This option resets the port. It requires a Linux kernel version of 1.1.80 or later. -q {on|off} This option sets printing the display of the current IRQ setting. NOTES
-o, -C, and -s all require a Linux kernel version of 1.1.76 or later. -C requires a Linux version prior to 2.1.131. -T requires a Linux version of 2.1.131 or later. BUGS
By some unfortunate coincidence the ioctl LPSTRICT of 2.0.36 has the same number as the ioctl LPTRUSTIRQ introduced in 2.1.131. So, use of the -T option on a 2.0.36 kernel with an tunelp compiled under 2.1.131 or later may have unexpected effects. FILES
/dev/lp? /proc/parport/*/* AVAILABILITY
The tunelp command is part of the util-linux package and is available from ftp://ftp.kernel.org/pub/linux/utils/util-linux/. util-linux May 1999 TUNELP(8)
All times are GMT -4. The time now is 02:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy