On 11/21/19 2:30 PM, Todd Zullinger wrote:
> Those aren't actual code snippets you used, are they? This
> code:
>
> if ! [[ "pgrep ksysguard" ]] ; then
>
> is testing whether the string is empty or not rather than
> running the command and checking for output. You can see
> that by running:
home user wrote:
>> You could also use 'pgrep ksysguard' ...
> Thank-you, Todd.
> I tried it. It does not work. I don't know why.
Nor do I. We'd need to see the actual code you ran and its
output for that. :)
> I tried both
> if ! [[ "pgrep ksysguard" ]] ; then
> and
> if [[ "pgrep -v
Hi,
On Thu, Nov 21, 2019 at 7:48 AM William Brown wrote:
>
>
> > On 21 Nov 2019, at 10:49, cool dharma06 wrote:
> >
>
> > Hi William,
> >
> > Thanks for your reply.
> >
> > I want to enable 389ds to generate nsUniqueID, modifiedTimestamp,
creators name for all enteries which is added/getting
> On 21 Nov 2019, at 10:49, cool dharma06 wrote:
>
> Hi William,
>
> Thanks for your reply.
>
> I want to enable 389ds to generate nsUniqueID, modifiedTimestamp, creators
> name for all enteries which is added/getting added to 389-ds. Any suggestions
> or reference link to enable this.
On Wed, 20 Nov 2019 at 17:41, Roger Heflin wrote:
> I am seeing it occurring on the new kernels on f30, so the kernel does
> seem what is doing it.
>
xhci has a bug affecting many USB devices across many hardware
configurations and kernels 4.20 and later.
On Wed, 20 Nov 2019 10:08:23 -0500
Sean Darcy wrote:
> I upgraded 29-> 30. Now I can't even get to the boot screen. I've made
> a live usb stick, but the stick only wants to install a completely new
> system. Is there any way to use the stick to troubleshoot the existing
> installation.
The
> Are you saying that the question you asked initially
> isn't the actual one you needed answering?
The initial question was:
> >How do I, within the .bash_profile if test, distinguish su connection
> > vs. direct login from the login screen?
That was the real question. I needed that answered
Hi William,
Thanks for your reply.
I want to enable 389ds to generate nsUniqueID, modifiedTimestamp, creators
name for all enteries which is added/getting added to 389-ds. Any
suggestions or reference link to enable this.
I have OpenLdap set up with replication enabled and I want to make one
On 11/21/19 7:43 AM, home user wrote:
> My real .bash_profile is trying to manage two pairs of xeyes, each with 5
> command line options. So Ed's autostart suggestions do not apply.
Why don't you state precisely what you'd like to accomplish so energy isn't
expended by
folks on issues which
On 11/21/19 7:52 AM, home user wrote:
> > if ! pidof ksysguard > /dev/null ; then ...
> Thank-you Patrick.
> I studied the man page for pidof. As I understand it, it implies that pidof
> does not work across login names; user2 cannot see user1's processes:
> -
> [from the description of
> if ! pidof ksysguard > /dev/null ; then ...
Thank-you Patrick.
I studied the man page for pidof. As I understand it, it implies that
pidof does not work across login names; user2 cannot see user1's processes:
-
[from the description of option "-c"]
This option is ignored for non-root
> You could also use 'pgrep ksysguard' ...
Thank-you, Todd.
I tried it. It does not work. I don't know why.
When I log in as user1, and then do "su --login user2", it does work.
When I log in as user2, it does not work.
I did a lot of testing using ordinary bash scripts rather than
On 11/21/19 7:29 AM, home user wrote:
> > FWIW, it is bad practice to answer multiple posts in the same message.
> I didn't know that. sorry.
>
> > For GNOME it is almost as simple. ...
> Thank-you, Ed. I'm using ksysguard in this thread for simplicity. My real
> .bash_profile is trying to
> FWIW, it is bad practice to answer multiple posts in the same message.
I didn't know that. sorry.
> For GNOME it is almost as simple. ...
Thank-you, Ed. I'm using ksysguard in this thread for simplicity. My
real .bash_profile is trying to manage two pairs of xeyes, each with 5
command line
> On 20 Nov 2019, at 15:41, cool dharma06 wrote:
>
> Hi all,
>
> i have OpenLDAP in my environment. And i am experimenting 389-ds and their
> functionalities. In my OpenLDAP, i have entries with following attributes:
> entryCSN, contextCSN, entryUUID.
>
> 1. For entryCSN and contextCSN -
I am seeing it occurring on the new kernels on f30, so the kernel does
seem what is doing it.
I was figuring another new laptop was in my future.
On Tue, Nov 19, 2019 at 10:23 PM ToddAndMargo via users
wrote:
>
> On 11/19/19 4:50 PM, Tom Horsley wrote:
> > On Tue, 19 Nov 2019 16:38:33 -0800
> >
On Wed, 2019-11-20 at 13:51 -0500, Tim Evans wrote:
> I reported this at the time I upgraded my two systems to F30, and
> find that it's still true with F31.
I've found some login screens order the list of accounts using the most
frequent users at the top.
--
uname -rsvp
Linux
On 11/20/19 2:27 PM, Samuel Sieb wrote:
On 11/20/19 10:51 AM, Tim Evans wrote:
While the extra click on "Not shown" is not a major big deal, I'm
unable to figure out how to flip-flop the two userids on the systems
so that the primary user appears on the login screen.
What is the content of
On 11/20/19 11:03 AM, Patrick Dupre wrote:
When I run nextcloud, I get:
"the password you use to log in to your computer no longer matches that of your
login keyring"
It was not too much an issue when I was able to cancel the request, but
for 2 days now, I am even not able kill the request.
I
On 11/20/19 10:51 AM, Tim Evans wrote:
While the extra click on "Not shown" is not a major big deal, I'm unable
to figure out how to flip-flop the two userids on the systems so that
the primary user appears on the login screen.
What is the content of the files in
On 11/20/2019 11:51 AM, Tim Evans wrote:
While the extra click on "Not shown" is not a major big deal, I'm unable
to figure out how to flip-flop the two userids on the systems so that
the primary user appears on the login screen.
Log in as your primary user and delete the other one.
Hello,
When I run nextcloud, I get:
"the password you use to log in to your computer no longer matches that of your
login keyring"
It was not too much an issue when I was able to cancel the request, but
for 2 days now, I am even not able kill the request.
I have to kill the nextcloud
I reported this at the time I upgraded my two systems to F30, and find
that it's still true with F31.
On my main (desktop) machine, there are two users, one of which (me) is
flagged as the administrative user; the other is a mere mortal. My
userid was displayed on the Gnome login screen; the
I upgraded 29-> 30. Now I can't even get to the boot screen. I've made
a live usb stick, but the stick only wants to install a completely new
system. Is there any way to use the stick to troubleshoot the existing
installation.
If I had to guess the upgrade screwed up the the UEFI boot. I can boot
On Tue, 2019-11-19 at 20:55 -0700, home user wrote:
> if ! [[ "ps -ef | grep [k]sysguard" ]] ; then
> ksysguard &
> fi
> -
if ! pidof ksysguard > /dev/null ; then
...
fi
poc
___
users mailing list -- users@lists.fedoraproject.org
To
25 matches
Mail list logo
