On Apr 14, 2022, at 20:49, Jonathan Billings wrote:
>
> Anyway, storing passwords is a terrible idea, even worse a history of old
> passwords. At best you store hashes.
Now that I have said that, if you are using OpenLDAP as an authentication
source (and not jus
On Apr 11, 2022, at 14:16, Kaushal Shriyan wrote:
>
> Is there a way to retrieve the OpenLDAP password history list using openldap
> utilities?
> For example to get the history of passwords which a user has used and the
> timestamp associated with it when the password ha
On Mon, Apr 11, 2022 at 11:45 PM Kaushal Shriyan
wrote:
> Hi,
>
> Is there a way to retrieve the OpenLDAP password history list
> using openldap utilities?
> For example to get the history of passwords which a user has used and the
> timestamp associated with it when the
Hi,
Is there a way to retrieve the OpenLDAP password history list
using openldap utilities?
For example to get the history of passwords which a user has used and the
timestamp associated with it when the password has been resetted.
Please guide me. Thanks in advance.
Best Regards,
Kaushal
On 11/12/21 04:40, Tom R (Milwaukee WI) wrote:
On Thu 11/11/21 23:37 -0800 Community support (Sam) for Fedora users wrote:
On 11/11/21 15:13, Tom R (Milwaukee WI) wrote:
Is it safe to run
$ dnf history rollback 148
There's no way that will work.
Wow, thanks!
Rollback generally
edora34
>> (i.e. go from fedora32 to fedora34). I'm happy to upgrade to fedora34.
>
>My understanding of the previous history is that it that the upgrade was
>successful, but for some reason it was having trouble booting.
Yes/agreed, thanks for correcting me.
>You booted the
of the previous history is that it that the upgrade was
successful, but for some reason it was having trouble booting. You
booted the F32 kernel, which worked, but you are still running F33.
Here's what my vps provider suggested I do:
# boot into fedora32, as root:
This is not a correct
be doing some cleanup first: http://sprunge.us/Cyhmq4
Is it safe to run
$ dnf history rollback 148
?
--
thanks!
On Mon 11/8/21 9:01 -0600 Tom R wrote:
>My notes: https://zq3q.org/fp/fed32-33ug-boothang.htm
>
>--
>thanks,
>Tom | Milwaukee WI
>
>Snipped, markdown v
On 10/28/20 4:38 AM, Michael Schwendt wrote:
> This is with default Fedora 33 Workstation x86_64.
>
> Firefox > History > Clear Recent History > Time range to clear
>
> The combobox can be clicked to show the drop-down list, but none of the
> shown items can be selecte
This is with default Fedora 33 Workstation x86_64.
Firefox > History > Clear Recent History > Time range to clear
The combobox can be clicked to show the drop-down list, but none of the
shown items can be selected with a mouse-click. Using cursor keys is the
workaround.
Can anyone
Il giorno mar, 20/11/2018 alle 18.37 +0100, Dario Lesca ha scritto:
> Yes, thanks, also this can be a workaround.
>
> But i can think also for other people, if in case this annoying
> problem also affects other people.
>
> Then, if this is the only solution, it's bette I fill a bug in order
> to
Il giorno mar, 20/11/2018 alle 10.11 -0700, Joe Zeff ha scritto:
> Try adding this line to ~/.bashrc:
> alias reboot='exec reboot'
Yes, thanks, also this can be a workaround.
But i can think also for other people, if in case this annoying problem
also affects other people.
Then, if this is the
On 11/20/2018 10:03 AM, Dario Lesca wrote:
Ok, thank, this can be a possible solution
but it will be difficult to avoid the habit of writing only "reboot" ...
to lose last history is very annoyng
Try adding this line to ~/.bashrc:
alias reboot='e
"reboot"
... to lose last history is very annoyng
Why this kind of problem occur only some time?
Has anyone had this kind of problem?
I must fill a bug?
IMHO:
Seem this problem occur only on Fedora Server
On Centos 7 this kind of problem has never happened (to me).
Thanks
--
Dario
On 11/20/18 4:50 AM, Dario Lesca wrote:
How to I get rid on this (my?) issue ?
Use "exec reboot" instead of "reboot". Close all of your other active
shells before you do.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send
my shell pid and nothing happen.
I have try to kill $PPID (my parent process id "sshd: root@pts/0") and
logout + history saved is happen
then, systemd send SIGTERM to all process, and when sshd get it, close
the shell ... how to close it if SIGTERM is ignored from it?
when the system goes do
On Mon, Nov 19, 2018 at 12:00 PM stan wrote:
> On Mon, 19 Nov 2018 17:11:32 +0100 Dario Lesca wrote:
> > Fedora server 29 minimal fresh install.
> >
> > If I restart server with "reboot" the last history of working shell is
> > not saved.
> >
On Mon, 19 Nov 2018 17:11:32 +0100
Dario Lesca wrote:
> Fedora server 29 minimal fresh install.
>
> If I restart server with "reboot" the last history of working shell is
> not saved.
> Is something missing that I should install?
That would seem to be a systemd e
Fedora server 29 minimal fresh install.
If I restart server with "reboot" the last history of working shell is
not saved.
I must remember to do "history -a" to store last commands history
If I do logout the history is correctly stored.
With Centos7 minimal fresh inst
Ed Greshko wrote:
> On Fri, Jun 15, 2018, 18:46 Patrick O'Callaghan
> wrote:
>
>> On Fri, 2018-06-15 at 18:01 +0800, Ed Greshko wrote:
>>> [egreshko@meimei ~]$ rpm -qa pulse*
>>> pulseaudio-11.1-18.fc28.1.x86_64
>>> pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
>>>
On Fri, Jun 15, 2018, 18:46 Patrick O'Callaghan
wrote:
> On Fri, 2018-06-15 at 18:01 +0800, Ed Greshko wrote:
> > On 06/15/18 13:44, Todd Zullinger wrote:
> > > Tim via users wrote:
> > > > Allegedly, on or about 14 June 2018, Todd Zullinger sent:
> > > > > To be fair, I don't think the rpm man
On Fri, 2018-06-15 at 18:01 +0800, Ed Greshko wrote:
> On 06/15/18 13:44, Todd Zullinger wrote:
> > Tim via users wrote:
> > > Allegedly, on or about 14 June 2018, Todd Zullinger sent:
> > > > To be fair, I don't think the rpm man page documents its
> > > > wildcard support. If it does, I'm
On 06/15/18 13:44, Todd Zullinger wrote:
> Tim via users wrote:
>> Allegedly, on or about 14 June 2018, Todd Zullinger sent:
>>> To be fair, I don't think the rpm man page documents its
>>> wildcard support. If it does, I'm looking past it.
>> I've always successfully done things like this:
>>
>>
On Fri, 2018-06-15 at 01:44 -0400, Todd Zullinger wrote:
> Tim via users wrote:
> > Allegedly, on or about 14 June 2018, Todd Zullinger sent:
> > > To be fair, I don't think the rpm man page documents its
> > > wildcard support. If it does, I'm looking past it.
> >
> > I've always successfully
Tim via users wrote:
> Allegedly, on or about 14 June 2018, Todd Zullinger sent:
>> To be fair, I don't think the rpm man page documents its
>> wildcard support. If it does, I'm looking past it.
>
> I've always successfully done things like this:
>
> rpm -qa \*pulse\*
>
> More through force of
Allegedly, on or about 14 June 2018, Todd Zullinger sent:
> To be fair, I don't think the rpm man page documents its
> wildcard support. If it does, I'm looking past it.
I've always successfully done things like this:
rpm -qa \*pulse\*
More through force of habit, than any hard knowledge.
--
te:
>> > On 14 June 2018 at 14:27, Robert Moskowitz > <mailto:r...@htt-consult.com>> wrote:
>> >> I want to get history for all the pulseaudio components (to
>> update my
>> >> audacity bug report at rpmfusion).
>> >>
&g
Robert Moskowitz wrote:
> Ah, I left off the 'list' portion of your command
>
> # dnf history list pulseaudio*
> ID | Command line | Date and time| Action(s) |
> Altered
> ---
t;>
>> # rpm -qa | grep pulseaudio
>
> But that does not give me the update history. Going to have to pipe this
> output into something else
>
> # rpm -qa | grep pulseaudio
> pulseaudio-module-bluetooth-11.1-18.fc28.1.x86_64
> pulseaudio-module-x11-11.1-18.fc28.
.
which has nothing to do with "history".
If, as the OP suggests, he wishes to know the history of when packages named
pulseaudio* were updated he may run into a problem if he wasn't consistent in
the
apps used to perform updates. First of all, rpm doesn't keep a history of
updat
On 06/14/2018 09:57 AM, Richard Shaw wrote:
On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz <mailto:r...@htt-consult.com>> wrote:
On 06/14/2018 09:08 AM, Ahmad Samir wrote:
> On 14 June 2018 at 14:27, Robert Moskowitz mailto:r...@htt-consult.com>> wrote:
>&g
On 06/14/18 22:23, Tony Nelson wrote:
> That is not what he means. Would one of you please look at the RPM
> man page?
Sure
--last Orders the package listing by install time such that the latest
packages are at the top.
which has nothing to do with &q
Tony Nelson wrote:
> That is not what he means. Would one of you please look
> at the RPM man page?
To be fair, I don't think the rpm man page documents its
wildcard support. If it does, I'm looking past it.
--
Todd
~~
From
Richard Shaw wrote:
> On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz
> wrote:
>
>>
>> On 06/14/2018 09:08 AM, Ahmad Samir wrote:
>>> FWIW, to match using a wildcard you'd have to use `rpm -qa pulseaudio*`.
>>
>> Don't think so:
>>
>> # `rpm -qa pulseaudio*`
>> bash:
On 18-06-14 09:57:33, Richard Shaw wrote:
On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz
wrote:
>
> On 06/14/2018 09:08 AM, Ahmad Samir wrote:
> > On 14 June 2018 at 14:27, Robert Moskowitz
wrote:
> >> I want to get history for all the pulseaudio components (to
upd
On Thu, Jun 14, 2018 at 8:55 AM Robert Moskowitz
wrote:
>
> On 06/14/2018 09:08 AM, Ahmad Samir wrote:
> > On 14 June 2018 at 14:27, Robert Moskowitz wrote:
> >> I want to get history for all the pulseaudio components (to update my
> >> audacity bug report at
On 06/14/2018 09:08 AM, Ahmad Samir wrote:
On 14 June 2018 at 14:27, Robert Moskowitz wrote:
I want to get history for all the pulseaudio components (to update my
audacity bug report at rpmfusion).
#rpm -q pulseaudio --last
produces
pulseaudio-11.1-18.fc28.1.x86_64 Thu 24 May
On 14 June 2018 at 14:27, Robert Moskowitz wrote:
> I want to get history for all the pulseaudio components (to update my
> audacity bug report at rpmfusion).
>
> #rpm -q pulseaudio --last
>
> produces
>
> pulseaudio-11.1-18.fc28.1.x86_64 Thu 24 Ma
On 06/14/18 20:32, Richard Shaw wrote:
> On Thu, Jun 14, 2018 at 7:28 AM Robert Moskowitz <mailto:r...@htt-consult.com>> wrote:
>
> I want to get history for all the pulseaudio components (to update my
> audacity bug report at rpmfusion).
>
> #rpm -q pulseau
On Thu, Jun 14, 2018 at 7:28 AM Robert Moskowitz
wrote:
> I want to get history for all the pulseaudio components (to update my
> audacity bug report at rpmfusion).
>
> #rpm -q pulseaudio --last
>
> produces
>
> pulseaudio-11.1-18.fc28.1.x86_64 Thu 24 Ma
I want to get history for all the pulseaudio components (to update my
audacity bug report at rpmfusion).
#rpm -q pulseaudio --last
produces
pulseaudio-11.1-18.fc28.1.x86_64 Thu 24 May 2018 09:59:34
PM EDT
but
# rpm -q pulseaudio* --last
results in:
package
2016-06-01 1:18 GMT-06:00 Maurizio Marini <mau...@datalogica.com>:
> Hello
> by some days (2 weeks or something like that)
> the notify popup that warn me that some updates are ready to be applied, does
> show me a very long history of updates needed by my system, many lines a
> The most obvious response is: Install the updates waiting to be
> installed.
yes, of course I do, but that popup is a finger in my eye!
> But do you mean that you're getting notifications about updates that
> have already been installed?
Yes, I get a very large popup, with all the
On Wed, 2016-06-01 at 09:18 +0200, Maurizio Marini wrote:
> by some days (2 weeks or something like that) the notify popup that
> warn me that some updates are ready to be applied, does show me a very
> long history of updates needed by my system, many lines are
> replicated, I have
Hello
by some days (2 weeks or something like that)
the notify popup that warn me that some updates are ready to be applied, does
show me a very long history of updates needed by my system, many lines are
replicated, I have a 15" screen and now it fills up all screen vertically
It is boring
> From: "Michael Schwendt" <mschwe...@gmail.com>
>
> On Wed, 21 Oct 2015 23:44:53 +0200, Antonio M wrote:
>
> > when I try to revert to a previous history I get an error...what does it
> > mean??
> >
> > # dnf history undo 125
>
> >
On 10/24/2015 08:20 PM, Michael Schwendt wrote:
> On Sat, 24 Oct 2015 20:05:52 +0800, Ed Greshko wrote:
>
>> The only time "undo" seems relevant is if you're working with
>> updates-testing repo.
> It cannot be generalised like that. Installing from _any_ repo, such
> as updates-testing, may
On 10/24/2015 08:02 PM, Michael Schwendt wrote:
> On Fri, 23 Oct 2015 11:30:55 +1030, Tim wrote:
>
>> Tim:
Makes a nonsense of having any downgrade/undo options then...
> Even the very latest install transaction cannot be undone, because it
> included an update, too:
>
> Undoing transaction
On Fri, 23 Oct 2015 11:30:55 +1030, Tim wrote:
> Tim:
> >> Makes a nonsense of having any downgrade/undo options then...
Even the very latest install transaction cannot be undone, because it
included an update, too:
Undoing transaction 49, from Sat Oct 24 13:56:18 2015
Install
On Sat, 24 Oct 2015 20:05:52 +0800, Ed Greshko wrote:
> The only time "undo" seems relevant is if you're working with
> updates-testing repo.
It cannot be generalised like that. Installing from _any_ repo, such
as updates-testing, may lead to upgrading something that cannot be
downgraded again
On Thu, 22 Oct 2015 12:02:07 +1030, Tim wrote:
> > You can only downgrade to packages, which are still available in
> > the repos. Unfortunately, when an update is released, it replaces
> > the previous update in the repo.
>
> Makes a nonsense of having any downgrade/undo options then...
True.
profiles would change in
a non-compatible way.
There were a few bookmarks that I wanted to retrieve, at the very least,
now I've got to do it the hard way. What's probably going to more
difficult is that I wanted to look through the history to find something
I'd looked at a few days ago, that I couldn
when I try to revert to a previous history I get an error...what does it
mean??
# dnf history undo 125
Last metadata expiration check performed 2:10:34 ago on Wed Oct 21 21:26:09
2015.
Undoing transaction 125, from Tue Oct 20 22:59:17 2015
Aggiornato clutter-gst3-3.0.12-1.fc22.x86_64
@updates
On Wed, 21 Oct 2015 23:44:53 +0200, Antonio M wrote:
> when I try to revert to a previous history I get an error...what does it
> mean??
>
> # dnf history undo 125
> @updates
> Nessun pacchetto sssd-ipa-0:1.13.0-4.fc22.x86_64 disponibile.
> Errore: An operation cannot be
Allegedly, on or about 22 October 2015, Michael Schwendt sent:
> You can only downgrade to packages, which are still available in
> the repos. Unfortunately, when an update is released, it replaces
> the previous update in the repo.
Makes a nonsense of having any downgrade/undo options then...
On Thu, 22 Oct 2015 01:05:20 +0200
Michael Schwendt <mschwe...@gmail.com> wrote:
> On Wed, 21 Oct 2015 23:44:53 +0200, Antonio M wrote:
>
> > when I try to revert to a previous history I get an error...what
> > does it mean??
> >
> > # dnf history undo 125
On 07/11/2015 11:00 AM, Kevin Fenzi wrote:
On Fri, 10 Jul 2015 20:52:31 -0600
jd1008 jd1...@gmail.com wrote:
Guys! No.
I mean first release according a wicki, was dubbed by RH as 0.8
not 8.0 back in 1993???
Which wiki?
I don't recall ever hearing about 0.8/0.9 versions...
kevin
On Fri, 10 Jul 2015 20:52:31 -0600
jd1008 jd1...@gmail.com wrote:
Guys! No.
I mean first release according a wicki, was dubbed by RH as 0.8
not 8.0 back in 1993???
Which wiki?
I don't recall ever hearing about 0.8/0.9 versions...
kevin
pgp5IuK1l03hh.pgp
Description: OpenPGP digital
On 07/10/2015 07:52 PM, jd1008 wrote:
I mean first release according a wicki, was dubbed by RH as 0.8
not 8.0 back in 1993???
As far as I know, there's no remaining archive of the original beta
releases of Red Hat Linux.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or
On 07/11/2015 06:59 PM, Gordon Messmer wrote:
On 07/10/2015 07:52 PM, jd1008 wrote:
I mean first release according a wicki, was dubbed by RH as 0.8
not 8.0 back in 1993???
As far as I know, there's no remaining archive of the original beta
releases of Red Hat Linux.
Sigh!! :(
I enjoy
That was Halloween. I believe that FC1 came out after RH9 and RHEL 3 was
based on it.
On Jul 10, 2015 10:52 PM, jd1008 jd1...@gmail.com wrote:
On 07/10/2015 07:14 PM, Fred Smith wrote:
On Fri, Jul 10, 2015 at 02:01:31PM -0600, jd1008 wrote:
On 07/10/2015 01:57 PM, Kevin Fenzi wrote:
On
On Fri, Jul 10, 2015 at 02:01:31PM -0600, jd1008 wrote:
On 07/10/2015 01:57 PM, Kevin Fenzi wrote:
On Fri, 10 Jul 2015 13:45:57 -0600
jd1008 jd1...@gmail.com wrote:
On 07/10/2015 01:32 PM, Fulko Hew wrote:
On Fri, Jul 10, 2015 at 3:26 PM, jd1008 jd1...@gmail.com wrote:
What RH
On 07/10/2015 07:14 PM, Fred Smith wrote:
On Fri, Jul 10, 2015 at 02:01:31PM -0600, jd1008 wrote:
On 07/10/2015 01:57 PM, Kevin Fenzi wrote:
On Fri, 10 Jul 2015 13:45:57 -0600
jd1008 jd1...@gmail.com wrote:
On 07/10/2015 01:32 PM, Fulko Hew wrote:
On Fri, Jul 10, 2015 at 3:26 PM, jd1008
On 07/10/2015 01:57 PM, Kevin Fenzi wrote:
On Fri, 10 Jul 2015 13:45:57 -0600
jd1008 jd1...@gmail.com wrote:
On 07/10/2015 01:32 PM, Fulko Hew wrote:
On Fri, Jul 10, 2015 at 3:26 PM, jd1008 jd1...@gmail.com wrote:
What RH release was FC1 based on?
Try this entry in Wikipedia:
On Fri, Jul 10, 2015 at 3:26 PM, jd1008 jd1...@gmail.com wrote:
What RH release was FC1 based on?
Try this entry in Wikipedia:
https://en.wikipedia.org/wiki/List_of_Fedora_releases#Fedora_Core_1.E2.80.934
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription
On Fri, 10 Jul 2015 13:45:57 -0600
jd1008 jd1...@gmail.com wrote:
On 07/10/2015 01:32 PM, Fulko Hew wrote:
On Fri, Jul 10, 2015 at 3:26 PM, jd1008 jd1...@gmail.com wrote:
What RH release was FC1 based on?
Try this entry in Wikipedia:
What RH release was FC1 based on?
Thanx!
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines:
seems fine except that the output of yum history
info X (X is the update transcaction) is a bit strange:
..
Scriptlet output:
1 warning: /etc/cups/cups-browsed.conf created as
/etc/cups/cups-browsed.conf.rpmnew
2
3 1k
4 2k
5 3k
6 4k
7 5k
8 6k
..
93 91k
94 92k
95 93k
96 94k
97 95k
98 96k
the transcaction is
done and did a forced shutdown.
I rebooted and everything seems fine except that the output of yum
history info X (X is the update transcaction) is a bit strange:
..
Scriptlet output:
1 warning: /etc/cups/cups-browsed.conf created as
/etc/cups/cups-browsed.conf.rpmnew
2
3 1k
4
is done and did a forced shutdown.
I rebooted and everything seems fine except that the output of yum
history info X (X is the update transcaction) is a bit strange:
..
Scriptlet output:
1 warning: /etc/cups/cups-browsed.conf created as
/etc/cups/cups-browsed.conf.rpmnew
2
3 1k
4 2k
5 3k
splash screen took over the screen at some point and I
cannot switch to any other tty. So I waited until I believe the
transcaction is done and did a forced shutdown.
I rebooted and everything seems fine except that the output of yum
history info X (X is the update transcaction) is a bit
Hi,
I've just installed f20 and can't figure out why the gnome-terminal
scroll history doesn't work. I've enabled both scroll on output and
scroll on keystroke in the Scrolling tab, but there is still no
scroll history.
What am I missing?
Thanks,
Alex
--
users mailing list
users
We have passwordHistory enabled on our directory. When a user tries to
change his own password to a value already in his personal password
history, it prevents him from (re)setting that same password, which is
desired.
However, I'm working on a password synchronization service that will
always
-build-day
Aug 20 18:54:01 Updated: firefox-23.0.1-1.fc18.x86_64
OK, thanks Harald, 'Edit Preferences Privacy History custom
settings Clear history when FF closes' was ticked. No idea how.
if you open about:config and enter 'history' or 'shutdown' in Find: bar,
you will/should see
here, installed it at koji-build-day
Aug 20 18:54:01 Updated: firefox-23.0.1-1.fc18.x86_64
OK, thanks Harald, 'Edit Preferences Privacy History custom
settings Clear history when FF closes' was ticked. No idea how.
if you open about:config and enter 'history' or 'shutdown' in Find: bar
On 09/02/2013 05:50 AM, John Pilkington wrote:
On 02/09/13 10:38, g wrote:
if you open about:config and enter 'history' or 'shutdown' in Find: bar,
you will/should see that 'default' is 'true'.
privacy.clearOnShutdown.history;true
It shows the status (for /everything
Am 31.08.2013 16:51, schrieb John Pilkington:
Installed yesterday from fedora-updates-testing. Is it just me? Is it
recoverable? Should this go to Bugzilla?
unconfirmed here, installed it at koji-build-day
Aug 20 18:54:01 Updated: firefox-23.0.1-1.fc18.x86_64
signature.asc
Description:
.fc18.x86_64
OK, thanks Harald, 'Edit Preferences Privacy History custom
settings Clear history when FF closes' was ticked. No idea how.
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo
Installed yesterday from fedora-updates-testing. Is it just me? Is it
recoverable? Should this go to Bugzilla?
John P
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of
On 10/17/2012 12:06 AM, Mark LaPierre wrote:
On 10/16/2012 02:52 AM, Tiziana Manfroni wrote:
Hi, I have some users that delete .history file (in tcsh shell), so I
can't see their commands.
Can I disable the command unset history?
If it is not possible, what can I do?
Thanks in advance
On 16/10/12 11:03, Bryn M. Reeves wrote:
On 10/16/2012 07:52 AM, Tiziana Manfroni wrote:
Hi, I have some users that delete .history file (in tcsh shell), so I
can't see their commands.
Can I disable the command unset history?
If it is not possible, what can I do?
You can't really prevent
involved in mankind; and
therefore never send to know for whom the bell tolls; it tolls for thee.
-Original Message-
From: Alan Cox a...@lxorguk.ukuu.org.uk
Date: Tue, 16 Oct 2012 15:50:13
To: users@lists.fedoraproject.org
Cc: redwo...@gmail.com
Subject: Re: how to disable unset HISTORY
You
Hi, I have some users that delete .history file (in tcsh shell), so I
can't see their commands.
Can I disable the command unset history?
If it is not possible, what can I do?
Thanks in advance
Tiziana
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change
On 10/16/2012 07:52 AM, Tiziana Manfroni wrote:
Hi, I have some users that delete .history file (in tcsh shell), so I
can't see their commands.
Can I disable the command unset history?
If it is not possible, what can I do?
You can't really prevent a user from altering their environment (it's
Recent versions of bash can also be compiled with syslog support by
defining SYSLOG_HISTORY but if your users are hooked on tcsh that
probably won't help (I don't think it's enabled in the Fedora builds
anyway).
And any remotely malicious intending user will simply go into vi, set the
vi
Am 16.10.2012 08:52, schrieb Tiziana Manfroni:
Hi, I have some users that delete .history file (in tcsh shell), so I can't
see their commands.
Can I disable the command unset history?
If it is not possible, what can I do?
nothing, the file is writeable for the user
so if unset doe snot
On 10/16/2012 06:03 AM, Bryn M. Reeves wrote:
On 10/16/2012 07:52 AM, Tiziana Manfroni wrote:
Hi, I have some users that delete .history file (in tcsh shell), so I
can't see their commands.
Can I disable the command unset history?
If it is not possible, what can I do?
You can't really
You can turn on BSD Process Accounting (which is in the kernel for
Fedora) in the system profile. This causes the kernel to dump a record
for each process spawned into the system logs. You will want to install
and use a tool to analyze the logs and keep them to a reasonable size.
BSD
On 10/16/2012 11:50 AM, Alan Cox wrote:
You can turn on BSD Process Accounting (which is in the kernel for
Fedora) in the system profile. This causes the kernel to dump a record
for each process spawned into the system logs. You will want to install
and use a tool to analyze the logs and
On 10/16/2012 02:52 AM, Tiziana Manfroni wrote:
Hi, I have some users that delete .history file (in tcsh shell), so I
can't see their commands.
Can I disable the command unset history?
If it is not possible, what can I do?
Thanks in advance
Tiziana
If you are creative with scripting you may
On 10/16/2012 05:06 PM, Mark LaPierre wrote:
On 10/16/2012 02:52 AM, Tiziana Manfroni wrote:
Hi, I have some users that delete .history file (in tcsh shell), so I
can't see their commands.
Can I disable the command unset history?
If it is not possible, what can I do?
Thanks in advance
On 10/16/2012 05:52 PM, JD wrote:
On 10/16/2012 05:06 PM, Mark LaPierre wrote:
On 10/16/2012 02:52 AM, Tiziana Manfroni wrote:
Hi, I have some users that delete .history file (in tcsh shell), so I
can't see their commands.
Can I disable the command unset history?
If it is not possible, what
On 10/16/2012 05:06 PM, Mark LaPierre wrote:
On 10/16/2012 02:52 AM, Tiziana Manfroni wrote:
Hi, I have some users that delete .history file (in tcsh shell), so I
can't see their commands.
Can I disable the command unset history?
If it is not possible, what can I do?
Thanks in advance
On 10/15/2012 11:52 PM, Tiziana Manfroni wrote:
If it is not possible, what can I do?
Enable the auditing system. Everything else can be trivially disabled
or evaded.
SuSE actually has some fair documentation for this:
On Sat, Apr 28, 2012 at 03:38:41PM -0600, Peter Gueckel wrote:
I read about a shell variable called HISTIGNORE that is supposed to prevent
duplicate
commands from occurring in .bash_history.
I put the following line into ~/.bash_profile:
export HISTIGNORE=
It's not working. I still
. The correct
option is HISTCONTROL.
Whereas HISTIGNORE uses pattern matching to not record commands in the
history list, HISTCONTROL controls which commands are saved in the
history list based on its value. In the OP's case the appropriate value
should be either of `ignoredups' or `erasedups
I read about a shell variable called HISTIGNORE that is supposed to prevent
duplicate
commands from occurring in .bash_history.
I put the following line into ~/.bash_profile:
export HISTIGNORE=
It's not working. I still have duplicate commands galore. Why isn't is working?
--
users mailing
On Sat, Apr 28, 2012 at 4:38 PM, Peter Gueckel pguec...@gmail.com wrote:
I read about a shell variable called HISTIGNORE that is supposed to prevent
duplicate
commands from occurring in .bash_history.
I put the following line into ~/.bash_profile:
export HISTIGNORE=
It's not working. I
On 28 April 2012 22:38, Peter Gueckel pguec...@gmail.com wrote:
I read about a shell variable called HISTIGNORE that is supposed to
prevent duplicate
commands from occurring in .bash_history.
I put the following line into ~/.bash_profile:
export HISTIGNORE=
It's not working. I still have
Andy Blanchard wrote:
HISTIGNORE only deals with consecutive duplicates, IIRC.
What you want is:
export HISTCONTROL=erasedups
you might also want to add :ignorespace to the end of that. That will
cause any command prefixed by a space to be ignored as well - very useful
for those
1 - 100 of 159 matches
Mail list logo
