Re: SU+J Lost files after a power failure

On Oct 14, 2013, at 12:41 PM, RW wrote: > On Mon, 14 Oct 2013 11:48:18 -0700 Charles Swiger wrote: >> Yes. Without journalling, you'd normally perform the full >> timeconsuming fsck in the foreground. > > Journalling removes the need for the background fsck which only recovers > lost space. Th

Re: SU+J Lost files after a power failure

Hi-- On Oct 14, 2013, at 11:51 AM, Daniel Feenberg wrote: > This discussion skirts the critical issue - are files that are not open for > writing endangered? No description of the uses of journaling can be > considered informative if it doesn't address that explicitly. As a naive user > I have

Re: SU+J Lost files after a power failure

On 14.10.2013 20:43, Adam Vande More wrote: > On Mon, Oct 14, 2013 at 1:33 PM, CeDeROM > wrote: > > Thank you for explaining :-) So it looks that it would be sensible to > force filesystem check every n-th mount..? > > > Please explain the logic in which this he

Re: SU+J Lost files after a power failure

On 14.10.2013 18:47, Adam Vande More wrote: > There is no *warranty* as explicitly stated in > http://www.freebsd.org/copyright/freebsd-license.html > Aha, please don't play on words ;-). I think you understood I was speaking about the filesystem state not a lawyer issue.

Re: SU+J Lost files after a power failure

On 14.10.2013 20:08, RW wrote: > On Mon, 14 Oct 2013 18:34:36 +0200 > David Demelier wrote: > >> On 14.10.2013 14:39, RW wrote: > >>> If you are having problems with data integrity you might try >>> gjournal or zfs instead. >> >> Why? SU+J is enabled by default. Isn't the purpose of a journaled f

Re: SU+J Lost files after a power failure

On Mon, 14 Oct 2013 11:48:18 -0700 Charles Swiger wrote: > fsck_y_enable="YES" One of the most annoying things about SU+J is that fsck asks if you want to use the journal. So fsck -y wont do a proper check unless the journal replay fails. ___ freebsd-q

Re: SU+J Lost files after a power failure

Charles Swiger wrote: [snip] > Yes. Without journalling, you'd normally perform the full timeconsuming > fsck > in the foreground. With journalling, it should be able to do a journal > replay to restore the filesystem to an OK state, but sometimes that > doesn't restore consistency, in which c

Re: SU+J Lost files after a power failure

On Mon, 14 Oct 2013 11:48:18 -0700 Charles Swiger wrote: > Yes. Without journalling, you'd normally perform the full > timeconsuming fsck in the foreground. Journalling removes the need for the background fsck which only recovers lost space. > With journalling, it should be > able to do a j

Re: SU+J Lost files after a power failure

On Mon, 14 Oct 2013, Bruce Cran wrote: On 10/14/2013 6:16 PM, CeDeROM wrote: Isn't there Journal to prevent and reverse such damage? Unlike other journaling filesystems, UFS+J only protects the metadata, not the data itself - i.e. I think it ensures you won't have to run a manual fsck, bu

Re: SU+J Lost files after a power failure

Thank you all for good hints! This will come handy! :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-

Re: SU+J Lost files after a power failure

On Oct 14, 2013, at 11:33 AM, CeDeROM wrote: > On Mon, Oct 14, 2013 at 7:54 PM, Bruce Cran wrote: >> On 10/14/2013 6:16 PM, CeDeROM wrote: >>> Isn't there Journal to prevent and reverse such damage? >> >> Unlike other journaling filesystems, UFS+J only protects the metadata, not >> the data itse

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 1:43 PM, Adam Vande More wrote: > > > mount -o sync > should be mount sync -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 1:33 PM, CeDeROM wrote: > Thank you for explaining :-) So it looks that it would be sensible to > force filesystem check every n-th mount..? Please explain the logic in which this helps anything. > Or to do a filesystem check > after crash..? Already standard behavio

Re: SU+J Lost files after a power failure

On 10/14/2013 7:33 PM, CeDeROM wrote: Thank you for explaining :-) So it looks that it would be sensible to force filesystem check every n-th mount..? Or to do a filesystem check after crash..? Are there any flags like that to mark filesystem unclean and to force fsck after n-th mount? That would

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 7:54 PM, Bruce Cran wrote: > On 10/14/2013 6:16 PM, CeDeROM wrote: >> Isn't there Journal to prevent and reverse such damage? > > Unlike other journaling filesystems, UFS+J only protects the metadata, not > the data itself - i.e. I think it ensures you won't have to run a m

Re: SU+J Lost files after a power failure

On Mon, 14 Oct 2013 18:34:36 +0200 David Demelier wrote: > On 14.10.2013 14:39, RW wrote: > > If you are having problems with data integrity you might try > > gjournal or zfs instead. > > Why? SU+J is enabled by default. Isn't the purpose of a journaled file > system to ensure that any bad shutd

Re: SU+J Lost files after a power failure

On 10/14/2013 6:16 PM, CeDeROM wrote: Isn't there Journal to prevent and reverse such damage? Unlike other journaling filesystems, UFS+J only protects the metadata, not the data itself - i.e. I think it ensures you won't have to run a manual fsck, but just like plain old UFS files may be trun

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 7:09 PM, Brad Mettee wrote: > On 10/14/2013 12:50 PM, CeDeROM wrote: >> Then why random files gets damaged as well even they are not >> accessed/written on power loss? :-) > > Random files can be affected because the sectors of the hard disk containing > the directory entri

Re: SU+J Lost files after a power failure

On 10/14/2013 12:50 PM, CeDeROM wrote: On Mon, Oct 14, 2013 at 6:47 PM, Adam Vande More wrote: On Mon, Oct 14, 2013 at 11:34 AM, David Demelier wrote: Why? SU+J is enabled by default. Isn't the purpose of a journaled file system to ensure that any bad shutdown will protect data? As already st

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 6:56 PM, Adam Vande More wrote: > On Mon, Oct 14, 2013 at 11:50 AM, CeDeROM wrote: >> Then why random files gets damaged as well even they are not >> accessed/written on power loss? :-) > Prove they weren't. Hmm, maybe /etc/pwd.db as David mentioned? This is updated on pa

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 11:50 AM, CeDeROM wrote: > > Then why random files gets damaged as well even they are not > accessed/written on power loss? :-) > Prove they weren't. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lis

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 6:47 PM, Adam Vande More wrote: > On Mon, Oct 14, 2013 at 11:34 AM, David Demelier > wrote: >> >> Why? SU+J is enabled by default. Isn't the purpose of a journaled file >> system to ensure that any bad shutdown will protect data? > > As already stated, those measures are to

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 11:34 AM, David Demelier wrote: > > Why? SU+J is enabled by default. Isn't the purpose of a journaled file > system to ensure that any bad shutdown will protect data? > As already stated, those measures are to preserve fs integrity eg meta data is in sync. It doesn't ensu

Re: SU+J Lost files after a power failure

On Mon, Oct 14, 2013 at 6:34 PM, David Demelier wrote: > Why? SU+J is enabled by default. Isn't the purpose of a journaled file > system to ensure that any bad shutdown will protect data? > > On GNU/Linux, on Windows you will not require anything else to recover > your data. > > I don't want to tw

Re: SU+J Lost files after a power failure

On 14.10.2013 14:39, RW wrote: > On Mon, 14 Oct 2013 05:02:22 -0400 > Michael Powell wrote: > >> David Demelier wrote: >> >>> Hello there, >>> >>> I'm writing because after a power failure I was unable to log in on >>> my FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly >>> but some f

Re: SU+J Lost files after a power failure

On Mon, 14 Oct 2013 05:02:22 -0400 Michael Powell wrote: > David Demelier wrote: > > > Hello there, > > > > I'm writing because after a power failure I was unable to log in on > > my FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly > > but some files disappeared, including /etc/pwd.

Re: SU+J Lost files after a power failure

Michael Powell wrote: [snip] > The other box is my first foray into the land of GPT, along with SU+J. It > was sitting at the 'couldn't mount... Press return for /bin/sh' line. > There was an error indicating that replaying one or more journals had > failed. I was able to successfully fsck all the

Re: SU+J Lost files after a power failure

David Demelier wrote: > Hello there, > > I'm writing because after a power failure I was unable to log in on my > FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some > files disappeared, including /etc/pwd.db. Thus I was unable to log in. > > I've been able to regenerate the p

Re: SU+J Lost files after a power failure

> On 13.10.2013 12:16, CeDeROM wrote: > > On 13 Oct 2013 11:30, "David Demelier" > > wrote: > >> Hello there, > >> I'm writing because after a power failure I was unable to log in on my > >> FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some > >

Re: SU+J Lost files after a power failure

On 13.10.2013 12:16, CeDeROM wrote: > On 13 Oct 2013 11:30, "David Demelier" > wrote: >> Hello there, >> I'm writing because after a power failure I was unable to log in on my >> FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some >> files disapp

Re: SU+J Lost files after a power failure

On 13 Oct 2013 11:30, "David Demelier" wrote: > Hello there, > I'm writing because after a power failure I was unable to log in on my > FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some > files disappeared, including /etc/pwd.db. Thus I was unable to log in. > I've been able t

Re: SU

are you logged as su, and can't execute commands ? or does su fail ? if you're correctly identified, what does your env and/or set contains Samuel Martín Moro CamTrace {EPITECH.} tek4 "Nobody wants to say how this works. Maybe nobody knows ..." Xorg.conf(5) On Tue, Jan 26,

Re: SU

Shone Russell wrote: I am not able to execute any commands when I utilize the su function, I am entering our correct password. It was working on Friday, but now it's not. Please let us know exactly what you're entering (without the password, of course) and what the results are. Do you get an

RE: SU Question

Sorry, I have the answer, my apologize to all. VJ Viraj Dixit City of Palo Alto Information Technology 650-329-2118 From: Dixit, Viraj Sent: Thursday, April 30, 2009 3:46 PM To: 'freebsd-questions@freebsd.org' Subject: RE: SU Question

RE: SU Question

Hi, I just installed Free BSD OS 7.1 and installation went without any errors, all looks good till I try to login with SU account via telnet and I get this error below. Please help!! VJ ___ freebsd-questions@freebsd.org mailing list http://

RE: SU Question

: 'freebsd-questions@freebsd.org' Subject: RE: SU Question Hi, I just installed Free BSD OS 7.1 and installation went without any errors, all looks good till I try to login with SU account via telnet and I get this error below. Please help!!

Re: su qeustion

On Dec 17, 2008, at 3:12 PM, Jonathan Moore wrote: I just installed FreeBSD with Gnome. And I changed the shell when I was logged ito the terminal as su root. Now when I try to log in to su it asks for a password and I get "su: /usr/bin/csh: No such file or directory" how can I change it

Re: su qeustion

On Dec 17, 2008, at 12:12 PM, Jonathan Moore wrote: I just installed FreeBSD with Gnome. And I changed the shell when I was logged ito the terminal as su root. Now when I try to log in to su it asks for a password and I get "su: /usr/bin/csh: No such file or directory" how can I change it

Re: su: not running setuid

On Tue, Oct 23, 2007 at 09:09:04PM +0100, Adam J Richardson wrote: > Christopher Cowart wrote: >> Unless you can find some local privilege escalation exploit, I'm >> thinking you're stuck. You can probably fix it in single-user mode: >> * Reboot >> * Pick single user mode from the boot menu >> * Ac

Re: su: not running setuid

Christopher Cowart wrote: Unless you can find some local privilege escalation exploit, I'm thinking you're stuck. You can probably fix it in single-user mode: * Reboot * Pick single user mode from the boot menu * Accept the default shell $ fsck -p $ mount -u / $ mount -a -t ufs $ chown root /usr/

Re: su: not running setuid

Hi, Thanks a lot!!! The fix you provided worked for me, I am able to switch from normal user to su but this I am able to do with the help of ssh login only. I am not able to login from my console. When I am trying to login from my console it is not accepting my username and password not even of

Re: su: not running setuid

Hi, No I am not able to login as root from other consoles also. I am able to ssh on this machine from other machines and is able to successfully login to this machine but from my console I am now even not able to login to this machine. It is not accepting my uname and passwd. Looks like I ma st

Re: su: not running setuid

On Mon, Oct 22, 2007 at 06:51:48PM +, Mayank Jain wrote: > Hi all, > > I have run chown -R uname:wheel . as root in the / directory. Now it is not > allowing me to log in as su. > Giving the following error > > su > su: not running setuid > > I have also tried su -l but still same error. Ca

Re: su: not running setuid

If you executed the command you claim you did, you're system permissions are really screwed up. You've changed ownership of *EVERY* file on the system to uname:wheel. My best guess is that su is trying to run as uname (setuid) and it's not getting the permissions is needs. 4th and long

Re: su: not running setuid

On Mon, 2007-10-22 at 18:51 +, Mayank Jain wrote: > Hi all, > > I have run chown -R uname:wheel . as root in the / directory. Now it is not > allowing me to log in as su. > Giving the following error > > su > su: not running setuid > > I have also tried su -l but still same error. Can any

Re: su: not running setuid

On Oct 22, 2007, at 11:51 AM, Mayank Jain wrote: I have run chown -R uname:wheel . as root in the / directory. Now it is not allowing me to log in as su. Giving the following error Ouch-- you've managed to reset the setuid/setgid bits for the entire system. You'll probably need to do a bu

Re: Su newbie question

> But that may not be the best way. You really don't want to spread > root accounts around a lot. One alternative might be setting up > sudo to allow the specific things that this other person needs to do. > sudo woul dbe the right way to do: you have fine choice on the various priviledges you

Re: Su newbie question

On Mon, May 28, 2007 at 12:58:51PM -0400, Ian Lord wrote: > Hi, > > A real dumb question today : I’ve always been the only administrator of > servers I installed so I never searched too much on the topic… > > A new employee has joined the team and he will need to administer the > servers (compil

Re: Su newbie question

Ian Lord wrote: Hi, A real dumb question today : I’ve always been the only administrator of servers I installed so I never searched too much on the topic… A new employee has joined the team and he will need to administer the servers (compile ports, etc) Usually, I do a su when I ne

Re: su to root denied?

On Wed, Dec 06, 2006 at 09:08:18PM -0600, Paul Schmehl wrote: > --On December 6, 2006 9:42:41 PM -0500 Kris Kennaway <[EMAIL PROTECTED]> > wrote: > > >On Wed, Dec 06, 2006 at 07:52:50PM -0600, john Mish III wrote: > >>I get this error message when I try to su to anything, either from root > >>or

Re: su to root denied?

--On December 6, 2006 9:42:41 PM -0500 Kris Kennaway <[EMAIL PROTECTED]> wrote: On Wed, Dec 06, 2006 at 07:52:50PM -0600, john Mish III wrote: I get this error message when I try to su to anything, either from root or to root, and I don't know why. $ su su: not running setuid Somehow your s

Re: su to root denied?

On Wed, Dec 06, 2006 at 07:52:50PM -0600, john Mish III wrote: > I get this error message when I try to su to anything, either from root or > to root, and I don't know why. > $ su > su: not running setuid Somehow your su application lost its setuid bit. Instead of blinding chmodding it you may w

Re: su problem

Martin Schweizer wrote: Hello If I su from user martin to root or from user martin to martin (for testing) I get this errors in /var/log/messages: [snip] May 9 11:33:08 merkur init: can't get /dev/console for controlling terminal: Operation not permitted May 9 11:33:38 merkur init: can't g

Re: su to root not prompting for a password

In the last episode (Apr 17), James Riendeau said: > Thanks! I didn't think it was so simple, and I feel like a lunkhead > for not thinking of that. I'm accustomed to being prompted for the > user's password when I run su, even if it is blank (I've been > spending way too much time on Mac OS X, I

Re: su to root not prompting for a password

Thanks! I didn't think it was so simple, and I feel like a lunkhead for not thinking of that. I'm accustomed to being prompted for the user's password when I run su, even if it is blank (I've been spending way too much time on Mac OS X, I guess). I must have clobbered only the root pass

RE: su to root not prompting for a password

On Monday, April 17, 2006 5:45 PM James Riendeau wrote: > > I upgraded to 6.1 RC-1 from 5.4, and when I su to root, it's not > prompting for a password. I created a new account, and it does the > same thing there. If the user is in the wheel group, it > drops to the > # prompt. If not,

Re: su to root not prompting for a password

At 09:45 AM 4/17/2006, James Riendeau wrote: I upgraded to 6.1 RC-1 from 5.4, and when I su to root, it's not prompting for a password. I created a new account, and it does the same thing there. If the user is in the wheel group, it drops to the # prompt. If not, it echos the BAD SU attempt er

Re: su: _secure_path: cannot stat .login_conf: Permission denied

Oles Hnatkevych <[EMAIL PROTECTED]> writes: > I am trying to "move" FreeBSD 6.1 installation from one hard drive to > another. I do stuff like "newfs /dev/ad1s1a" and so on, then I mount > all new partitions to some tree in /mnt, then I do simple things: > tar --one-file-system -cf - -C / .|tar xp

Re: su command & PPP

Mohsen Pahlevanzadeh wrote: on 11/04/05 at 15:58 > Dears, > I have 2 question : > 1.for dialing PPP ,Am i do compile kernel? > 2.When i run gdm,i can't use su command.When i use this command,i > recieve following text : > "su : sorrry!" > Please guide me... > Yours,Mohsen. Why don't you fix the d

Re: su command & PPP

Mohsen Pahlevanzadeh wrote: > Dears, > I have 2 question : > 1.for dialing PPP ,Am i do compile kernel? > 2.When i run gdm,i can't use su command.When i use this command,i > recieve following text : > "su : sorrry!" > Please guide me... > Yours,Mohsen. Oh - and btw, fix your time and date. --

Re: su command & PPP

Mohsen Pahlevanzadeh wrote: > Dears, > I have 2 question : > 1.for dialing PPP ,Am i do compile kernel? I don't know - I have not done PPP in years. > 2.When i run gdm,i can't use su command.When i use this command,i > recieve following text : > "su : sorrry!" Add yourself to the group wheel >

Re: su command & PPP

On 11/5/05, Mohsen Pahlevanzadeh <[EMAIL PROTECTED]> wrote: > Dears, > I have 2 question : > 1.for dialing PPP ,Am i do compile kernel? Make sure "device tun" in your kernel, use /usr/sbin/ppp, not /usr/sbin/pppd. /etc/ppp/ppp.conf - is ppp's config file "man ppp" describes ppp and ppp.conf _

Re: su command & PPP

On Sat, 5 Nov 2005 08:28 am, Mohsen Pahlevanzadeh wrote: > Dears, > I have 2 question : > 1.for dialing PPP ,Am i do compile kernel? > 2.When i run gdm,i can't use su command.When i use this > command,i recieve following text : > "su : sorrry!" This is the normal response to a user who does not ha

Re: su - does not ask for password

Teo, If you check your log files you may see something in there about passwordless accounts. :) ~Mr. Anderson --- Teo De Las Heras <[EMAIL PROTECTED]> wrote: > That's exactly why I just assumed that I had set a > password for root...I > didn't think it was possible to not have a password > set.

Re: su - does not ask for password

That's exactly why I just assumed that I had set a password for root...I didn't think it was possible to not have a password set. Teo On 10/15/05, Andrew P. <[EMAIL PROTECTED]> wrote: > > On 10/15/05, Teo De Las Heras <[EMAIL PROTECTED]> wrote: > > That worked! I thought I remembered giving root

Re: su - does not ask for password

On 10/15/05, Teo De Las Heras <[EMAIL PROTECTED]> wrote: > That worked! I thought I remembered giving root a password!? So, if > you don't have a password set, one is not asked for? > > Teo > Quite so. You should never ever leave root password blank. In fact, FreeBSD as an OS and many programs t

Re: su - does not ask for password

That worked! I thought I remembered giving root a password!? So, if you don't have a password set, one is not asked for? Teo On 10/14/05, Andrew P. <[EMAIL PROTECTED]> wrote: > > My account has a password and when > > I "su -" I go right in as root without a > > password prompt. What changed? >

Re: su - does not ask for password

> My account has a password and when > I "su -" I go right in as root without a > password prompt. What changed? > > Teo > % su # passwd Changing local password for root New Password: Retype New Password: # Now you're done. ___ freebsd-questions@freebs

Re: su - does not ask for password

Am Freitag, 14. Oktober 2005 17:48 CEST schrieb Teo De Las Heras: > I've added myself to the wheel group and can successfully su - into > root. I'm wondering though, where I make the configuration to ask for a > password when su - is called. You have to assign the superuser a password first. su wi

Re: SU Question

In the last episode (May 12), Dixit, Viraj said: > I am getting this error message when I try to logon using "su" > command through Telnet remotely. All this started when I accidentally > changed permissions, since then all permissions have been restored, > yet the same error. > % su > Password: >

Re: SU Question

On Thu, May 12, 2005 at 10:19:31AM -0700, Dixit, Viraj wrote: > Final question, I notice the rights of "su" on another system were > like this "-r-sr-xr-x". What's the rule of setting the option "s" in > the permissions. Thanks! You can set this bit (the setuid bit) with chmod. See the chmod man

RE: SU Question

Final question, I notice the rights of "su" on another system were like this "-r-sr-xr-x". What's the rule of setting the option "s" in the permissions. Thanks! VJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinf

RE: SU Question

HI Dan, I am getting this error message when I try to logon using "su" command through Telnet remotely. All this started when I accidentally changed permissions, since then all permissions have been restored, yet the same error. % su Password: su: setting user context: Operation not permitted

Re: su: illegal option -- s

Dan: Thanks, this seems to have worked. --karl --- Dan Nelson <[EMAIL PROTECTED]> wrote: > In the last episode (Apr 02), Karl Agee said: > > FreeBSD 4.11-Stable, bash 2.05. > > > > I am getting an error when I try to launch a > daemon > > script manually as root, or in > /usr/local/etc/rc.d: >

Re: su: illegal option -- s

In the last episode (Apr 02), Karl Agee said: > FreeBSD 4.11-Stable, bash 2.05. > > I am getting an error when I try to launch a daemon > script manually as root, or in /usr/local/etc/rc.d: > > -su-2.05b# /usr/local/koha/intranet/scripts/z3950daemon/z3950-daemon-launch.sh > -su-2.05b# su: illega

Re: su command problem

> On Tue, 29 Mar 2005 08:25:10 -0800 (PST), John Public <[EMAIL PROTECTED]> > wrote: > Thank you very much! I had checked the password file, > but had been focused on the mysql account. I only > just noticed that the root account was set to use > /bin/csh for it's shell. When I changed it to >

Re: su command problem

Thank you very much! I had checked the password file, but had been focused on the mysql account. I only just noticed that the root account was set to use /bin/csh for it's shell. When I changed it to /usr/local/bin/bash, suddenly everything started working. Thank you for your direction, I reall

Re: su command problem

John Public wrote: I'm apologize for being unclear. Let me try again. I have not modified the mysql-server.sh script in any way. The 'su -m mysql -c date' line is merely an example of what I used to see if 'su' is having a problem. All that line does is run the 'date' command as the mysql user.

Re: su command problem

I'm apologize for being unclear. Let me try again. I have not modified the mysql-server.sh script in any way. The 'su -m mysql -c date' line is merely an example of what I used to see if 'su' is having a problem. All that line does is run the 'date' command as the mysql user. I used this for t

Re: su command problem

>On Mon, 28 Mar 2005 11:03:23 -0800 (PST), John Public <[EMAIL PROTECTED]> wrote: > Thanks for your quick reply. In answer to your query, NP > yes, I installed mysql 4.1 from ports, and it works > just fine if I start it using mysqld_safe. However, > if I attempt to run it from > /usr/local/e

Re: su command problem

> > To whom it may concern: > > I am running into an issue using rc.conf to run > applications at startup. Specifically, nagios, and > mysql. When the system boots, it goes to a command > prompt at the stage of the boot process when those > applications would be run and then stops. If I exit >

Re: su command problem

> > I am running into an issue using rc.conf to run > applications at startup. Specifically, nagios, and > mysql. When the system boots, it goes to a command > prompt at the stage of the boot process when those > applications would be run and then stops. If I exit > out of the prompt, booting c

Re: su: Sorry

On Wed, 16 Mar 2005 14:08:05 +0100, Karol Kwiatkowski <[EMAIL PROTECTED]> wrote: > Gert Cuykens wrote: > > Why can i not su accessing the server true ssh ? > > > > $ su > > su: Sorry > > $ > > http://lists.freebsd.org/mailman/htdig/freebsd-questions/2004-November/063643.html > > Cheers, > > Karo

Re: su: Sorry

Gert Cuykens wrote: > Why can i not su accessing the server true ssh ? > > $ su > su: Sorry > $ http://lists.freebsd.org/mailman/htdig/freebsd-questions/2004-November/063643.html Cheers, Karol -- Karol Kwiatkowski ___ freebsd-questions@freebsd.or

Re: su: Sorry

On Wed, 16 Mar 2005 13:54:49 +0100, Gert Cuykens <[EMAIL PROTECTED]> wrote: > Why can i not su accessing the server true ssh ? are you in the wheel group? check out /etc/pam.d/su > > $ su > su: Sorry > $ > ___ > freebsd-questions@freebsd.org mailing l

Re: su: Sorry - 5.2.1 -

thank you for the help... I will have to wait until I get home to try it.. Thanks again.. G_ On Sat, 6 Nov 2004 17:32:42 +, Daniel Bye <[EMAIL PROTECTED]> wrote: > On Sat, Nov 06, 2004 at 11:23:44AM -0600, Gable Barber wrote: > > $ su > > su: Sorry > > $ > > In BSD, you need to be a memb

Re: su: Sorry - 5.2.1 -

On Sat, Nov 06, 2004 at 11:23:44AM -0600, Gable Barber wrote: > $ su > su: Sorry > $ In BSD, you need to be a member of group `wheel' to use su. Login as root, and edit the /etc/group file to add your username to wheel. Alternatively, use the pw command. Something like this should work: # ps u

Re: su: Sorry - 5.2.1 -

you have to be in group wheel to su. ssh barrs root login as default. On Sat, 6 Nov 2004 11:23:44 -0600, Gable Barber <[EMAIL PROTECTED]> wrote: > $ su > su: Sorry > $ > > The FAQ says to post this first : > > $ uname -a > FreeBSD tcb.garagemoderne.com 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE #0: >

Re: 'su' problem

> > > > su: Sorry. > > Are you running it as root? If so, you are probably mistyping something. > > If you are not root and trying to su to root, then your id has to be > > in the wheel group. > > I run it as normal user, and only replies like this > > $ su > su: Sorry, > $ > > What problem co

Re: 'su' problem

> > Hello list... > > When I try to run 'su' it does not run and returns a message: > > su: Sorry. > > and returns to the shell prompt... I guess it is 'cos some kind of > permission... just read the 'su' manpage and it tells about a /etc/pam.conf > but the file is not present... should I cre

Re: 'su' problem

On Fri, 16 Jul 2004 00:44:20 -0500 Miguel Cardenas <[EMAIL PROTECTED]> spake thus: > Hello list... > > When I try to run 'su' it does not run and returns a message: > > su: Sorry. > > and returns to the shell prompt... I guess it is 'cos some kind of > permission... just read the 'su' manpage

Re: Su to Root

On Sat, Mar 20, 2004 at 07:42:17PM +0100, Remko Lodder wrote: > Jez Hancock wrote: > > >On Sat, Mar 20, 2004 at 12:37:37PM -0500, Kevin Coles wrote: > > > >>I am using freebsd 5.2, which I have installed recently. I cannot seem > >>to su to root while using my normal account. > >>All I get is a m

Re: Su to Root

Jez Hancock wrote: On Sat, Mar 20, 2004 at 12:37:37PM -0500, Kevin Coles wrote: I am using freebsd 5.2, which I have installed recently. I cannot seem to su to root while using my normal account. All I get is a message saying "Sorry." Can anyone help? Try resetting the root password perhaps?

Re: Su to Root

On Sat, Mar 20, 2004 at 12:37:37PM -0500, Kevin Coles wrote: > I am using freebsd 5.2, which I have installed recently. I cannot seem > to su to root while using my normal account. > All I get is a message saying "Sorry." Can anyone help? Try resetting the root password perhaps? See here: http:

Re: Su to Root

On Sat, Mar 20, 2004 at 12:37:37PM -0500, Kevin Coles wrote: > I am using freebsd 5.2, which I have installed recently. I cannot seem > to su to root while using my normal account. > All I get is a message saying "Sorry." Can anyone help? You need to be a member of the wheel group in order to us

Re: Su to Root

Kevin Coles wrote: Hello everyone, I am using freebsd 5.2, which I have installed recently. I cannot seem to su to root while using my normal account. All I get is a message saying "Sorry." Can anyone help? Any help would be appreciated. Thanks, Kevin Coles __

Re: SU not working on fresh CVSUP

On Tue, 3 Jun 2003, Mike Loiterman wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > This is an issue for current but since I can't send to the current > mailing list from this machine I figured I'd try here first: > > Just cvsup'd to current a few hours ago. Built and installed worl

Re: su not using ~/.bash_profile

On Sat, Sep 28, 2002 at 01:48:57AM +0200, [EMAIL PROTECTED] wrote: > well, > %su - > > does, but a su from root to another user doesn't, and i'd like it to.. > I use an alias: alias su='su -l' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body

Re: su to root

On Thursday 18 July 2002 11:06 am, Brian T. Schellenberger wrote: | IMHO, "op" is far superior to "sudo." Hmm . . . come to think of it, that's a little terse. "op" is easy to configure, and it allows you give access to people not to certain commands but to certain commands *only* with certain

Re: su to root

IMHO, "op" is far superior to "sudo." On Wednesday 17 July 2002 03:04 pm, Tom Limoncelli wrote: | "Balaji, Pavan" wrote: | > I wonder what exactly this means. I don't remember seeing any option for | > creating/not-creating the wheel group while installation. | | It means "Install 'sudo' so that

  1   2   >