Sponsored Content
Full Discussion: Windows XP issue...
Special Forums Windows & DOS: Issues & Discussions Windows XP issue... Post 302797639 by hanson44 on Tuesday 23rd of April 2013 01:34:47 AM
Old 04-23-2013
If the new user account doesn't work, I think you have two options:

1) Uninstall and reinstall the browsers.
2) Reinstall the operating system.
 

7 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unix in a Windows environment issue

What types of error messages would I recieve if the backbone of the network is setup for both Unix and Windows systems? (6 Replies)
Discussion started by: Aisha Sturkey
6 Replies

2. Windows & DOS: Issues & Discussions

Drive issue under Windows

I recently got myself a new 2 TB drive. However everytime I connect the drive it doesn't have a drive letter, so I have to open the diskmgmt.msc and manually reassign it (EVERY TIME I connect the Drive...) Also the Drive appears to have no Recycle Bin. It always prompts to instantly delete... (4 Replies)
Discussion started by: pasc
4 Replies

3. Shell Programming and Scripting

ksh - variable to be set to windows path issue

Greetings Experts, I need to pass a parameter to ksh and the value is windows path eg: sh abc.txt C:\Users\chill3chee\Desktop No matter I try with \ delimiter, still could not get this exact value assigned to the shell variable which was checked with echo. Tried with using... (2 Replies)
Discussion started by: chill3chee
2 Replies

4. Red Hat

Oracle Linux issue - all files FTPed to it from windows need to to be processed with dos2UNIX

Hello Friends, I have observed one recent issue about ftp from windows to Linux. Initially we had Solaris unix and any file sent from windows to solaris via ftp (binary or ascii) worked smoothly. Say for e.g if I sent a shell script to soalris from windows, that script used to run corectly.... (17 Replies)
Discussion started by: Albert_Pinto7
17 Replies

5. Windows & DOS: Issues & Discussions

Plink issue in windows

I had a simple automation process to take config backup from san switches to windows via SSH. This can be accomplished using plink. My script was working fine earlier but from last few days it is not collecting data and the error which i am getting is below. "":confused: I have done the... (6 Replies)
Discussion started by: nirjhar17
6 Replies

6. UNIX for Beginners Questions & Answers

X Windows Security Issue

Hi there, I am trying to understanding the difference between X11, host- based versus user-based access controls. And how vulnerability can the X11 settings be and why it is recommended to turn it off. (1 Reply)
Discussion started by: alvinoo
1 Replies

7. UNIX for Advanced & Expert Users

X windows issue

Hello, I am trying to fire up a GUI in my Unix server as root and it comes out with this error MobaXterm X11 proxy: Unsupported authorisation protocol Error: Can't open display: localhost:11.0 Is this to do with the Xauthority file as I have added this command to it xauth add... (8 Replies)
Discussion started by: DOkuwa
8 Replies
qmail-getpw(8)						      System Manager's Manual						    qmail-getpw(8)

NAME
qmail-getpw - give addresses to users SYNOPSIS
qmail-getpw local DESCRIPTION
In qmail, each user controls a vast array of local addresses. qmail-getpw finds the user that controls a particular address, local. It prints six pieces of information, each terminated by NUL: user; uid; gid; homedir; dash; and ext. The user's account name is user; the user's uid and gid in decimal are uid and gid; the user's home directory is homedir; and messages to local will be handled by home- dir/.qmaildashext. In case of trouble, qmail-getpw exits nonzero without printing anything. WARNING: The operating system's getpwnam function, which is at the heart of qmail-getpw, is inherently unreliable: it fails to distinguish between temporary errors and nonexistent users. Future versions of getpwnam should return ETXTBSY to indicate temporary errors and ESRCH to indicate nonexistent users. RULES
qmail-getpw considers an account in /etc/passwd to be a user if (1) the account has a nonzero uid, (2) the account's home directory exists (and is visible to qmail-getpw), and (3) the account owns its home directory. qmail-getpw ignores account names containing uppercase let- ters. qmail-getpw also assumes that all account names are shorter than 32 characters. qmail-getpw gives each user control over the basic user address and all addresses of the form user-anything. When local is user, dash and ext are both empty. When local is user-anything, dash is a hyphen and ext is anything. user may appear in any combination of uppercase and lowercase letters at the front of local. A catch-all user, alias, controls all other addresses. In this case ext is local and dash is a hyphen. You can override all of qmail-getpw's decisions with the qmail-users mechanism, which is reliable, highly configurable, and much faster than qmail-getpw. SEE ALSO
qmail-users(5), qmail-lspawn(8) qmail-getpw(8)
All times are GMT -4. The time now is 03:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy