On 08/08/2012 11:34 AM, Brian Mathis wrote:
Capturing history files is error-prone and a very bad way to approach
this problem. You should instead look into using process accounting,
provided by the psacct package. You can read about it here:
Am 08.08.2012 23:03, schrieb m.r...@5-cent.us:
Les Mikesell wrote:
On Wed, Aug 8, 2012 at 2:56 PM, m.r...@5-cent.us wrote:
flame, but not to you, Heng Su
VCS's that let multiple people check the same object out at the same
time You're *exactly* back where you were before people were
hello,
I want to protect the history file from deleted for all users except
user 'root' can do it, is that possible?
For my server, many users can log in with root from remote through
ssh, so I can not trace which guy do wrong things. So I decide to create
new account for every users
Use remote logging to a second machine which only you have access to.
http://www.linuxjournal.com/content/creating-centralized-syslog-server
Harold
8/8/2012 12:56 PM, Heng Su wrote:
hello,
I want to protect the history file from deleted for all users except
user 'root' can do it, is
Greetings,
On Wed, Aug 8, 2012 at 10:26 PM, Heng Su ste.suh...@gmail.com wrote:
hello,
For my server, many users can log in with root from remote through
ssh, so I can not trace which guy do wrong things. So I decide to create
new account for every users and let them use 'sudo' then I can
Heng Su wrote:
hello,
I want to protect the history file from deleted for all users except
user 'root' can do it, is that possible?
For my server, many users can log in with root from remote through
ssh, so I can not trace which guy do wrong things. So I decide to create
new account
On Wed, Aug 8, 2012 at 11:56 AM, Heng Su ste.suh...@gmail.com wrote:
I want to protect the history file from deleted for all users except
user 'root' can do it, is that possible?
For my server, many users can log in with root from remote through
ssh, so I can not trace which guy do
Use sudo.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Hi mark,
Great! I think those you mentioned is exactly what I want.
Normally, I want to trace which guy got wrong things in server.
I tried the link that Harold provided find it's a good idea to
protect log files, however, I want to know is which guy type which command.
the
On 08/09/2012 01:54 AM, Les Mikesell wrote:
On Wed, Aug 8, 2012 at 11:56 AM, Heng Su ste.suh...@gmail.com wrote:
I want to protect the history file from deleted for all users except
user 'root' can do it, is that possible?
For my server, many users can log in with root from remote
Greetings,
On Wed, Aug 8, 2012 at 11:32 PM, Heng Su ste.suh...@gmail.com wrote:
this server, however, someone let say new guy overwrite wrong file. I
need to trace on it and inform him carefully.
SCMs like SVN, git etc. are exactly for such events.
You are taking backups, aren't you?
--
On 08/09/2012 02:14 AM, Rajagopal Swaminathan wrote:
Greetings,
On Wed, Aug 8, 2012 at 11:32 PM, Heng Su ste.suh...@gmail.com wrote:
this server, however, someone let say new guy overwrite wrong file. I
need to trace on it and inform him carefully.
SCMs like SVN, git etc. are exactly for
On Wed, Aug 8, 2012 at 12:56 PM, Heng Su ste.suh...@gmail.com wrote:
I want to protect the history file from deleted for all users except
user 'root' can do it, is that possible?
For my server, many users can log in with root from remote through
ssh, so I can not trace which guy do
On Wed, Aug 8, 2012 at 1:13 PM, Heng Su ste.suh...@gmail.com wrote:
No, it is not a common situation. Normally you should not let anyone
you don't trust become root. For fairly obvious reasons...
Let said if you want get low price to set up multiple application
servers and outsource
On Wed, Aug 8, 2012 at 1:23 PM, Heng Su ste.suh...@gmail.com wrote:
Normal flow is get codes from SCMs repository or do CI server, however,
you know some small company got such thing messy (my current company,
lol ^_^). Sometime you have to update only one file of the project.
Why does it
On 08/09/2012 02:46 AM, Les Mikesell wrote:
On Wed, Aug 8, 2012 at 1:23 PM, Heng Su ste.suh...@gmail.com wrote:
Normal flow is get codes from SCMs repository or do CI server, however,
you know some small company got such thing messy (my current company,
lol ^_^). Sometime you have to update
Hi Harald,
Thank you so much to guide to correct path and let me know how to
move on, learn more from you.
Indeed I am a developer not an admin, that's a good question for the
headers of my company why there is no admin to manage the server in our
company. Anyway this can not controlled by
Heng Su wrote:
On 08/09/2012 02:46 AM, Les Mikesell wrote:
On Wed, Aug 8, 2012 at 1:23 PM, Heng Su ste.suh...@gmail.com wrote:
Normal flow is get codes from SCMs repository or do CI server, however,
you know some small company got such thing messy (my current company,
lol ^_^). Sometime you
On Wed, Aug 8, 2012 at 2:07 PM, Heng Su ste.suh...@gmail.com wrote:
On 08/09/2012 02:46 AM, Les Mikesell wrote:
On Wed, Aug 8, 2012 at 1:23 PM, Heng Su ste.suh...@gmail.com wrote:
Normal flow is get codes from SCMs repository or do CI server, however,
you know some small company got such thing
On Wed, Aug 8, 2012 at 2:56 PM, m.r...@5-cent.us wrote:
flame, but not to you, Heng Su
VCS's that let multiple people check the same object out at the same
time You're *exactly* back where you were before people were using
VCSs.
/flame
Errr, what? No sensible VCS forces you to wait
Les Mikesell wrote:
On Wed, Aug 8, 2012 at 2:56 PM, m.r...@5-cent.us wrote:
flame, but not to you, Heng Su
VCS's that let multiple people check the same object out at the same
time You're *exactly* back where you were before people were using
VCSs.
/flame
Errr, what? No sensible VCS
On Wed, Aug 8, 2012 at 4:03 PM, m.r...@5-cent.us wrote:
Errr, what? No sensible VCS forces you to wait for someone else to
finish their portion of the work.
You're wrong. I've worked in small and large teams, and *ALWAYS* we
checked out with locks. If two people need to work on one file,
Les Mikesell wrote:
On Wed, Aug 8, 2012 at 4:03 PM, m.r...@5-cent.us wrote:
Errr, what? No sensible VCS forces you to wait for someone else to
finish their portion of the work.
You're wrong. I've worked in small and large teams, and *ALWAYS* we
checked out with locks. If two people need
On Wed, Aug 8, 2012 at 4:33 PM, m.r...@5-cent.us wrote:
If you want to force your team to wait for your change, fine - and
sometimes it is even a good idea, but the tool should not make that
decision for you.
Yes, I do want to force them to wait for what one person's working on -
it's not
On Wed, 8 Aug 2012 21:00:59 +0300
Mihamina Rakotomandimby miham...@rktmb.org wrote:
Use sudo.
Weak! Real fascists use sudosh!
Rui
ps: I'm sure there are some fascists who are more fascist so feel free
to point out even better options ;)
___
CentOS
25 matches
Mail list logo
