Re: what is an administrator?

[Joonas Sarajärvi]

Terry Polzin kirjoitti 27.09.2017 klo 17:05:

In Anaconda adding a user account as an "Administrator" adds that user to
the "wheel" group by default the wheel group is enabled wthin sudo to run
all commands with "root" privileges.  After install adding a user to the
"wheel" group will have the same effect without the need to edit
/etc/sudoers via "vi sudo" and adding the user manually.



Also editing only sudoers will not add a rule equivalent to what is set 
up for wheel group in /etc/polkit-1/rules.d/50-default.rules


I am not sure if there are even more places to look at if one wants an 
equivalent setup without the wheel group. If someone knows about 
documentation on this, would be awesome to have it posted on list.


- Joonas
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: Live Media Only??

[Joonas Sarajärvi]

Hi,

08.03.2016, 00:15, Bear Tooth kirjoitti:


I went to download F3 from

https://spins.fedoraproject.org/en/

(using Opera 35.0 under F23) and everything I got turned out to be Live
CDs (except for being larger than any CD I have). I don't mean to
hesitate. I want a real full install. What am I doing wrong??



Spins are indeed live images. They are not CD sized because it is 
expected that most users have access to either USB memories or at least 
writable DVDs. If you do an installation from the live image, the  I 
think resulting installed OS is just as real and full as it would be 
from netinstall installer or the DVD installer.


The netinstall images and main server image are "non-live" and they have 
a bit more customizability in the installation phase. The resulting 
installation should not differ much except in what gets installed by 
default.


- Joonas
--
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: rsyslog

[Joonas Sarajärvi]

2015-03-07 11:04 GMT+02:00 Tim :
> On Fri, 2015-03-06 at 08:28 -0700, Pete Travis wrote:
>> No, the journalctl man page does not tell you about ntp logs, nor do
>> the rsyslog pages explain grep :)
>
> ;-)
>
> The man page suggested that the search parameter was a service name
> (that I wouldn't know, at the time), as opposed to just being a keyword
> I could supply to look for in a log entry.
>
> It's still tediously slow to use, compared to the old messages text file
> (which was only a recent log file, since the last rotation, not a huge
> behemoth).  I'm not convinced it's the best way to do things for those
> that only need to do the occasional system administration (because,
> generally, their computer just works fine).

You can limit the amount of data to be grepped or otherwise searched,
if you just tell journalctl to limit its output a bit. On a system
that is booted quite frequently, limiting oneself to just messages
since the last boot should work nicely:

  journalctl -b | grep -i ntp

If your system has a long uptime, the -b option might produce a large
amount of data. In such a case, you might instead use the --since
option:

  journalctl --since '-1 week' | grep -i ntp

I would usually let journalctl put the results in a pager (it does
that by default when not piping) and then use the search/filter
features of less to narrow down the results. These examples use grep,
though, because you seemed to prefer using it for searching.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F20: No sound unless root ??

[Joonas Sarajärvi]

2015-02-02 22:18 GMT+02:00 sean darcy :
> On 02/02/2015 03:10 PM, sean darcy wrote:
>>
>> I'm trying to play some sound as a user. But pulseaudio can't find any
>> outputs:
>>
>> $ aplay -l
>> aplay: device_list:268: no soundcards found...
>>
>> But, as root, aplay sees the integrated sound card:
>>
>

How are you logged in in the system? My impression is that sound
devices in fedora are set up to be available to the user who is
physically present.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Another systemd annoyance

[Joonas Sarajärvi]

2015-01-31 13:52 GMT+02:00 Heinz Diehl :
> Hi,
>
> tried to safely bring down a crashed Fedora 21 machine today, but M-sysrq
> didn't do anything. After bringing the machine up again, the logs showed
> that M-sysrq functionality was disabled. After investigating further, it 
> seemed
> that only Sysrq-S (emergency save) was actually working. In 
> /etc/sysctl.d/01-sysctl.conf,
> "kernel.sysrq=1" was present. It took me nearly 30 min. to find out that 
> systemd
> has it's own sysctl definitions, gladly ignoring/overwriting /etc/sysctl.d. In
> /usr/lib/sysctl.d/50-default.conf, "kernel.sysrq=16" was set, which is what 
> crippled
> full sysrq functionality.
>
> In addition, I'm curious what happens when the next systemd update gets 
> pulled in.
> Most probably, my manual settings will be overwritten with what systemd thinks
> is good for the user..
>

Processing order of files under /etc/sysctl.d/ seems to be such that
files with a high number override files with a low number. If you do
not want your changes to be overridden, I think it would be a good
idea to pick a high number like 90 instead of 01 for the start if your
config file name.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F21 minimal install?

[Joonas Sarajärvi]

Hi,

2014-12-16 19:57 GMT+02:00 Ian Pilcher :
> Do any of the F21 installation media provide a minimal install option
> anymore?  IIRC, the "basic server" (or whatever it's called) now
> installs more than 600 packages, around twice as many as the F20 minimal
> install.

At least with a kickstart config, an F21 installation of less than 300
packages seems to be possible. As the config, I used basically an
identical setup to what had worked for me for making minimal F20
installations.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: smplayer nagware

[Joonas Sarajärvi]

Hello,

2014-10-30 13:33 GMT+02:00 Tim :
> I thought I'd escaped from this sort of crap when I shifted to Linux,
> all those years ago.  I've just started up smplayer and got a pop-up
> saying "you can support SMPlayer by sending a donation or sharing it
> with your friends," with buttons to donate with paypal, and so something
> with facebook or twitter.

You are in no way obliged to send money or take other actions, even if
the application mentions that it would be a nice thing to do. Linux
does not require that applications running on it abstain for
mentioning such things either. And even the concept of free software
does not require it.

Given how smplayer is in Rpmfusion-free, my impression is that it is
free software. So you should be free to make a modified version that
does not contain the message that offends you, and it should even be
ok to distribute that. But the original application author is
similarly free to release a version of the software that displays it.
With proprietary software, the original author would not even be
required to give you that possibility. In case of smplayer, you should
have that option.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: 64bit skype client needed

[Joonas Sarajärvi]

>
> OK, I have the rpm pf skype which was built for fc18:
> skype-4.2.0.11-3.fc18.x86_64.rpm
> but it still depends on i686 libs and other components.
>
> I was wondering if there is a way to extract the spec file
> from it and rebuild it (i.e. relink it) with 64bit libs, by
> editing the spec file, and running rpmbuild ...etc.
>
To make a 64-bit build of the application, you would need to actually
compile the sources with a compiler that targets the 64-bit
instruction set. This requires access to application source code.
Source code to the Skype client is not available.

My impression is that the skype "x86_64" rpm is still the same 32-bit
application that ships in their 32-bit package.

Fortunately, an x86-64 Fedora installation can easily run also 32-bit
applications.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedora 20 with AMD catalyst video driver

[Joonas Sarajärvi]

Hello,

2014-09-15 19:18 GMT+03:00 Bruno Jean :
> So my question is the following: Is the default video driver in the fedora 20 
> allows for a 2560×1440 external monitor resolution with AMD GPU, or I should 
> go with another GPU (Nvidia?) or a motherboard GPU.
>
> Thanks in advance for your support,
>

At least the built-in Radeon HD6550d GPU that I have in a quad-core
AMD CPU works nicely with the fedora default drivers. While I do not
have a 2560×1440 display to try with it, I do not have problems with
displays of smaller resolutions getting set to their correct
resolutions.

The stuff you miss out on by not using Catalyst should mostly be some
OpenGL performance and features, and possibly some power management
stuff. But even with the Fedora default drivers, OpenGL performance
seems sufficient for a large number of OpenGL based applications.

- Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: is it the future?

[Joonas Sarajärvi]

2014-09-14 18:12 GMT+03:00 Timothy Murphy :
> But what you actually said was
> "I might add that according to the documentation, you can avoid the
> persistent journal by removing /var/log/journal/ directory or by
> specifying Storage=volatile or Storage=none in
> /etc/systemd/journald.conf".
>
I guess I should have been more specific about that the config option
affects just whether the journal content gets stored by journald. So
it would not affect what journalctl displays. Journalctl seems to
default to displaying all the journal content it can find in the
standard /run/log/journal and /var/log/journal locations. But
hopefully this is clear now.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: is it the future?

[Joonas Sarajärvi]

2014-09-14 16:36 GMT+03:00 Balint Szigeti :
> On Sun, 2014-09-14 at 16:22 +0300, Joonas Sarajärvi wrote:
>
> 2014-09-14 15:22 GMT+03:00 Timothy Murphy :
> I have already done it that you wrote and still no affect. The 'journalctl'
> just doesn't read or handle its config file.

Just to be specific, journald.conf is a config file for journald. My
impression is that journalctl does not care about the journald config
at all.

If you still have a large amount of journal content after deleting
/var/log/journal/, I do wonder where journalctl on your system reads
it from.
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: is it the future?

[Joonas Sarajärvi]

2014-09-14 15:22 GMT+03:00 Timothy Murphy :
> As a matter of interest, I changed Storage to volatile
> and re-booted my laptop,
> but this did not seem to have any effect -
> journalctl still gives over 500,000 lines (I stopped there)
> and goes back 3 months.
> The first line of journalctl says it will be limited to 100MB.

If you left /var/log/journal content in place, I guess journalctl and
systemctl status will still consider also that
when priting journal content for you. But AFAIK you can just delete
the directory if you do not need the persistent journal.
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: is it the future?

[Joonas Sarajärvi]

2014-09-14 14:01 GMT+03:00 Timothy Murphy :
> Joonas Sarajärvi wrote:
>
>> It is not slow if you have little journal content, as you would in
>> cases where you prefer plain-text logs and set journald to not keep a
>> persistent log.
>
> How?
> I don't see anything relevant in "man journalctl" under Fedora-20.
> (There is no entry for "man journald".)
I was going to post the correct man page names, but Veli-Pekka Kestilä
seems to already have sent those.

I might add that according to the documentation, you can avoid the
persistent journal by removing /var/log/journal/ directory or by
specifying Storage=volatile or Storage=none in
/etc/systemd/journald.conf

The default value for that setting is "auto", which means that
existence of /var/log/journal/ enables the persistent log.
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: is it the future?

[Joonas Sarajärvi]

2014-09-14 0:26 GMT+03:00 Lars E. Pettersson :
> On 09/12/14 21:12, Kevin Fenzi wrote:
>> The amount of memory and i/o is trivial, IMHO.
>
>
> Trivial? Take a look at my nine month old bug report, that has received no
> response whatsoever form the systemd maintainers, about the sluggishness of
> the journal compared to the good old text based log files.
>
> 
>
> Even 'systemctl status some_service' take way too long time due to the
> sluggish journal.
>
It is not slow if you have little journal content, as you would in
cases where you prefer plain-text logs and set journald to not keep a
persistent log. At least in my experience, even a Raspberry pi with
less than 200 MiB of RAM can easily handle it.

If you have a large amount of content in the journal, accessing it
takes a bit time. I tend to limit the persistent journal size to
something like a few hundred megabytes. Then it can still store many
months worth of data, but performance of journalctl and systemd status
stay reasonable.

At least for me, most of the journal slowness seems to happen when the
journal data is not cached by the kernel. For example, running
systemctl status postgresql took something like 8 seconds on the first
run, but less than 10 ms on the next one.

- Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: is it the future?

[Joonas Sarajärvi]

Hey,

2014-09-12 21:30 GMT+03:00 Anders Wegge Keller :
>  I'm asking for a pointer to the numerous rebuttals of falsehoods, and
> carefully considerations, that time and time again are claimed to exist. A
> Debian document, written to whitewash a forced descision is not what I'm
> asking for.

The page I linked to includes argumentation both for and against all
the four init system options that were considered for Debian. Of
course the systemd page there is for advocating systemd, but you can
also read the argumentations against its use in the pages of other
inits. And as far as I know, the systemd page is at least reasonably
correct in its facts.

If you need a rebuttal specifically for the other article, I currently
do not know where I could point you. But in my opinion, the Debian
debate pages are one of the better places to get an overview of the
merits of different init options. While the debate resulted in Debian
picking systemd, just valuing the various technical aspects
differently could have had a different result in that discussion. The
facts in there should still be reasonably right.

- Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: is it the future?

[Joonas Sarajärvi]

2014-09-12 11:06 GMT+03:00 Anders Wegge Keller :
>  Do you know of a place where I can find the analysis behind this
> assessment, or is it just your personal opinion?

The recent initsystem debate [1] from Debian pretty exhaustively
explores the pros and cons of many major init system options. While
the needs of Fedora differ slightly, a lot of the discussion applies
here, too.

[1] https://wiki.debian.org/Debate/initsystem/
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F20 Where's my system mail?

[Joonas Sarajärvi]

2014-04-10 17:08 GMT+03:00 Arthur Dent :
> Does everyone here now do without email alerts, or does everyone just
> install postfix or some such?
>
> I would really like to know if there is a workaround for me...
>
> Thanks again
>
> Mark
>

My impression is that an MTA is currently not installed by default
because it was thought that most users do not use the things it
provides. However, since you seem to actually use functionality that
requires an MTA to be present, I think you should just install some
MTA of your choice and keep using the system mail functionality.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: wireshark installed but not available

[Joonas Sarajärvi]

2014-04-07 16:43 GMT+03:00 Robert Moskowitz :
> ARGH  I hate logging out!!!  I have too many apps running 'just right'
> to logout more than say once a month.  (really when I have to reboot when
> things get doggy)
>
> sigh.
For now, you might be able to perform the capture by running tcpdump
from commad line as root, and telling it to write packets into a file.
Wireshark can open such a file with no additional privileges. E.g.
something like this:

tcpdump -i enp3s0 -w packets

The open the packets file in wireshark.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F20 - Unintended consequences of no default MTA - How best to fix

[Joonas Sarajärvi]

2013/12/31 Joe Zeff :
> Not always.  As an example, I'm getting error messages at boot time on my
> laptop about [sdb] even though there isn't one.  Locating them with
> journalctl would require me to know exactly what field to look for, instead
> of just doing this as root:
>
> cat /var/log/messages | grep [sdb]
>
> Of course, if you do know the field name, such as when you're looking for
> messages from a service started at boot by systemd, journalctl may well be
> your best bet.  It all depends on what you're looking for and what info you
> already have.

Journalctl does not prevent you from using generic text search tools
like grep. For example, this should have pretty same results as your
example:

journalctl | grep [sdb]

You would likely want to limit the journalctl command a bit to avoid
searching from the entire locally stored history. This can be avoided
by using journalctl -b or journalctl --since -7d or some other
parameters that limit the search to just the recent logs.

If I was looking for something sdb related problem, my preferred way
to start looking for it would be to run maybe journalctl --since -7d
and then use the text search of less to point me at the relevant parts
of the log. Often it is useful to not immediately trim out all except
the lines that match some search. OTOH if you need specifically that,
you can use grep like you could with a plaintext syslog file.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: How avoid unwanted systemd-journald?

[Joonas Sarajärvi]

Sorry for posting again so soon and replying to myself, but I just
noticed one very useful thing that might help quite much in the
specific problem you described:

2013/11/18 Joonas Sarajärvi :
> 2013/11/18 Suvayu Ali :
>> the other day, I wanted to
>> investigate why my laptop shutdown suddenly (I think it was
>> overheating), but there was no reasonable way for me to filter the cpu
>> specific messages.
> I am not sure where that message in particular would show up.

Likely you would not want to look for a specific subsystem anyway
Often there are many things in the system interacting and it is nicer
to look at the whole log in the correct point in time. One nice filter
criteria is to filter by boot id with the --boot option of journalctl

journalctl --boot

The above would show just the messages that were gathered during the
currently ongoing boot cycle. Now if you want messages of the previous
boot, --boot allows you to specify an offset. So if you pass -1 there
like this, it would show you messages from the previous boot cycle:
journalctl --boot=-1

If you already booted many times, just grow the number after the minus
sign to find the one that ended before you intended it to. Then just
scroll to the end (the > key usually does this in less) to see what
were the last messages that were recorded before shutdown.

In some cases like a kernel panic, you will likely not have the kernel
panic message in the log. This is because usually at the point where
the kernel has the message, it will not write anything to disk
anymore. If there is nothing interesting in the end of that boot, you
should also check if the following boot has a note about the journal
being rotated due to not being properly closed. This would at least
let you know that you miss some messages.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: How avoid unwanted systemd-journald?

[Joonas Sarajärvi]

2013/11/18 Suvayu Ali :
> Hi Jonas,
>
> I have a comment, and a question.
>
> On Sun, Nov 17, 2013 at 03:46:55PM +0200, Joonas Sarajärvi wrote:
>> The journald log format is documented at least to some extent [1], and
>> there exists free software for reading the log. To me, it sounds like
>> way more accessible than if it was a binary data format of a typical
>> proprietary tool. For example, booting any Fedora live image should
>> suffice if you need to read the journal of a system that uses journald
>> and happens to become unbootable.
>
> I am sure you (and everyone else on the list) will agree, tools for
> viewing plain text (cat, more, less, ) outnumber and
> are available on every platform compared to any specialised tool.  Even
> if a format is open, it still needs tools that support it.  I would not
> count on having a gui when my system crashes.  Sometimes the only access
> you have to a crashed system is the recovery prompt.
I wonder where this notion that you'd need a GUI to access the journal
content came from. You do need a working journalctl, but it is not a
GUI tool. Normally it outputs syslog-like output that you could feed
to your favourite syslog-output-expecting log analysis tool.

>> At least for my needs, the journal has been way more convenient to use
>> than rsyslog. It is much nicer to read logs when journalctl e.g.
>> combines the older rotated logs with the latest ones. Also, it easily
>> allows me to easily specify that I want just the logs of this month or
>> of just this one boot, or of just some specific service.
>
> I have been very frustrated with journalctl.  The manual page is very
> unhelpful in that regard.  For example the other day, I wanted to
> investigate why my laptop shutdown suddenly (I think it was
> overheating), but there was no reasonable way for me to filter the cpu
> specific messages.  Could you give some pointers how I can do that?  I
> would be very grateful.
I am not sure where that message in particular would show up. My first
instinct in such a situation would be to just run journalctl without
arguments. If the output is not piped anywhere, journalctl opens less
and puts the syslog-like output there. Now it is pretty same as if I
had run less /var/log/messages in a system that uses a traditional
syslog. I can for example press / to access the search function of
less and search for the "cpu" string.

Since a hardware related error would likely be logged by the kernel, I
might invoke journalctl like this:
journalctl _TRANSPORT=kernel

This would limit the things I get so that only kernel debug messages
are shown. Different filter criteria you could use are described in
the systemd.journal-fields man page.

Another useful parameter would be the --since parameter, e.g. like this:
journalctl --since 2013-11-15 _TRANSPORT=kernel

Now journalctl would omit old stuff that likely would not be
interesting in this case.

But maybe the message is not in the kernel log, and you'd wish to use
grep to search for the message like you could with a text-based
syslog? You can like this:
journalctl --since 2013-11-15 | grep -i cpu

The --since parameter is still useful, in case you happen to have many
months of log data stored in the journal. With the --since and --until
parameters, you can limit the search to any arbitrary interval that is
covered by your stored log data, regardless of how those times relate
to the times at which log rotation has happened.

Hopefully this helps. At least you should know that you can still use
your knowledge of the traditional unixy text-processing tools.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: How avoid unwanted systemd-journald?

[Joonas Sarajärvi]

2013/11/17 Frantisek Hanzlik :
> Steven Stern wrote:
>> On 11/15/2013 04:46 AM, Frantisek Hanzlik wrote:
>>> For one thing I'm in the conviction that binary logs are hazardous
>>> bullshit,
>>
>> In what way might the logs be hazardous?
>
> It was mean mainly from administrator view. When things go bad,
> machine HW/SW fail or any other disasters occurs, logs are very
> valuable. And I'm confident that binary logs are too weak in this
> situation. Text logs are useful even if log file is damaged or ends
> with fragments and can be easy readable with lot of tools. Binary
> logs, by contrast, may be useless when log file is damaged or I
> haven't this one unique utility for reading them. And my experiences
> with systems where binary logs are implemented says clearly that
> binary logs is bad idea.
> Second, it is question when tight integration of systemd and logging
> services has any benefits - there is number of situation (logging
> over network, for example) which speaks for separate logging service.

The journald log format is documented at least to some extent [1], and
there exists free software for reading the log. To me, it sounds like
way more accessible than if it was a binary data format of a typical
proprietary tool. For example, booting any Fedora live image should
suffice if you need to read the journal of a system that uses journald
and happens to become unbootable.

Typically journalctl will generate you a representation of the data in
syslog log file format. This loses some infromation that the journal
stores, because there is no way to represent it all while keeping the
output syslog-like and easily human-readable. This output can be
easily fed to traditional unix tools like grep, if that is your
preferred way of extracting information from logs.

Finally, since you can also run a normal syslog daemon which maintains
a text-format logs for you, I do not really see why having some log
data in journald format under /run/log/journal/ should be considered
hazardous. You can pretty much just ignore it if you feel like using
other kinds of tools for storing and managing logs.

> And possibilities with e.g. rsyslogd are better than with journald
> - why Fedora must again replace verified, reliable, Unix standard
> things with some crappy solutions? For nightmares of its users?
At least for my needs, the journal has been way more convenient to use
than rsyslog. It is much nicer to read logs when journalctl e.g.
combines the older rotated logs with the latest ones. Also, it easily
allows me to easily specify that I want just the logs of this month or
of just this one boot, or of just some specific service.

If I was writing tools that'd automatically handle the logs, I think I
would also benefit from the additional data that journal stores that
is usually not available in a syslog formatted log. Having to use e.g.
the journal API would of course be some burden, but I can imagine it
being nicer than having to e.g. parse all the different date formats
that a text-formatted log could have. Or having to handle all of the
other things that may or may not be in the syslog lines, in various
formats.

Of course there are still bugs and the other issues in the new tools,
but they certainly aren't there in order to cause nightmares. I am
hopeful that the issues can be and are fixed. For my (relatively
simple) setups, there aren't any major showshoppers, though.

[1] http://www.freedesktop.org/wiki/Software/systemd/journal-files/

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Can I run two "instances" of apache httpd?

[Joonas Sarajärvi]

Hello,

2013/8/9 Zdenek Pytela :
> Yes. You just have multiple Listen lines in your config file and
> then you have to restart the httpd.service.
I think the main goal was not just to get Apache to listen to multiple
ports, but to have two entirely separate Apache instances running, to
prevent a badly behaving web application from affecting the better
behaving ones. Of course this would likely also involve having them
listen to different ports.

-Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Can I run two "instances" of apache httpd?

[Joonas Sarajärvi]

9.8.2013 11.05 "Georgios Petasis"  wrote:
>
> In general I think it can be done (i.e.:
http://wiki.apache.org/httpd/RunningMultipleApacheInstances),
> but is a way to do this in fedora 19, and keep all this "systemctl *
httpd" stuff?
>
I have not attempted it, but I think it should be possible. You would just
write a new systemd unit that'd start Apache so that it would read its
configuration files from a different location. Then you could carefully
create the alternative configuration so that the Apache instances do not
interfere with each other.

- Joonas
-- 
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: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: F-18 startx -

[Joonas Sarajärvi]

Hi,

2013/3/13 Tim :
> It does seem a rather brutal approach.

I do not much like setting symlinks manually, either. However,
systemctl also can set them for you if you run just something like
this:

  systemctl enable --force multi-user.target

This works because multi-user.target has a line like this in its
[Install] section:
Alias=default.target

The force flag is needed or systemctl will not overwrite an existing symlink.

From Fedora 18 onwards, the same mechanism also works for display
managers like kdm and gdm.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Fedora 17 Gnome 3 Desperate Plea

[Joonas Sarajärvi]

2012/12/29 Mika Suomalainen :
> I (or actually not me, but many people whom I know) have another
> problem with GNOME3, they don't know how to halt the computer
> properly, because the "Shutdown" button is hidden behind the menu in
> top-right and you must press "alt" to access the option.

Fortunately this particular issue does not seem to exist anymore in
Gnome 3.6, as shipped in the Fedora 18 prereleases.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: force yum to download

[Joonas Sarajärvi]

You might want to use yumdownloader instead.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: was: Still no kmod for new nvidia- now: so Move On

[Joonas Sarajärvi]

listic notion #2.
> Video card design is well known and pretty standard, so why can't an
> Open source electronics genius assemble a competent 3D video card for
> global Linux 3D power users?  Yep it's only a few hundred thousand
> cards, maybe a couple of million but has anyone researched the
> possibilities?
> If so what was the outcome?
> What are the barriers?
> Could it be used to raise funds for further development?
> Does anyone care?
There exists the Open Graphics Project:
http://wiki.opengraphics.org/tiki-index.php. They are developing a
completely open graphics hardware design. I have not followed them
lately, but at least the site seems still quite active.


-- 
Joonas Sarajärvi
mue...@gmail.com
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

Re: Package Hunt

[Joonas Sarajärvi]

2010/1/25 Mike Dwiggins :
>
>
> Joseph L. Casale wrote:
>>> Anyone heard of libcrypto.so.8 and/or where I can find it?
>>>
>>
>> Google suggests via rpmfind that it's an older (v<1) openssl lib from F11?
>>
>
> Ach, did not think of goggle.  That sounds about right, the package that
> calls for it has it's last version as F 11.  Guess I will have to roll
> back to keep the Boss happy!
>
> No way I will be able to convince him to wait for the new version.
>

Security and bug maintenance ending next summer is not good enough
reason for upgrading? Of course you still have a few months of support
in F11 available, but eventually you will probably need to upgrade it.
Fedora is not very good a distro for long term use unless you have the
upgrades planned into your usage.



-- 
Joonas Sarajärvi
mue...@gmail.com
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines