now running mac os x 10.53 and sudo chmod comes back with : operation not permitted.
sample file:
-rwxr-xr-x+ 1 1000 com.apple.monitor_all_services 276592 Jun 8 2007 342345.tif
i am running as root. (1 Reply)
Hello,
I have written a script that has a sudo command to change file permissions within it.
When I run the script manually, the sudo command inside of it works fine.
When the script is run through crontab I get the error "cron: not found".
It the same user profile that I am using... (6 Replies)
Hi All,
i have a cron entry like
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /amex/sssmonitor/dss_chk.ksh
and the script is like
#!/bin/ksh
file=`uname -n`
> /sunmast/projects/oasis/COREDEV/Dss$file.log
> /tmp/output_sss
today=`date`
varb=`ps -ef | grep... (5 Replies)
Legends,
I am trying sudo chmod from one shell to different machine. but getting the error.
Please let me know if there is any way to do this.
A#pk} for i in Bl1 Brl1
>> do
>> echo $i
>> ssh $i sudo chmod 755 /etc/services
>> done
Bl1
Password:
bash: sudo: command not found
... (2 Replies)
Have a sudo statement inside of a here document. It prompts me for a password, but doesnt wait for me to enter my password. Is there a way I can use the command without sudo or anyway that I can enter the password correctly?
Eg :
while read remotehost
do
ssh -t $2@$remotehost <<REMOTE... (13 Replies)
This is the first time for using sudo for me.
# visudo
## Allows people in group admin to run all commands
%admin ALL=(ALL) ALL
# groupadd admin
# useradd temp
# usermod -a -G admin temp
# id temp
uid=506(temp) gid=506(temp) groups=506(temp),507(admin)
#
#sudo... (5 Replies)
I have a situation where the system is dumping a 2g causing filesystem to fill up. We identified the source and working on a solution. However, I wanted to limit the size of the 'core' file.
Please examine the test scenario ...
cnewtonne@mars> ulimit -f 0
cnewtonne@mars> ls -ltr core*... (2 Replies)
Hi All, I need your expertise to solve my problem, my account has permission to make sudo and su but when I try to switch user in a shell, it does not work with following message:
"Sorry, user jmbeltra is not allowed to execute '/usr/bin/su -c echo HELLO THERE - oracle' as root on dbbr1k01"
I... (4 Replies)
Hi All, im a bit new to Solaris 10 iv been working on Redhat and cant seem to get the sudo working on Solaris 10:D
Iv installed the below packages via pkgadd command:
gcc-4.7.2-sol10-x86-local
libiconv-1.14-sol10-x86-local
libintl-3.4.0-sol10-x86-local
sudo-1.8.13-sol10-x86-local
... (1 Reply)
Hi,
I have configured ldap manually on solaris 10/11 machine with below entries:
# ldapclient list |grep sudo
NS_LDAP_SERVICE_SEARCH_DESC= sudoers:ou=SUDOers,dc=exm,dc=ple,dc=com
# cat /etc/nsswitch.conf |grep -i sudo
sudoers: files ldap
#
But groups available in LDAP server... (8 Replies)
Discussion started by: Sridaran
8 Replies
LEARN ABOUT DEBIAN
calife.auth
CALIFE.AUTH(5) BSD File Formats Manual CALIFE.AUTH(5)NAME
calife.auth -- format of the calife authorization file
DESCRIPTION
The calife.auth files are files consisting of newline separated records, one per user, containing three colon (``:'') separated fields.
These fields are as follows:
name User's login name / @group.
shell User's shell
user1,user2,...,usern
List of logins allowed for the user name
The name field is the login used to access the computer account.
The login name must never begin with a hyphen (``-''); also, it is strongly suggested that neither upper-case characters or dots (``.'') be
part of the name, as this tends to confuse mailers. No field may contain a colon (``:'') as this has been used historically to separate the
fields in the user database.
One alternative syntax is to use @group to specify that any user in the given group is allowed to use calife to become root.
The shell field is the command interpreter the user prefers. If there is nothing in the shell field, the user's current shell as found in
the (/etc/passwd) file is assumed.
If the shell field is '*', then the account is considered as locked and access is denied.
If the third parameter is specified, it is assumed to be the list of login the current user has the right to become. It enables use of calife
for non-root only accounts.
calife.auth is placed in /etc.
EXAMPLE
# calife.auth-dist
#
# Format
#
# name[:shell_to_be_run][:user1,user2,usern]
#
fcb
roberto:/bin/tcsh
pb::guest,blaireau
SEE ALSO calife(1), su(1)HISTORY
A calife.auth file format appeared in DG/UX and SunOS, written for Antenne 2 in 1991. It has evolved with the extra shell specification. The
login list was reintroduced in 2.7.
AUTHOR
Ollivier Robert <roberto@keltia.frmug.fr.net>
BSD September 25, 1994 BSD