Please forgive the OTishness of this, but I'm hoping some of
my fellows in the large data center space may have a hint or
two here ...
I am working with a firm that needs to run sudo in a variety of
OS environments. A few of these - noteably IBM AIX - do not provide
vendor support and legal
Hi,
Tim Daneliuk wrote:
Please forgive the OTishness of this, but I'm hoping some of
my fellows in the large data center space may have a hint or
two here ...
I am working with a firm that needs to run sudo in a variety of
OS environments. A few of these - noteably IBM AIX - do not provide
installed X,
icewm, windowmaker, firefox36, thunderbird, gimp and a few others. I
think I've eliminated all the cruft from 9.0. However, I can't build
sudo (or screen) and I can't work out why. Here is the error:
# make distclean clean install
=== Cleaning for sudo-1.8.4
=== Deleting distfiles
On 03/03/12 12:31, ill...@gmail.com wrote:
Stale header files in /usr/include maybe?
Hi,
Yes that's it. It seems utmp.h got changed to utmpx.h between 8.2
and 9.0. Fixed by csup of 9.0-R and doing the buildworld buildkernel etc.
thanks,
--
freebsd at growveg dot net
On 3 March 2012 14:43, FreeBSD Mailing Lists free...@growveg.net wrote:
On 03/03/12 12:31, ill...@gmail.com wrote:
Stale header files in /usr/include maybe?
Hi,
Yes that's it. It seems utmp.h got changed to utmpx.h between 8.2 and
9.0. Fixed by csup of 9.0-R and doing the buildworld
On 04/03/2012 04:36, ill...@gmail.com wrote:
Hmm, I would think that merely removing the offending file
and copying the correct one from /usr/obj/usr/src/tmp/usr/include/
would suffice.
I dunno, I don't think so. Why would it not be installed in the
downgrade process? Also, the filenames
eliminated all the cruft from 9.0. However, I can't build
sudo (or screen) and I can't work out why. Here is the error:
# make distclean clean install
=== Cleaning for sudo-1.8.4
=== Deleting distfiles for sudo-1.8.4
=== License sudo accepted by the user
=== Found saved configuration for sudo
On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote:
hi
I add line to syslog.conf
and killall -HUP syslogd
Tell me please how to stop sudo to food /var/log/messages?
There is a short block for that functionality in
the file /usr/local/etc/sudo.conf.sample which you
can create your
On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote:
Tell me please how to stop sudo to food /var/log/messages?
ADDITION: Of course I meant /usr/local/etc/sutoers,
NOT sudo.conf.
Instead of logging via syslog (to /var/log/messages),
why not use a specific log file for sudo? Add those
lines
Здравствуйте, Polytropon.
Вы писали 4 декабря 2011 г., 15:41:45:
P On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote:
Tell me please how to stop sudo to food /var/log/messages?
P ADDITION: Of course I meant /usr/local/etc/sutoers,
P NOT sudo.conf.
P Instead of logging via syslog
Коньков Евгений kes-...@yandex.ru writes:
Здравствуйте, Polytropon.
Вы писали 4 декабря 2011 г., 15:41:45:
P On Sun, 4 Dec 2011 05:34:19 +0200, Коньков Евгений wrote:
Tell me please how to stop sudo to food /var/log/messages?
P ADDITION: Of course I meant /usr/local/etc/sutoers,
P
hi
I add line to syslog.conf
and killall -HUP syslogd
Tell me please how to stop sudo to food /var/log/messages?
--
С уважением,
Коньков mailto:kes-...@yandex.ru
___
freebsd-questions@freebsd.org mailing list
http
Hi FreeBSD Folks,
I'm using Samba 3.5.6 to authenticate logins and manage access on FreeBSD 8.1.
With Sudo 1.7.2, I was able to use Active Directory groups in sudoers(5), but
this doesn't seem to work in 1.7.4.
Versions:
$ uname -a
FreeBSD cis-mvl.ml.unisa.edu.au 8.1-RELEASE-p2 FreeBSD 8.1
Steven Friedrich free...@insightbb.com wrote:
... tried sudo mail. I got root's mailbox nd I deleted all but two
emails. When I q(uit) mail, it said it saved 2 messages in mbox.
But when I try to go back in it says I don't have any mail. There
is no root directory in /var/mail.
Did sudo
On Sunday 26 September 2010 11:21:50 pm you wrote:
From free...@insightbb.com Sun Sep 26 18:14:09 2010
From: Steven Friedrich free...@insightbb.com
To: Robert Bonomi bon...@mail.r-bonomi.com
Subject: Re: sudo anomaly
Date: Sun, 26 Sep 2010 19:16:00 -0400
On Sunday 26 September 2010
, and tried sudo mail. I got
root's mailbox nd I deleted all but two emails. When I q(uit) mail, it said it
saved 2 messages in mbox. But when I try to go back in it says I don't have
any mail. There is no root directory in /var/mail.
Did sudo lose my mbox?
Can anyone verify this anomaly
me gurpreet...@gmail.com writes:
Hi,
Upon doing sudo some-command as a normal user (non-root), sudo asks for
password only once, subsequent invocations of sudo doesn't ask for password
- even though I do sudo -k or sudo -K in between.
Although sudo starts asking for password after the time
Hi,
Lowell Gilbert wrote:
megurpreet...@gmail.com writes:
Upon doing sudosome-command as a normal user (non-root), sudo asks for
password only once, subsequent invocations of sudo doesn't ask for password
- even though I do sudo -k or sudo -K in between.
Although sudo starts asking
I don't see anything suspicious in the timestamp directory:
foo% sudo ls -l /var/run/sudo/
total 12
drwx-- 2 root wheel 512 Aug 2 01:06 gurpreet
drwx-- 2 root wheel 512 Aug 2 00:37 other
drwx-- 2 root wheel 512 Aug 2 00:37 third
foo% sudo ls -l /var/run/sudo/gurpreet
by design. There's a timeout that you can set, ...
Chris,
That is not by design.
sudo -K should remove the timestamp
--
sudo
-K The -K (sure kill) option is like -k except that it
removes
the user's time stamp entirely and may not be used
Hi,
Upon doing sudo some-command as a normal user (non-root), sudo asks for
password only once, subsequent invocations of sudo doesn't ask for password
- even though I do sudo -k or sudo -K in between.
Although sudo starts asking for password after the time stamp expiry.
in other words:
% sudo
It's by design. There's a timeout that you can set, try man sudo.
Chris
Sorry for top-posting, Android won't let me quote, but K-9 can't yet do
threading.
On 30 Jul 2010 21:43, me gurpreet...@gmail.com wrote:
Hi,
Upon doing sudo some-command as a normal user (non-root), sudo asks
On 07/30/2010 06:00 PM, Chris Rees wrote:
It's by design. There's a timeout that you can set, try man sudo.
Chris
Chris,
That is not by design.
sudo -K should remove the timestamp
--
sudo
-K The -K (sure kill) option is like -k except that it
removes
I have actually seen this on some FreeBSD6.3 systems and thought
it was a querk. It may still be a querk but it has started again
on an 8.0 system. I think I am doing something to cause it, but
I am not sure.
When one executes a sudo command, I get a last login
message which reflects
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/06/2010 19:41:04, Martin McCormick wrote:
When one executes a sudo command, I get a last login
message which reflects the last time I ran sudo. Example:
Any ideas as to what to look at?
/usr/local/etc/pam.d/sudo probably
.
When one executes a sudo command, I get a last login
message which reflects the last time I ran sudo. Example:
[mar...@pilot ~]$ sudo whoami
Password:
Last login: Thu Jun 24 13:07:20 from pilot.it.okstate
root
There is another FreeBSD8.0 system here that has not yet
I'm using FreeBSD 8-STABLE from yesterday. I had sudo 1.6.9.20 installed
and used portupgrade to upgrade it to 1.7.2.2. At this point, it stopped
working:
$ sudo -v
otp-md5 [something]
Password:
Sorry, try again.
otp-md5 [something]
Password:
Sorry, try again.
otp-md5 [something]
Password
On 02/04/2010 10:26 AM, Kirk Strauser wrote:
Any idea why that may be or how I could troubleshoot it, short of
bisecting the sudo releases until I find the culprit?
Eh, did it anyway. The problem was with a change added between 1.7.2p1
and 1.7.2p2. This patch fixes it:
--- auth/pam.c.orig
Hello,
I have an sh script that is called by the www process which has a
shell that defaults to /sbin/nologin
I have configured the sudoers file with these settings:
www ALL=(www) NOPASSWD: /usr/local/bin/postfixadmin-domain-
postdeletion.sh
And It does not seem to be able to execute…
to sudo to run as that
account. Did you mean to setup the rule for the postfix user? Or a
postfix target account?
That said, I think what you typed should have worked. You shouldn't have
seen www is not allowed to execute ... as www, because your sudoers
file says otherwise.
Assuming your account
On Thu, Sep 03, 2009 at 08:10:36PM -0400, Jerry wrote:
On Fri, 4 Sep 2009 01:34:05 +0200 Mel Flynn wrote:
alias spico='/usr/local/bin/sudo pico -m' and be done with it.
Instead of an extra alias, why not export $VISUAL or $EDITOR, and rely
on sudoedit(8)?
That is what I am currently doing
On Fri, Sep 4, 2009 at 10:50 AM, George Davidovichfree...@optimis.net wrote:
On Thu, Sep 03, 2009 at 08:10:36PM -0400, Jerry wrote:
On Fri, 4 Sep 2009 01:34:05 +0200 Mel Flynn wrote:
alias spico='/usr/local/bin/sudo pico -m' and be done with it.
Instead of an extra alias, why not export
On Wednesday 02 September 2009 13:26:59 Jerry wrote:
I have set up several 'alias' definitions in my .bashrc file. They are
honored when run as either a regular user or as root. However, when I
prefix a command with 'sudo', the alias is no longer honored. In other
words, the actual command
On Fri, 4 Sep 2009 01:34:05 +0200
Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote:
alias spico='/usr/local/bin/sudo pico -m' and be done with it.
That is what I am currently doing; however,there are other commands
that I want to use that are not available when used via sudo
On Friday 04 September 2009 02:10:36 Jerry wrote:
On Fri, 4 Sep 2009 01:34:05 +0200
Mel Flynn mel.flynn+fbsd.questi...@mailing.thruhere.net wrote:
alias spico='/usr/local/bin/sudo pico -m' and be done with it.
That is what I am currently doing; however,there are other commands
that I want
I have set up several 'alias' definitions in my .bashrc file. They are
honored when run as either a regular user or as root. However, when I
prefix a command with 'sudo', the alias is no longer honored. In other
words, the actual command is run;however, any flags that I was passing
to it via
On 9/2/09, Jerry ges...@yahoo.com wrote:
I have set up several 'alias' definitions in my .bashrc file. They are
honored when run as either a regular user or as root. However, when I
prefix a command with 'sudo', the alias is no longer honored. In other
words, the actual command is run;however
On Wed, 2 Sep 2009 13:06:28 -0600
Tim Judd taj...@gmail.com wrote:
[snip]
Because sudo calls the binary, via SUID on sudo. It doesn't pay
attention to user profiles or rc files (like .bashrc).
I don't use sudo, so I can't recommend past that.
In other words, sudo is not compatible
In the last episode (Sep 02), Jerry said:
On Wed, 2 Sep 2009 13:06:28 -0600
Tim Judd taj...@gmail.com wrote:
Because sudo calls the binary, via SUID on sudo. It doesn't pay
attention to user profiles or rc files (like .bashrc).
I don't use sudo, so I can't recommend past
On Wed, 2 Sep 2009 15:06:48 -0500, Dan Nelson dnel...@allantgroup.com wrote:
sudo does not run root's shell at all; it directly runs whatever is given it
on the commandline.
Another idea would to be to call sudo with the desired shell as
argument (in order to inherit the aliases), followed
On 02/19/2009 15:56, Aleksandr Miroslav wrote:
For the longest time, I have installed ports via the sudo make install or
sudo portupgrade or sudo portinstall method and never had a problem.
This seems to have jumped up and bitten me on the arse as well. I
believe the problem lies herein:
http
lowering the umask of the person running sudo.
This had the effect of truly screwing up many installed ports for me
Maybe try sudo -H -u root [command] NetBSD Pkgsrc is nice in this
respect because it has sudo(8) integration in the MKs. ~BAS
signature.asc
Description
On 02/25/2009 11:49, Brian A. Seklecki wrote:
lowering the umask of the person running sudo.
This had the effect of truly screwing up many installed ports for me
Maybe try sudo -H -u root [command] NetBSD Pkgsrc is nice in this
respect because it has sudo(8) integration in the MKs. ~BAS
, created the local brouhaha with
groups credential crashing. Perhaps next time a -dev extension of the
port should roll for a few months (6-9), especially given the history of
sudo releng.
~BAS
signature.asc
Description: This is a digitally signed message part
I'm setting up a centralized Kerberos/LDAP authentication system and
trying to get sudo to use a) Kerberos for the password, and b) LDAP for
a non-local user's group.
Locally on a client system /etc/sudoers specifies %sysadmin to be able
to sudo to root. I don't need to move sudoers to LDAP
How do I run multiple sudo commands at once? This fails because the
semicolon ends the whole sudo command:
sudo whoami; whoami
root
user
This confuses tcsh:
monica:~ sudo ( whoami ; whoami )
Badly placed ()'s.
I could obviously write a shell script or something or do:
sudo whoami; sudo
How do I run multiple sudo commands at once? This fails
because the semicolon ends the whole sudo command:
sudo whoami; whoami
root
user
This confuses tcsh:
monica:~ sudo ( whoami ; whoami )
Badly placed ()'s.
Supposing sudo spawns a shell, something like
~ sudo whoami \; whoami
This works for me:
sudo sh -c whoami;whoami
On Oct 25, 2008, at 9:11 PM, Kelly Jones wrote:
How do I run multiple sudo commands at once? This fails because the
semicolon ends the whole sudo command:
sudo whoami; whoami
root
user
This confuses tcsh:
monica:~ sudo ( whoami ; whoami
All,
I am having a wierd problem with sudo on a FreeBSD 7 system that is
joined to AD domain through Samba. When I sudo a command, when prompted
for a password, any password including a blank one works. Obviously a
security issue.
Here are the config files:
/usr/local/etc/sudoers
root
up and hit the serial port
just fine, but cutecom can't open it except with sudo. I tried
tweaking devfs.conf (as well as a straight chmod on /dev/cuad0), and
it doesn't seem to rectify the problem. I've also got several linux
ports that hit usb devices via libusb that won't connect
with sudo. I tried
tweaking devfs.conf (as well as a straight chmod on /dev/cuad0), and
it doesn't seem to rectify the problem. I've also got several linux
ports that hit usb devices via libusb that won't connect without sudo
- obviously, I'd like not to have to run user-type apps with sudo on
my
At 07:39 PM 4/14/2008, Steve Franks wrote:
I have two terminal programs - cutecom and minicom, both built from
ports with no tweaks. Minicom will fire up and hit the serial port
just fine, but cutecom can't open it except with sudo. I tried
tweaking devfs.conf (as well as a straight chmod
I have two terminal programs - cutecom and minicom, both built from
ports with no tweaks. Minicom will fire up and hit the serial port
just fine, but cutecom can't open it except with sudo. I tried
tweaking devfs.conf (as well as a straight chmod on /dev/cuad0), and
it doesn't seem to rectify
I noticed that every sudo command I issue is accompanied
by a Last login message.
25testokcns root $ls .hushlogin
ls: .hushlogin: No such file or directory
26testokcns root $sudo touch .hushlogin
Last login: Thu Apr 3 11:38:24 from testokcns.osuokc
27testokcns root $sudo date
Last login
On Thursday 03 April 2008 01:06:37 pm Martin McCormick wrote:
I noticed that every sudo command I issue is accompanied
by a Last login message.
25testokcns root $ls .hushlogin
ls: .hushlogin: No such file or directory
26testokcns root $sudo touch .hushlogin
Last login: Thu Apr 3 11
Steven Friedrich writes:
26testokcns root $sudo touch .hushlogin
Well, it IS odd that you're using sudo when logged in as root 8o)
I was cd'd to the /root directory, but was logged in as
me. It kind of got me there for a second, but notice the $ in
the prompt.
Interestingly
The commands always work but I would rather not get that message
each time. Am I missing something obvious?
A quick google search will show you that it's the
${LOCALBASE}/etc/pam.d/sudo file which is the root of your problem.
It's pam_lastlog(8) which makes the message. If you don't need
On Thu, 2008-04-03 at 12:06 -0500, Martin McCormick wrote:
I noticed that every sudo command I issue is accompanied
by a Last login message.
25testokcns root $ls .hushlogin
ls: .hushlogin: No such file or directory
26testokcns root $sudo touch .hushlogin
Last login: Thu Apr 3 11:38
$ whoami
v
$ ll a
-rw-r--r-- 1 root v 0 Mar 30 10:02 a
$ sudo cat a
a: Permission denied.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
On Sun, 30 Mar 2008 10:13:02 +0800, lveax [EMAIL PROTECTED] wrote:
$ whoami
v
$ ll a
-rw-r--r-- 1 root v 0 Mar 30 10:02 a
$ sudo cat a
a: Permission denied.
You have to redirect output 'within' sudo, so try using:
sudo sh -c 'cat unwritable
Hi--
I¹m trying to make a bootable clone of my startup drive, and read Mike
Bombich¹s instructions on how to do this.
He includes the following line as the last step in the process:
Finally, recreate the kernel extension cache for the CD:
sudo mkextcache -t ppc -d \
/Volumes/Rescue/System
Jeffrey Ellis wrote:
Hi--
I¹m trying to make a bootable clone of my startup drive, and read Mike
Bombich¹s instructions on how to do this.
He includes the following line as the last step in the process:
Finally, recreate the kernel extension cache for the CD:
sudo mkextcache -t ppc -d
In response to Steve Franks [EMAIL PROTECTED]:
Don't get it. I installed firefox from the package at
ftp4.us.freebsd.org like always (so I thought) but if I run 'firefox',
I get a prompt back, and no firefox, but if I run it as sudo, it comes
up fine. Where should I start fixing permissions
Don't get it. I installed firefox from the package at
ftp4.us.freebsd.org like always (so I thought) but if I run 'firefox',
I get a prompt back, and no firefox, but if I run it as sudo, it comes
up fine. Where should I start fixing permissions at, do you think?
Steve
[EMAIL PROTECTED] wrote:
On Fri, Nov 23, 2007 at 03:43:39PM -0800, Kamil Kisiel wrote:
For some reason, on this particular FreeBSD machine, sudo never asks
me for a password, even if I haven't logged in for days.
I've been struggling with this problem for some time
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/23/07, Kamil Kisiel wrote:
For some reason, on this particular FreeBSD machine, sudo never asks
me for a password, even if I haven't logged in for days. I tried
running sudo -k, sudo -K before trying it. I've even tried manually
removing
On Fri, Nov 23, 2007 at 03:43:39PM -0800, Kamil Kisiel wrote:
For some reason, on this particular FreeBSD machine, sudo never asks
me for a password, even if I haven't logged in for days.
I've been struggling with this problem for some time but still haven't
been able to find a solution. Any
On Fri, Nov 23, 2007 at 07:09:36PM -0800, Kamil Kisiel wrote:
On 11/23/07, Christopher Cowart [EMAIL PROTECTED] wrote:
On Fri, Nov 23, 2007 at 03:43:39PM -0800, Kamil Kisiel wrote:
For some reason, on this particular FreeBSD machine, sudo never asks
me for a password, even if I haven't
-0800, Kamil Kisiel wrote:
For some reason, on this particular FreeBSD machine, sudo never asks
me for a password, even if I haven't logged in for days.
I've been struggling with this problem for some time but still haven't
been able to find a solution. Any ideas
On Fri, Nov 23, 2007 at 08:01:23PM -0800, Kamil Kisiel wrote:
Alright, maybe my impression of success was slightly premature. It
seems that the problem now is that sudo doesn't like the pam_unix.so
module for whatever reason. If I use the default sudo pam file, which
simply includes all
FreeBSD machine, sudo never asks
me for a password, even if I haven't logged in for days.
I've been struggling with this problem for some time but still haven't
been able to find a solution. Any ideas?
Maybe something is misconfigured in your pam stack? Check
/etc/pam.d/sudo
For some reason, on this particular FreeBSD machine, sudo never asks
me for a password, even if I haven't logged in for days. I tried
running sudo -k, sudo -K before trying it. I've even tried manually
removing /var/run/sudo.
When I run sudo -l, I get:
User kamil may run the following commands
On 11/23/07, Christopher Cowart [EMAIL PROTECTED] wrote:
On Fri, Nov 23, 2007 at 03:43:39PM -0800, Kamil Kisiel wrote:
For some reason, on this particular FreeBSD machine, sudo never asks
me for a password, even if I haven't logged in for days.
I've been struggling with this problem
Pieter de Goeje a écrit :
Sudo by default logs with facility 'local2' and priority 'notice'. Neither one
is specified in your syslog.conf.
Yes, it fix my problem !
Thanks very much !
Nicolas
--
Nicolas Letellier, administrateur systèmes
Site personnel : http://nicoelro.net
Curriculum
On Wed, 2007-10-10 at 18:38 +0200, Nicolas Letellier wrote:
Pieter de Goeje a écrit :
Sudo by default logs with facility 'local2' and priority 'notice'. Neither
one
is specified in your syslog.conf.
To set the facility in sudoer(5):
Defaultssyslog=auth
Or local0-7
On Tuesday 09 October 2007,
Pieter de Goeje [EMAIL PROTECTED] wrote: (among other verbiage)
It logs it's (sic) messages in /var/log/messages.
Is this mentioned in the man page ? If nort, it should be!
___
freebsd-questions@freebsd.org mailing list
Hello,
In my FreeBSD 6.2, I use sudo for a user.
However, I want know who has used sudo in my machine. But, sudo doesn't
log anything. I have nothing about sudo in /var/log...
Syslog log auth.* in /var/log/auth, but nothing about sudo...
What's the problem ? Any ideas ?
Thanks !
Nicolas
On Tuesday 09 October 2007, Nicolas Letellier wrote:
Hello,
In my FreeBSD 6.2, I use sudo for a user.
However, I want know who has used sudo in my machine. But, sudo doesn't
log anything. I have nothing about sudo in /var/log...
Syslog log auth.* in /var/log/auth, but nothing about sudo
Hello,
Thanks for your response.
No, there is nothing about sudo in /var/log/messages (in anyone else
file in /var/log).
But i modified my /etc/syslog.conf. The problem could is this file ?
I pastebin my file : http://pastebin.com/m35ceae32
What's the problem to log sudo informations
On Tuesday 09 October 2007, Nicolas Letellier wrote:
Hello,
Thanks for your response.
No, there is nothing about sudo in /var/log/messages (in anyone else
file in /var/log).
But i modified my /etc/syslog.conf. The problem could is this file ?
I pastebin my file : http://pastebin.com
Hi,
On a new system that I am installing, I found out that the new version
of sudo version 1.6.9p3 clears the environment variables.
It was not the case on previous version like version 1.6.8p12.
I tried to understand what is the configuration to perform like it was
before, I tried to add
env_reset now seems to be on by default. you could turn it off if you
need to or fiddle with the env_keep and env_check lists.
That's what I mean, how to turn it off.
Olivier
___
freebsd-questions@freebsd.org mailing list
Olivier Nicole wrote:
Hi,
On a new system that I am installing, I found out that the new version
of sudo version 1.6.9p3 clears the environment variables.
It was not the case on previous version like version 1.6.8p12.
I tried to understand what is the configuration to perform like
user basis.
see /usr/local/share/doc/sudo/UPGRADE
Vince
Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED
On 07/08/07, Olivier Nicole [EMAIL PROTECTED] wrote:
env_reset now seems to be on by default. you could turn it off if you
need to or fiddle with the env_keep and env_check lists.
That's what I mean, how to turn it off.
I added the line
Defaults !env_reset
to sudoers. You might want to
[EMAIL PROTECTED] wrote:
On 07/08/07, Olivier Nicole [EMAIL PROTECTED] wrote:
env_reset now seems to be on by default. you could turn it off if you
need to or fiddle with the env_keep and env_check lists.
That's what I mean, how to turn it off.
I added the line
Defaults !env_reset
to
Posted At: Monday, July 30, 2007 8:37 AM
Posted To: FreeBSD-Ports
Conversation: /libexec/ld-elf.so.1: Undefined symbol optifd referenced
fromCOPY relocation in /bin/cp when installing sudo port
Subject: /libexec/ld-elf.so.1: Undefined symbol optifd referenced
fromCOPY relocation in /bin/cp when
Of FreeBSD-Ports
Posted At: Monday, July 30, 2007 8:37 AM
Posted To: FreeBSD-Ports
Conversation: /libexec/ld-elf.so.1: Undefined symbol optifd referenced
fromCOPY relocation in /bin/cp when installing sudo port
Subject: /libexec/ld-elf.so.1: Undefined symbol optifd referenced
fromCOPY relocation
After blithely upgrading everything else, I at-
tempted rebuilding jdk15 and, crumbs! my nfs
mounted /ports (4.7G) filled up and the build
barfed although I have WRKDIRPREFIX set in
/etc/csh.cshrc
Barbara Streisand! I thought, what could be the
prob-lem now?
% cd /ports/java/jdk15 sudo make
Christian Walther writes:
Try using pseudo tty allocation with your ssh command, it's the -t
option.
So, use ssh -t remote.system.domain sudo dhcpreset as the command.
That worked perfectly.
If this doesn't work directly, you can even try several ts. I had
best results with -ttt
We have 3 FreeBSD systems. One is trying to use ssh and sudo to
run commands on two other systems. The remote command being
executed is:
ssh remote.system.domain sudo dhcpreset
dhcpreset is an expect script most of which is shown
here:
spawn $env(SHELL)
expect -exact \#
send -- date\r
Hi Martin,
On 27/07/07, Martin McCormick [EMAIL PROTECTED] wrote:
We have 3 FreeBSD systems. One is trying to use ssh and sudo to
run commands on two other systems. The remote command being
executed is:
ssh remote.system.domain sudo dhcpreset
dhcpreset is an expect script most
On 4/7/07, Kevin Kinsey [EMAIL PROTECTED] wrote:
Jerry McAllister wrote:
Also, although telnet is a hole nowdays for logging in to a system with
an id and password for the very reasons you have given, it still has
a use. You can use it to easily poke at a port and check the response
to
Jerry McAllister wrote:
I noticed one grammatical thing of question. In the first paragraph
under Use ssh instead of Telnet or rsh/rlogin it says
they should never be used to administrate a machine over a network,
I think the word should be 'administer' instead of 'administrate'
On Fri, Apr 06, 2007 at 12:08:04PM +0100, Alex Zbyslaw wrote:
Jerry McAllister wrote:
I noticed one grammatical thing of question. In the first paragraph
under Use ssh instead of Telnet or rsh/rlogin it says
they should never be used to administrate a machine over a network,
I
Jerry McAllister wrote:
On Thu, Apr 05, 2007 at 11:28:34AM -0500, Jeremy C. Reed wrote:
On Thu, 5 Apr 2007, Kevin Kinsey wrote:
I thought I might also mention a potential sudo-shortcoming. :-D
See:
http://bsdwiki.reedmedia.net/wiki/Recognize_basic_recommended_access_methods.html
Where I
On 4/5/07, Schiz0 [EMAIL PROTECTED] wrote:
True, if that was the case I'd use sudo. But I'm the only user on my systems
that I'd trust with root access, so there's no point with my setup.
[Please don't top post]
Anyway, yes, I would say it depends on the situation, and it's even a
matter
True, if that was the case I'd use sudo. But I'm the only user on my systems
that I'd trust with root access, so there's no point with my setup.
On 4/5/07, Pietro Cerutti [EMAIL PROTECTED] wrote:
On 4/5/07, Schiz0 [EMAIL PROTECTED] wrote:
I don't use sudo. I find it rather pointless. If I
On 05/04/07, Schiz0 [EMAIL PROTECTED] wrote:
[Moved answer to the bottom -- please don't use top post]
On 4/5/07, Pietro Cerutti [EMAIL PROTECTED] wrote:
On 4/5/07, Schiz0 [EMAIL PROTECTED] wrote:
I don't use sudo. I find it rather pointless. If I need to do something
as
root, I use su
I don't use sudo. I find it rather pointless. If I need to do something as
root, I use su to gain root privileges, then when I'm done, I exit and
return to the original user. The user running su must be in the group
wheel to be able to su to root. This is a simple yet convenient security
system
1 - 100 of 205 matches
Mail list logo
