03-27-2002
Quote:
especially on systems where more than one person have/need root access.
And even better, you don't necessarily have to give the user root access. They can simply execute a command / script as another specified user as well, so they have no root access at all. You can also set it up so that everyone in one group can use sudo, rather than having to set it up for each individual person.
See if you have it installed and check the man page. If not, see here:
http://www.courtesan.com/sudo/
10 More Discussions You Might Find Interesting
1. Solaris
OS: Solaris 5.8
Everytime I run fsck -y I get: FILE SYSTEM STATE IN SUPERBLOCK IS WRONG; FIX? yes
Do I need to run fsck with the backup superblock option or is there
some other option I should use. I have tried the format->analyze->read
option but that does not report any corrupt blocks.... (5 Replies)
Discussion started by: run_time_error
5 Replies
2. UNIX for Dummies Questions & Answers
I want to use fsck to check and repair my linux system. When I use this command, what do I need to pay attention to or what should I do to make job running successfully. Thanks for your inputs for a newbie. (3 Replies)
Discussion started by: duke0001
3 Replies
3. UNIX for Dummies Questions & Answers
hy guys
I got a ques
I cant acess root, i tried to fsck it, but gets errors to read file systems. What steps do you take to recover the host before you see if there is any data corruption on the root drive?
Regards
Charneet (1 Reply)
Discussion started by: charneet
1 Replies
4. Solaris
Hello
I am getting this in dmesg:
/mount1: unexpected free inode 1262865, run fsck(1M) -o f
What are the options I should use with fsck?
thanks (2 Replies)
Discussion started by: melanie_pfefer
2 Replies
5. UNIX for Dummies Questions & Answers
i want to know what does it mean by doing a consistentcy check fsck on a disk and why journaling filesystems dont need to do it
and what is meant by disk is in a consistent state when writing because entries are recorded in a journal and then to the metadata and then removed from journal (1 Reply)
Discussion started by: farhan_t49
1 Replies
6. UNIX for Dummies Questions & Answers
Hello
I own a SPARC Ultra 10 workstation (standalone) and when issuing the fsck command I get the following output on fs C0t0d0s7:
Phase 1 (checks blocks and sizes):
dada warning: /pci@lf;0/pci@1, 1/ide@3/dad@0,0(dad1): ATA Transport failed:reason, `incomplete'>
Uncorrectable data... (2 Replies)
Discussion started by: tjwops
2 Replies
7. Solaris
What can I fix this issue? I have ran below commands but everything is same.:confused:
WARNING: Last shutdown is later than time on time-of-day chip: check date.
The / file system (/dev/rdsk/c1t0d0s0) is being checked
WARNING - unable to repair the / filesystem. Run fsck manually (fsck -F... (4 Replies)
Discussion started by: getrue
4 Replies
8. UNIX for Advanced & Expert Users
unable to repair the / filesystem. Run fsck manually (fsck -F ufs /dev/rdsk/c1t0d0s0)
--------------------------------------------------------------------------------
What can I fix this issue? I have ran below commands but everything is same.
WARNING: Last shutdown is later than time... (2 Replies)
Discussion started by: VijayPuttu
2 Replies
9. Solaris
Hi,
When we are running fsck in vxvm FS within few sec it will completed even if data is more than 500GB or in TB also.
compare to UFS FS in that it will take more time compare with vxvm.UFS check FS in block level. & then vvxm on where its checking the FS.
Please explain. (1 Reply)
Discussion started by: tiger09
1 Replies
10. Solaris
Dear all,
solaris version
--------------------
Oracle Solaris 10 9/10 s10s_u9wos_14a SPARC
Copyright (c) 2010, Oracle and/or its affiliates. All rights reserved.
Assembled 11 August 2010
-bash-3.2$ uname -a
SunOS nblabsvr 5.10 Generic_144488-08 sun4u sparc SUNW,SPARC-Enterprise
... (5 Replies)
Discussion started by: ossupport55
5 Replies
LEARN ABOUT DEBIAN
sbuild-adduser
SBUILD-ADDUSER(8) Debian sbuild SBUILD-ADDUSER(8)
NAME
sbuild-adduser - add an sbuild user
SYNOPSIS
sbuild-adduser [-h|--help | -V|--version] USER1 [USER2 [USERn...]]
DESCRIPTION
sbuild-adduser adds the specified users to the sbuild group, granting them the privelege to build packages with sbuild(1). The schroot(1)
configuration must permit the user to obtain root permissions in the chroot via the root-users and root-groups options in schroot.conf,
because this is required to install and remove build-dependencies inside the chroot. This is normally done using the sbuild group, but
additional users or groups may be added in order to grant finer-grained permissions, for example to restrict individual users to particular
chroots.
OPTIONS
Actions
-h, --help
Display this manual.
-V, --version
Print version information.
User selection
USER The user to be granted sbuild access.
EXAMPLES
To allow user rleigh sbuild access:
% sudo sbuild-adduser rleigh
AUTHORS
Roger Leigh.
COPYRIGHT
Copyright (C) 2006-2008 Roger Leigh <rleigh@debian.org>.
SEE ALSO
sbuild(1), sbuild-setup(7), schroot.conf(5).
Version 0.63.2 18 Aug 2012 SBUILD-ADDUSER(8)