We have SCO 5.0.5 and can't log into system as "root". The system indicates the password is incorrect. No one knows what happened.
How can we resolve this issue.. Are there files we can restore from backup...?
Any suggestions would be appreciated.
Thank you.. (2 Replies)
Hello
I have a question.
I have a box with Aix 5.3 but I want to disable root access direct from any terminal or console. I mean If I want to login to 10.10.10.10
login:root
password *********
Root access is not permited
Which file I have to edit. to the users first login with... (4 Replies)
hi
i am new to unix and i have abig task. i have to \run particular commands having root privileges from a non root user. i know sudo is one of the way but i need sum other approach kindly help
Thanks (5 Replies)
Hello, I have two old Solaris machines
$ uname -a
SunOS unknown 5.8 Generic_117350-39 sun4u sparc SUNW,UltraAX-e2
unfortunately, it has been so long ago that i have used these that the root password has left my head...
i can log into one of the machine as a normal user, but am unable to... (4 Replies)
Hi ,
I have a Mac OS X Lion mac book pro. I have a hard drive which I have partitioned in two
(a) OSX Partition - Mac OS Extended Journaled format. Mount point: /
(b) Data Partition - Windows NT Filesystem format. Mount point: /Volumes/Data
I need to access the NTFS partition (I have a... (6 Replies)
normally I
rsync -haPE source destination
What I want to do is take a old ~ directory from an external drive and have it ONLY update missing files NOT replace existing files. excluding ~/library
any help would be great. (3 Replies)
Currently in my system Red Hat is installed. And Many user connect to my machine via SSH Techia Terminal.
I want to give some users a root level access.
Can anyone please help me how to make it possible. I too searched on the Google but didn't find the correct way
Regards
ADI (4 Replies)
I access over 100 SUSE SLES servers as root from my admin server, via ssh sessions using ssh keys, so I don't have to enter a password. My SUSE Admin server is setup in the following manner:
1) Remote root access is turned off in the sshd_config file.
2) I am the only user of this admin... (6 Replies)
We are having a little problem on a server. We want that some users should be able to do e.g. sudo and become root, but with the restriction that the user can't change root password. That is, a guarantee that we still can login to that server and become root no matter of what the other users will... (2 Replies)
Discussion started by: 244an
2 Replies
LEARN ABOUT CENTOS
git-reflog
GIT-REFLOG(1) Git Manual GIT-REFLOG(1)NAME
git-reflog - Manage reflog information
SYNOPSIS
git reflog <subcommand> <options>
DESCRIPTION
The command takes various subcommands, and different options depending on the subcommand:
git reflog expire [--dry-run] [--stale-fix] [--verbose]
[--expire=<time>] [--expire-unreachable=<time>] [--all] <refs>...
git reflog delete ref@{specifier}...
git reflog [show] [log-options] [<ref>]
Reflog is a mechanism to record when the tip of branches are updated. This command is to manage the information recorded in it.
The subcommand "expire" is used to prune older reflog entries. Entries older than expire time, or entries older than expire-unreachable
time and not reachable from the current tip, are removed from the reflog. This is typically not used directly by the end users -- instead,
see git-gc(1).
The subcommand "show" (which is also the default, in the absence of any subcommands) will take all the normal log options, and show the log
of the reference provided in the command-line (or HEAD, by default). The reflog will cover all recent actions (HEAD reflog records branch
switching as well). It is an alias for git log -g --abbrev-commit --pretty=oneline; see git-log(1).
The reflog is useful in various Git commands, to specify the old value of a reference. For example, HEAD@{2} means "where HEAD used to be
two moves ago", master@{one.week.ago} means "where master used to point to one week ago", and so on. See gitrevisions(7) for more details.
To delete single entries from the reflog, use the subcommand "delete" and specify the exact entry (e.g. "git reflog delete master@{2}").
OPTIONS --stale-fix
This revamps the logic -- the definition of "broken commit" becomes: a commit that is not reachable from any of the refs and there is a
missing object among the commit, tree, or blob objects reachable from it that is not reachable from any of the refs.
This computation involves traversing all the reachable objects, i.e. it has the same cost as git prune. Fortunately, once this is run,
we should not have to ever worry about missing objects, because the current prune and pack-objects know about reflogs and protect
objects referred by them.
--expire=<time>
Entries older than this time are pruned. Without the option it is taken from configuration gc.reflogExpire, which in turn defaults to
90 days.
--expire-unreachable=<time>
Entries older than this time and not reachable from the current tip of the branch are pruned. Without the option it is taken from
configuration gc.reflogExpireUnreachable, which in turn defaults to 30 days.
--all
Instead of listing <refs> explicitly, prune all refs.
--updateref
Update the ref with the sha1 of the top reflog entry (i.e. <ref>@{0}) after expiring or deleting.
--rewrite
While expiring or deleting, adjust each reflog entry to ensure that the old sha1 field points to the new sha1 field of the previous
entry.
--verbose
Print extra information on screen.
GIT
Part of the git(1) suite
Git 1.8.3.1 06/10/2014 GIT-REFLOG(1)