Topic: signal-event & db: command not found

[dkvnk]

help,

i've been trying to enable repo8 on my sme server 9 by instructions on http://wiki.contribs.org/SME9.0_Contribs_QA#Setup

but signal-event & db command is always return :command not found

[guest22]

Hi and welcome,

your issue indicates that you have done some more then just follow the documentation. You path environment is likely not correct.


That by itself will remain a problem.


Tell us a bit about the history of you installation pls.

[dkvnk]

Hi, Thanks for reply

This I have done

Code: [Select]

[root@server-sme1 e-smith]# db yum_repositories show sme8contribs
bash: db: command not found
[root@server-sme1 e-smith]# db yum_repositories set sme8contribs repository \
> Name 'SME 8 - contribs' \
> MirrorList 'http://mirrorlist.contribs.org/mirrorlist/smecontribs-8' \
> GPGCheck yes \
> Visible no \
> status disabled
bash: db: command not found
[root@server-sme1 e-smith]# signal-event yum-modify
bash: signal-event: command not found


[guest22]

Again, your path variable is not correct. The firts command you give shows that already. You need to fix that.


What have you done _before_ trying to enable this repo. What is the history of this server and what contribs did you install?

[dkvnk]

its a fresh install sme 9 & i've hasn't install nothing,

i'll figure it and try search google, still learn sme.. its my first install and i dont know what i must change about path variable

thanks.

[guest22]

something must have gone wrong somewhere....


Anyway, to get you going, pls use '/sbin/e-smith/db' instead of just 'db'

[Stefano]

something must have gone wrong somewhere....


Anyway, to get you going, pls use '/sbin/e-smith/db' instead of just 'db'

I agree..
this should be investigated as it should not happen

[DanB35]

How are you getting to the root prompt?  Are you logging in directly as root, or are you logging in as another user and then using su?  If you're using su, you need to do 'su -'. otherwise it won't read root's environment, which will result in what you're seeing here.

[guest22]

How are you getting to the root prompt?  Are you logging in directly as root, or are you logging in as another user and then using su?  If you're using su, you need to do 'su -'. otherwise it won't read root's environment, which will result in what you're seeing here.

This tip is going to the quarter finals!

[Stefano]

we should/could use motd file (/etc/motd) and the "PrintMotd yes" flag in /etc/sshd/sshd_config to give some useful info to user login in console

[guest22]

we should/could use motd file (/etc/motd) and the "PrintMotd yes" flag in /etc/sshd/sshd_config to give some useful info to user login in console

Agree, can you open a new bug for this pls?

[ReetP]

we should/could use motd file (/etc/motd) and the "PrintMotd yes" flag in /etc/sshd/sshd_config to give some useful info to user login in console

And if you are a really lucky boy and tell me roughly how to do it I'll do you a patch

[Stefano]

give me some time, I'll post in bugzilla, stay tuned

[dkvnk]

something must have gone wrong somewhere....


Anyway, to get you going, pls use '/sbin/e-smith/db' instead of just 'db'

thanks, its work... but i will always use by path /sbin/e-simth/.. instead simple command

How are you getting to the root prompt?  Are you logging in directly as root, or are you logging in as another user and then using su?  If you're using su, you need to do 'su -'. otherwise it won't read root's environment, which will result in what you're seeing here.

Hi.. i've try without 'su' before, and when i try with su permision its same
every command must type with path

going back to sme 8, i'm curious and then fresh install.. again the command must type with patch /sbin/e-smith, but installing addon is easy than sme 9 (for me  )

[Stefano]

no..

if you login with a "normal" user, you must use

Code: [Select]

su -

not only

Code: [Select]

su

try and let us know

[dkvnk]

no..

if you login with a "normal" user, you must use

Code: [Select]

su -

not only

Code: [Select]

su

try and let us know

Hi

Great! it work
Thanks

[Stefano]

NFR done:

http://bugs.contribs.org/show_bug.cgi?id=8939

[stephdl]

we should/could use motd file (/etc/motd) and the "PrintMotd yes" flag in /etc/sshd/sshd_config to give some useful info to user login in console

The motd has been desactivated for security reasons some years ago.....in fact they didn't want to say to the guy who is doing a hack what is the system where he is.

Of course for good reasons that could be reactivated.....for example ask about involvment or money to the inactive community

[Stefano]

"they" who?

motd is shown only when you are logged in.. and if you're already in, telling or not you what kind of system is under your finger doesn't make much difference IMHO

[stephdl]

'They' are people with permissions to push to cvs and release  rpms

[Stefano]

is there any reference in bugzilla? during NFR creation "motd" input  in the sbj filed did not give any result

[Stefano]

in any case, things can change

[stephdl]

read http://bugs.contribs.org/show_bug.cgi?id=7898#c7

[Stefano]

I can't see any reason, only a question (from Ian) to Charlie and Shad.. but no answer.

IMO (I repeat myself), showing system's info and/or any other kind of info with motd is a nosense problem in a security vision.. you see it when you're in, you already have all in your hands..

and, repeating myself again, things can change.. I'm quite sure that this kind of feature is harmless for security and more user-friendly..

[stephdl]

why not, my patches are there if you want to use them as template

[Stefano]

already done my job, see the referenced bug (you'd see something "familiar", if you know what I mean )

http://bugs.contribs.org/show_bug.cgi?id=8939

[Stefano]

we could/should merge the NFRs.. but we should also avoid to have a too long message