On 8/21/19 5:39 PM, ToddAndMargo via users wrote:
The PID is the number to the left of PDT
That should have said the "right" of ... Ooops
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedo
On 8/11/19 5:25 PM, ToddAndMargo via users wrote:
Hi All,
I have no idea what this tells me
$ cat /proc/sys/kernel/core_pattern
|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e
Does anyone know of a list somewhere?
And why does it send out a pipe symbol?
What does this do?
On 2019-08-12 20:53, Samuel Sieb wrote:
On 8/12/19 3:18 AM, Jeremy Nicoll - ml fedora wrote:
Excuse my interruption, but why would that create a file named
'core'? Why doesn't it just place 'core' in the named file?
That's not a real file...
Thank-you to both Sam and Samuel for explainin
ToddAndMargo via users writes:
On 8/12/19 3:37 AM, Sam Varshavchik wrote:
Well, if the program exits with the exit code that indicates that it dumped
core, you can have your script automatically run coredumpctl to extract the
core out.
The stinking script exits after starting the program.
On 8/13/19 5:23 AM, ToddAndMargo via users wrote:
> On 8/12/19 2:27 AM, Ed Greshko wrote:
>> By default the core files are kept in/var/lib/systemd/coredump/
>>
>> If files are "missing" nothing can be extracted.
>
> If it is not missing, how do I extract it from coredump?
> "cp"?
>
No, you use cor
On 8/12/19 3:37 AM, Sam Varshavchik wrote:
Well, if the program exits with the exit code that indicates that it
dumped core, you can have your script automatically run coredumpctl to
extract the core out.
The stinking script exits after starting the program.
Rats!
__
On 8/12/19 2:27 AM, Ed Greshko wrote:
By default the core files are kept in/var/lib/systemd/coredump/
If files are "missing" nothing can be extracted.
If it is not missing, how do I extract it from coredump?
"cp"?
___
users mailing list -- users@lis
On 8/12/19 3:18 AM, Jeremy Nicoll - ml fedora wrote:
On 2019-08-12 02:01, Sam Varshavchik wrote:
ToddAndMargo via users writes:
What does this do?
# echo core > /proc/sys/kernel/core_pattern
This will, instead, create a plain file called
"core" in the executable's directory.
Excuse
Jeremy Nicoll - ml fedora writes:
On 2019-08-12 02:01, Sam Varshavchik wrote:
ToddAndMargo via users writes:
What does this do?
# echo core > /proc/sys/kernel/core_pattern
This will, instead, create a plain file called
"core" in the executable's directory.
Excuse my interruption,
ToddAndMargo via users writes:
On 8/11/19 6:01 PM, Sam Varshavchik wrote:
Now, if you really want a core file, you don't really have to do any of
that. You can leave core_pattern at its default value, and just pull the
core file down, upon demand. I have a small shell script in my $HOME/bin
On 2019-08-12 02:01, Sam Varshavchik wrote:
ToddAndMargo via users writes:
What does this do?
# echo core > /proc/sys/kernel/core_pattern
This will, instead, create a plain file called
"core" in the executable's directory.
Excuse my interruption, but why would that create a file nam
On 8/12/19 4:27 PM, ToddAndMargo via users wrote:
> On 8/11/19 11:56 PM, Ed Greshko wrote:
>> "missing" means that the core was stored in a file, but this file
>> has since been removed.
>
>
> Is there some age out timer involved.
From the coredump.conf(5) man page
MaxUse
On 8/11/19 11:56 PM, Ed Greshko wrote:
"missing" means that the core was stored in a file, but this file
has since been removed.
Is there some age out timer involved.
And if it is not missing, how do I extract it?
___
users mailin
On 8/12/19 2:46 PM, ToddAndMargo via users wrote:
> On 8/11/19 9:05 PM, Andy Paterson via users wrote:
>> man 5 core
>
> # coredumpctl list | grep -i cimtrak
>
> TIME PID UID GID SIG COREFILE EXE
> Fri 2019-07-26 08:21:14 PDT 32530 0 0 11 missing
> /opt/Ci
On 8/11/19 9:05 PM, Andy Paterson via users wrote:
man 5 core
# coredumpctl list | grep -i cimtrak
TIMEPID UID GID SIG COREFILE EXE
Fri 2019-07-26 08:21:14 PDT 32530 0 0 11 missing
/opt/Cimcor/CimTrak/CimTrakServer/CimTrakServer.bin
The core file
On 8/11/19 6:01 PM, Sam Varshavchik wrote:
Now, if you really want a core file, you don't really have to do any of
that. You can leave core_pattern at its default value, and just pull the
core file down, upon demand. I have a small shell script in my $HOME/bin
directory:
$ cat ~/bin/core
#!/b
man 5 core
> On 12 Aug 2019, at 04:48, ToddAndMargo via users
> wrote:
>
>> On 8/11/19 6:01 PM, Sam Varshavchik wrote:
>> ToddAndMargo via users writes:
>>> Hi All,
>>>
>>> I have no idea what this tells me
>>>
>>> $ cat /proc/sys/kernel/core_pattern
>>> |/usr/lib/systemd/systemd-coredump
On 8/11/19 6:01 PM, Sam Varshavchik wrote:
ToddAndMargo via users writes:
Hi All,
I have no idea what this tells me
$ cat /proc/sys/kernel/core_pattern
|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e
Does anyone know of a list somewhere?
Would you believe the proc manual pag
On 8/12/19 8:25 AM, ToddAndMargo via users wrote:
> Hi All,
>
> I have no idea what this tells me
>
> $ cat /proc/sys/kernel/core_pattern
> |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e
>
> Does anyone know of a list somewhere?
>
> And why does it send out a pipe symbol?
>
>
> What
ToddAndMargo via users writes:
Hi All,
I have no idea what this tells me
$ cat /proc/sys/kernel/core_pattern
|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e
Does anyone know of a list somewhere?
Would you believe the proc manual page, which directs you to the core manual
pa
Hi All,
I have no idea what this tells me
$ cat /proc/sys/kernel/core_pattern
|/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e
Does anyone know of a list somewhere?
And why does it send out a pipe symbol?
What does this do?
# echo core > /proc/sys/kernel/core_pattern
Wil
21 matches
Mail list logo