Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: How can be disabled syslog-ng service at boot (Read 1449 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: How can be disabled syslog-ng service at boot

Reply #15 –
If your goal is lightweightness, use busybox syslogd, can't get more lightweight than a syslog designed for embedded and low memory systems.

You can grab my OpenRC service file if you want.

Re: How can be disabled syslog-ng service at boot

Reply #16 –
Haha, nice program, cool. Who doesn't want light weight? Even if i had a thread ripper with a ton of memory and powerful graphic card i would still aim for the fastest most efficient packages. It's a brilliant philosophy  8)

Re: How can be disabled syslog-ng service at boot

Reply #17 –
>It's a brilliant philosophy

Well then you'll love busybox and suckless.

Besides, busybox ain't just a syslog, theres a lot more you can replace.
Code: [Select]
$ ll --color=no /usr/local/busybox/
total	  
lrwxrwxrwx	base32 -> ../../bin/busybox
lrwxrwxrwx	base64 -> ../../bin/busybox
lrwxrwxrwx	basename -> ../../bin/busybox
lrwxrwxrwx	cp -> ../../bin/busybox
lrwxrwxrwx	cut -> ../../bin/busybox
lrwxrwxrwx	date -> ../../bin/busybox
lrwxrwxrwx	df -> ../../bin/busybox
lrwxrwxrwx	diff -> ../../bin/busybox
lrwxrwxrwx	dirname -> ../../bin/busybox
lrwxrwxrwx	du -> ../../bin/busybox
lrwxrwxrwx	egrep -> ../../bin/busybox
lrwxrwxrwx	fbset -> ../../bin/busybox
lrwxrwxrwx	fgrep -> ../../bin/busybox
lrwxrwxrwx	grep -> ../../bin/busybox
lrwxrwxrwx	head -> ../../bin/busybox
lrwxrwxrwx	ln -> ../../bin/busybox
lrwxrwxrwx	ls -> ../../bin/busybox
lrwxrwxrwx	md5sum -> ../../bin/busybox
lrwxrwxrwx	mv -> ../../bin/busybox
lrwxrwxrwx	pgrep -> ../../bin/busybox
lrwxrwxrwx	pwd -> ../../bin/busybox
lrwxrwxrwx	seq -> ../../bin/busybox
lrwxrwxrwx	sha1sum -> ../../bin/busybox
lrwxrwxrwx	sha256sum -> ../../bin/busybox
lrwxrwxrwx	sha3sum -> ../../bin/busybox
lrwxrwxrwx	sha512sum -> ../../bin/busybox
lrwxrwxrwx	sum -> ../../bin/busybox
lrwxrwxrwx	syslogd -> ../../bin/busybox
lrwxrwxrwx	tac -> ../../bin/busybox
lrwxrwxrwx	cat -> ../../bin/busybox
lrwxrwxrwx	tail -> ../../bin/busybox
lrwxrwxrwx	tty -> ../../bin/busybox
lrwxrwxrwx	uniq -> ../../bin/busybox
...

Put them first in your $PATH and enjoy (except make sure makepkg is run with the standard $PATH, you can do it with env PATH='/bin:/sbin' makepkg)
 

Re: How can be disabled syslog-ng service at boot

Reply #18 –

Quote from: Lancia – on
I don't think it's that much in the grand scheme of things, especially considering how web browsers write tons of stuff to ~/.cache

There's a setting in firefox you can change so ff will use only RAM memory. This is what shows ff in my about:cache. So in my case ff reads/writes exclusively in memory. That setting you can look for more info here  section DISK AVOIDANCE

"browser.cache.disk.enable"       turn it to false