Sponsored Content
Full Discussion: Usernames in Sudoers have #
Top Forums UNIX for Advanced & Expert Users Usernames in Sudoers have # Post 302305268 by Gibby13 on Wednesday 8th of April 2009 11:22:05 AM
Old 04-08-2009
Usernames in Sudoers have #

We have users that have a # in their username. Sudo is working on some servers and not others. I have narrowed it down to the # in their username. Any suggestions or ideas why it is working on 1 server but not another.

Server not working is - Solaris 10 patch level 138888-01
Server working is - Solaris 10 patch level 137111-01
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

max charachters for usernames

Can anyone tell me what the charachter maximum on a username is in SunOs 5.6. Thanks Mark (1 Reply)
Discussion started by: m.szylkarski
1 Replies

2. UNIX for Advanced & Expert Users

Usernames and processes most used

I need a command that returns the usernames that have ran the 10 processes that have taken the most time to execute on a machine. I also need a command that returns only those directories that have read/execute permissions for all the users. (4 Replies)
Discussion started by: anw68ster
4 Replies

3. Shell Programming and Scripting

extracting usernames with at least 4 characters

Hi, i want to use grep to extract users with at least 4 characters in their username, i've tried who | grep \{4,\} but thats not working!!!!!! Thanks (4 Replies)
Discussion started by: c19h28O2
4 Replies

4. Post Here to Contact Site Administrators and Moderators

What is meant by the words under usernames?

Under all users, there are some keynames. Some are obvious, like Moderator and Registered User. I have seen others too. What do they mean or signify?;) (2 Replies)
Discussion started by: joeyg
2 Replies

5. UNIX for Advanced & Expert Users

Usernames across Applications

Hello everyone, I was just wondering if there was a way to make it so that usernames could be used across applications. For instance, I have a server that has a bunch of users. I want these users to have ways of accessing my database as well as a variety of other programs, but I don't want them... (2 Replies)
Discussion started by: gonzofish
2 Replies

6. Shell Programming and Scripting

Creating usernames from a list of names

Hello everyone, I am trying to create a script that will make usernames (last name and first letter of name - for example, James Bond = bondj). At this point, I figured out how to make a script that can read the list of names from a text file. Here is what I have: #!/bin/bash ... (5 Replies)
Discussion started by: RSpades
5 Replies

7. Shell Programming and Scripting

Loop through usernames 1 by 1 and select

Hello All, A quick description of what I would like to do; 1) Find all the current registered usernames and loop through them. 2) Display each username 1 by 1 and Ask the user if they would like to store the username in another array (y or n) 3) Display the list of chosen usernames... (4 Replies)
Discussion started by: mmab
4 Replies

8. Solaris

Individual usernames for the same login account

Hi There is an application installed on a server, that has a unique login account, but many users are using it with the same login name! How can we overcame this by creating individual accounts for the same application login account? (11 Replies)
Discussion started by: fretagi
11 Replies

9. Homework & Coursework Questions

Display usernames and their UIDs

Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted! 1. The problem statement, all variables and given/known data: Write a script that displays all usernames and their UIDs in the following fashion: name1 uid=999 name2... (2 Replies)
Discussion started by: baniel
2 Replies
GIT-CVSEXPORTCOMMIT(1)						    Git Manual						    GIT-CVSEXPORTCOMMIT(1)

NAME
git-cvsexportcommit - Export a single commit to a CVS checkout SYNOPSIS
git cvsexportcommit [-h] [-u] [-v] [-c] [-P] [-p] [-a] [-d cvsroot] [-w cvsworkdir] [-W] [-f] [-m msgprefix] [PARENTCOMMIT] COMMITID DESCRIPTION
Exports a commit from GIT to a CVS checkout, making it easier to merge patches from a git repository into a CVS repository. Specify the name of a CVS checkout using the -w switch or execute it from the root of the CVS working copy. In the latter case GIT_DIR must be defined. See examples below. It does its best to do the safe thing, it will check that the files are unchanged and up to date in the CVS checkout, and it will not autocommit by default. Supports file additions, removals, and commits that affect binary files. If the commit is a merge commit, you must tell git cvsexportcommit what parent the changeset should be done against. OPTIONS
-c Commit automatically if the patch applied cleanly. It will not commit if any hunks fail to apply or there were other problems. -p Be pedantic (paranoid) when applying patches. Invokes patch with --fuzz=0 -a Add authorship information. Adds Author line, and Committer (if different from Author) to the message. -d Set an alternative CVSROOT to use. This corresponds to the CVS -d parameter. Usually users will not want to set this, except if using CVS in an asymmetric fashion. -f Force the merge even if the files are not up to date. -P Force the parent commit, even if it is not a direct parent. -m Prepend the commit message with the provided prefix. Useful for patch series and the like. -u Update affected files from CVS repository before attempting export. -k Reverse CVS keyword expansion (e.g. $Revision: 1.2.3.4$ becomes $Revision$) in working CVS checkout before applying patch. -w Specify the location of the CVS checkout to use for the export. This option does not require GIT_DIR to be set before execution if the current directory is within a git repository. The default is the value of cvsexportcommit.cvsdir. -W Tell cvsexportcommit that the current working directory is not only a Git checkout, but also the CVS checkout. Therefore, Git will reset the working directory to the parent commit before proceeding. -v Verbose. CONFIGURATION
cvsexportcommit.cvsdir The default location of the CVS checkout to use for the export. EXAMPLES
Merge one patch into CVS .ft C $ export GIT_DIR=~/project/.git $ cd ~/project_cvs_checkout $ git cvsexportcommit -v <commit-sha1> $ cvs commit -F .msg <files> .ft Merge one patch into CVS (-c and -w options). The working directory is within the Git Repo .ft C $ git cvsexportcommit -v -c -w ~/project_cvs_checkout <commit-sha1> .ft Merge pending patches into CVS automatically -- only if you really know what you are doing .ft C $ export GIT_DIR=~/project/.git $ cd ~/project_cvs_checkout $ git cherry cvshead myhead | sed -n 's/^+ //p' | xargs -l1 git cvsexportcommit -c -p -v .ft AUTHOR
Written by Martin Langhoff <martin@catalyst.net.nz[1]> and others. DOCUMENTATION
Documentation by Martin Langhoff <martin@catalyst.net.nz[1]> and others. GIT
Part of the git(1) suite NOTES
1. martin@catalyst.net.nz mailto:martin@catalyst.net.nz Git 1.7.1 07/05/2010 GIT-CVSEXPORTCOMMIT(1)
All times are GMT -4. The time now is 11:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy