Hi,
I try to execute bleachbit (as user) on every boot. So I used kcron, and while running that task manually works perfect I was wondering if it executed on reboot as well.
Is there some type of logfile? I don’t know where to look, most answers on the internet refer to ubuntu. Or are there better ways to do so? I’m still new to modern linux.
If you are able to use a terminal:
Try journalctl -b with grep (and whatever the name you want to search for).
In my experience cron needs the full path to be able to run an application.
Depending on your DE there are other ways to start an app at boot.
For kde: system settings → autostart.
Check journalctl -u cronie.service or journalctl -u kcron.service eventually.
I don’t use kcron as the setting up new cronjobs directly in /etc/cron.d/ is pretty straight forward once you’ve internalized the crontab syntax.
You could add something like echo "$(date): All Cleaned Up!" >> /var/log/bleachbit.log after the command you want to be executed.
For example: bleachbit -c --preset; echo "$(date): All Cleaned Up" >> /var/log/bleachbit.log
I get “no entries”
And obviously it didn’t run, because when I run it manually after reboot there are files to delete that shouldn’t be there if it had run like it should.
This is /var/spool/cron/*user*
#Bleachbit Systemstart
@reboot /usr/bin/bleachbit -c --preset
# Diese Datei wurde von KCron generiert Thursday, 3. April 2025 16:04:26 Mitteleuropäische Sommerzeit.
You could make a script and let a systemd service run it for you as your user.
[Unit]
Description= Running Bleachbit
DefaultDependencies=no
Before=shutdown.target reboot.target halt.target
[Service]
User=username
ExecStart=/path/to/cleanup.sh
Type=oneshot
[Install]
WantedBy=shutdown.target reboot.target halt.target
The script could look like:
#! /bin/bash
## run bleachbit with preset
bleachbit -c --preset
echo "$(date) All Cleaned Up!" >> /home/username/cleanup.log
Make this executable and put it somewhere in your path. For example /home/username/.local/bin
Or anywhere you like. Just exclude the location in Bleachbit.
To add this location to your path, you need something like export PATH="$HOME/.local/bin:$PATH" in your .bashrc
This is just an example. You need to adjust it to your situation by replacing username with your real user name and so on. Also the .targets may need some adjustment. As it is it should work for shutdown, reboot and suspension I think. Research further.
Bleachbit stir up high sentiments among some members of the Linux community. You have been warned 
This is all part of me transitioning from Windows to Linux. With that script I can replace Bleachbit one day by letting it do what Bleachbit is doing now, but I’ll have to do it step by step.
The last time I used Linux was more than 20 years ago, a lot of things have changed and I have to relearn a lot.
In this case it seems that the cron-service wasn’t even running.
I’ve watched some videos on Youtube since your last reply, and now I was able to get it working with systemd, thank you very much for your help!!
It doesn’t run on boot, but that’s not necessary since it does its job at shutdown. I still don’t know what you mean by “add this location to your path”.
The videos I mentioned:
" Systemd Explained: The Ultimate Deep Dive for Linux Users" by Learn Linux TV:
https://www.youtube.com/watch?v=Kzpm-rGAXos&t=286s
and " Automate Your Tasks with systemd Timers: A Step-by-Step Guide", also by Learn Linux TV:
https://www.youtube.com/watch?v=n6BuUgkZ5T0&t=150s
I’m glad to hear that you got it working!
Adding a directory to your path means including that directory in the list of locations where the system searches for executable files.
You can type echo $PATH in a terminal to see those locations.
I have to mention also, please exercise caution when using Bleachbit. many users complaining at it for breaking their system tend not to pay attention to its setting and remove more things than they should.
Add the things you absolutely don’t want to be deleted to its whitelist. And never run it as root!
So it’s like the “PATH”-command in DOS.
I’m quite an experienced user in Windows, so I am careful enough in what I am choosing to delete. In a way Windows and Linux are quite similar. In Windows I knew how to navigate through the registry, the policies, the .ini-files and so on. My main issue with switching to Linux is WHERE to find the files I am looking for and what the counterparts are named. Bleachbit is helping me to find them before I start using rm -rf * to get rid of things.
When users start to complain about a program it’s often not the program’s fault.
This will delete all the files and folders in the current directory. It will do it recursively and forcibly without prompting for confirmation. Be careful with it and please don’t use it with sudo in a system directory.
I am not sure if this tool will help but it will give you some visual about a structure of directory.
For example tree /boot for my system using grub:
$ tree /boot
/boot
├── amd-ucode.img
├── grub
│ ├── custom.cfg
│ ├── fonts
│ │ └── unicode.pf2
│ ├── grub.cfg
│ ├── grubenv
│ ├── locale
│ │ ├── ast.mo
│ │ ├── ca.mo
│ │ ├── da.mo
│ │ ├── de_CH.mo
│ │ ├── de@hebrew.mo
│ │ ├── de.mo
│ │ ├── en@arabic.mo
│ │ ├── en@cyrillic.mo
│ │ ├── en@greek.mo
│ │ ├── en@hebrew.mo
│ │ ├── en@piglatin.mo
│ │ ├── en@quot.mo
│ │ ├── eo.mo
│ │ ├── es.mo
│ │ ├── fi.mo
│ │ ├── fr.mo
│ │ ├── gl.mo
│ │ ├── he.mo
│ │ ├── hr.mo
│ │ ├── hu.mo
│ │ ├── id.mo
│ │ ├── it.mo
│ │ ├── ja.mo
│ │ ├── ka.mo
│ │ ├── ko.mo
│ │ ├── lg.mo
│ │ ├── lt.mo
│ │ ├── nb.mo
│ │ ├── nl.mo
│ │ ├── pa.mo
│ │ ├── pl.mo
│ │ ├── pt_BR.mo
│ │ ├── pt.mo
│ │ ├── ro.mo
│ │ ├── ru.mo
│ │ ├── sl.mo
│ │ ├── sr.mo
│ │ ├── sv.mo
│ │ ├── tr.mo
│ │ ├── uk.mo
│ │ ├── vi.mo
│ │ ├── zh_CN.mo
│ │ └── zh_TW.mo
│ ├── themes
│ │ └── starfield
│ │ ├── blob_w.png
│ │ ├── boot_menu_c.png
│ │ ├── boot_menu_e.png
│ │ ├── boot_menu_ne.png
│ │ ├── boot_menu_n.png
│ │ ├── boot_menu_nw.png
│ │ ├── boot_menu_se.png
│ │ ├── boot_menu_s.png
│ │ ├── boot_menu_sw.png
│ │ ├── boot_menu_w.png
│ │ ├── COPYING.CC-BY-SA-3.0
│ │ ├── dejavu_10.pf2
│ │ ├── dejavu_12.pf2
│ │ ├── dejavu_14.pf2
│ │ ├── dejavu_16.pf2
│ │ ├── dejavu_bold_14.pf2
│ │ ├── infinity.png
│ │ ├── README
│ │ ├── slider_c.png
│ │ ├── slider_n.png
│ │ ├── slider_s.png
│ │ ├── starfield.png
│ │ ├── terminal_box_c.png
│ │ ├── terminal_box_e.png
│ │ ├── terminal_box_ne.png
│ │ ├── terminal_box_n.png
│ │ ├── terminal_box_nw.png
│ │ ├── terminal_box_se.png
│ │ ├── terminal_box_s.png
│ │ ├── terminal_box_sw.png
│ │ ├── terminal_box_w.png
│ │ └── theme.txt
│ └── x86_64-efi
│ ├── acpi.mod
│ ├── adler32.mod
│ ├── affs.mod
│ ├── afs.mod
│ ├── afsplitter.mod
│ ├── ahci.mod
│ ├── all_video.mod
│ ├── aout.mod
│ ├── appleldr.mod
│ ├── archelp.mod
│ ├── asn1.mod
│ ├── asn1_test.mod
│ ├── ata.mod
│ ├── at_keyboard.mod
│ ├── backtrace.mod
│ ├── bfs.mod
│ ├── bitmap.mod
│ ├── bitmap_scale.mod
│ ├── bli.mod
│ ├── blocklist.mod
│ ├── boot.mod
│ ├── boottime.mod
│ ├── bsd.mod
│ ├── bswap_test.mod
│ ├── btrfs.mod
│ ├── bufio.mod
│ ├── cacheinfo.mod
│ ├── cat.mod
│ ├── cbfs.mod
│ ├── cbls.mod
│ ├── cbmemc.mod
│ ├── cbtable.mod
│ ├── cbtime.mod
│ ├── chain.mod
│ ├── cmdline_cat_test.mod
│ ├── cmosdump.mod
│ ├── cmostest.mod
│ ├── cmp.mod
│ ├── cmp_test.mod
│ ├── command.lst
│ ├── configfile.mod
│ ├── core.efi
│ ├── cpio_be.mod
│ ├── cpio.mod
│ ├── cpuid.mod
│ ├── crc64.mod
│ ├── cryptodisk.mod
│ ├── crypto.lst
│ ├── crypto.mod
│ ├── cs5536.mod
│ ├── ctz_test.mod
│ ├── datehook.mod
│ ├── date.mod
│ ├── datetime.mod
│ ├── diskfilter.mod
│ ├── disk.mod
│ ├── div.mod
│ ├── div_test.mod
│ ├── dm_nv.mod
│ ├── echo.mod
│ ├── efifwsetup.mod
│ ├── efi_gop.mod
│ ├── efinet.mod
│ ├── efitextmode.mod
│ ├── efi_uga.mod
│ ├── ehci.mod
│ ├── elf.mod
│ ├── erofs.mod
│ ├── eval.mod
│ ├── exfat.mod
│ ├── exfctest.mod
│ ├── ext2.mod
│ ├── extcmd.mod
│ ├── f2fs.mod
│ ├── fat.mod
│ ├── file.mod
│ ├── fixvideo.mod
│ ├── font.mod
│ ├── fshelp.mod
│ ├── fs.lst
│ ├── functional_test.mod
│ ├── gcry_arcfour.mod
│ ├── gcry_blowfish.mod
│ ├── gcry_camellia.mod
│ ├── gcry_cast5.mod
│ ├── gcry_crc.mod
│ ├── gcry_des.mod
│ ├── gcry_dsa.mod
│ ├── gcry_idea.mod
│ ├── gcry_md4.mod
│ ├── gcry_md5.mod
│ ├── gcry_rfc2268.mod
│ ├── gcry_rijndael.mod
│ ├── gcry_rmd160.mod
│ ├── gcry_rsa.mod
│ ├── gcry_seed.mod
│ ├── gcry_serpent.mod
│ ├── gcry_sha1.mod
│ ├── gcry_sha256.mod
│ ├── gcry_sha512.mod
│ ├── gcry_tiger.mod
│ ├── gcry_twofish.mod
│ ├── gcry_whirlpool.mod
│ ├── geli.mod
│ ├── gettext.mod
│ ├── gfxmenu.mod
│ ├── gfxterm_background.mod
│ ├── gfxterm_menu.mod
│ ├── gfxterm.mod
│ ├── gptsync.mod
│ ├── grub.efi
│ ├── gzio.mod
│ ├── halt.mod
│ ├── hashsum.mod
│ ├── hdparm.mod
│ ├── hello.mod
│ ├── help.mod
│ ├── hexdump.mod
│ ├── hfs.mod
│ ├── hfspluscomp.mod
│ ├── hfsplus.mod
│ ├── http.mod
│ ├── iorw.mod
│ ├── iso9660.mod
│ ├── jfs.mod
│ ├── jpeg.mod
│ ├── json.mod
│ ├── keylayouts.mod
│ ├── key_protector.mod
│ ├── keystatus.mod
│ ├── ldm.mod
│ ├── legacycfg.mod
│ ├── legacy_password_test.mod
│ ├── linux16.mod
│ ├── linux.mod
│ ├── loadbios.mod
│ ├── loadenv.mod
│ ├── loopback.mod
│ ├── lsacpi.mod
│ ├── lsefimmap.mod
│ ├── lsefi.mod
│ ├── lsefisystab.mod
│ ├── lsmmap.mod
│ ├── ls.mod
│ ├── lspci.mod
│ ├── lssal.mod
│ ├── luks2.mod
│ ├── luks.mod
│ ├── lvm.mod
│ ├── lzopio.mod
│ ├── macbless.mod
│ ├── macho.mod
│ ├── mdraid09_be.mod
│ ├── mdraid09.mod
│ ├── mdraid1x.mod
│ ├── memdisk.mod
│ ├── memrw.mod
│ ├── minicmd.mod
│ ├── minix2_be.mod
│ ├── minix2.mod
│ ├── minix3_be.mod
│ ├── minix3.mod
│ ├── minix_be.mod
│ ├── minix.mod
│ ├── mmap.mod
│ ├── moddep.lst
│ ├── modinfo.sh
│ ├── morse.mod
│ ├── mpi.mod
│ ├── msdospart.mod
│ ├── mul_test.mod
│ ├── multiboot2.mod
│ ├── multiboot.mod
│ ├── nativedisk.mod
│ ├── net.mod
│ ├── newc.mod
│ ├── nilfs2.mod
│ ├── normal.mod
│ ├── ntfscomp.mod
│ ├── ntfs.mod
│ ├── odc.mod
│ ├── offsetio.mod
│ ├── ohci.mod
│ ├── part_acorn.mod
│ ├── part_amiga.mod
│ ├── part_apple.mod
│ ├── part_bsd.mod
│ ├── part_dfly.mod
│ ├── part_dvh.mod
│ ├── part_gpt.mod
│ ├── partmap.lst
│ ├── part_msdos.mod
│ ├── part_plan.mod
│ ├── part_sun.mod
│ ├── part_sunpc.mod
│ ├── parttool.lst
│ ├── parttool.mod
│ ├── password.mod
│ ├── password_pbkdf2.mod
│ ├── pata.mod
│ ├── pbkdf2.mod
│ ├── pbkdf2_test.mod
│ ├── pcidump.mod
│ ├── pgp.mod
│ ├── plainmount.mod
│ ├── play.mod
│ ├── png.mod
│ ├── priority_queue.mod
│ ├── probe.mod
│ ├── procfs.mod
│ ├── progress.mod
│ ├── raid5rec.mod
│ ├── raid6rec.mod
│ ├── random.mod
│ ├── rdmsr.mod
│ ├── read.mod
│ ├── reboot.mod
│ ├── regexp.mod
│ ├── reiserfs.mod
│ ├── relocator.mod
│ ├── romfs.mod
│ ├── scsi.mod
│ ├── search_fs_file.mod
│ ├── search_fs_uuid.mod
│ ├── search_label.mod
│ ├── search.mod
│ ├── serial.mod
│ ├── setjmp.mod
│ ├── setjmp_test.mod
│ ├── setpci.mod
│ ├── sfs.mod
│ ├── shift_test.mod
│ ├── signature_test.mod
│ ├── sleep.mod
│ ├── sleep_test.mod
│ ├── smbios.mod
│ ├── spkmodem.mod
│ ├── squash4.mod
│ ├── strtoull_test.mod
│ ├── syslinuxcfg.mod
│ ├── tar.mod
│ ├── terminal.lst
│ ├── terminal.mod
│ ├── terminfo.mod
│ ├── test_blockarg.mod
│ ├── testload.mod
│ ├── test.mod
│ ├── testspeed.mod
│ ├── tftp.mod
│ ├── tga.mod
│ ├── time.mod
│ ├── tpm2_key_protector.mod
│ ├── tpm.mod
│ ├── trig.mod
│ ├── tr.mod
│ ├── true.mod
│ ├── tss2.mod
│ ├── udf.mod
│ ├── ufs1_be.mod
│ ├── ufs1.mod
│ ├── ufs2.mod
│ ├── uhci.mod
│ ├── usb_keyboard.mod
│ ├── usb.mod
│ ├── usbms.mod
│ ├── usbserial_common.mod
│ ├── usbserial_ftdi.mod
│ ├── usbserial_pl2303.mod
│ ├── usbserial_usbdebug.mod
│ ├── usbtest.mod
│ ├── video_bochs.mod
│ ├── video_cirrus.mod
│ ├── video_colors.mod
│ ├── video_fb.mod
│ ├── videoinfo.mod
│ ├── video.lst
│ ├── video.mod
│ ├── videotest_checksum.mod
│ ├── videotest.mod
│ ├── wrmsr.mod
│ ├── xfs.mod
│ ├── xnu.mod
│ ├── xnu_uuid.mod
│ ├── xnu_uuid_test.mod
│ ├── xzio.mod
│ ├── zfscrypt.mod
│ ├── zfsinfo.mod
│ ├── zfs.mod
│ └── zstd.mod
├── initramfs-linux-fallback.img
├── initramfs-linux.img
├── initramfs-linux-lts.img
├── initramfs-linux-zen-fallback.img
├── initramfs-linux-zen.img
├── memtest86+
│ └── memtest.efi
├── vmlinuz-linux
├── vmlinuz-linux-lts
└── vmlinuz-linux-zen
8 directories, 378 files
There are also GUI applications for disk usage analyze like baobab (GTK based) or filelight (QT based). To be run in a terminal ncdu will give also some visual over the filesystem structure and usage.
For Filesystem Hierachy Standard:
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.