while the OP had an entry for /tmp in teir /etc/fstab.
Wow!
AFAICT, i did not create any systemd files nor ran a generator or such.
Apart from listing units, i did not interfere ... wait ... i recall
using the systemctl edit command once
So, what likely happened is:
- You had an fstab entry
Am 05.10.2022 um 21:03 schrieb Andy Smith:
> Well it says it was generated by systemd-fstab-generator, but that
> would usually put its generated units in /run/systemd/generator, not
> /etc/systemd/system/, so it seems at some point something/someone ran:
>
> # systemd-fstab-generator
Hello,
On Wed, Oct 05, 2022 at 02:31:01PM -0400, Greg Wooledge wrote:
> On Wed, Oct 05, 2022 at 06:23:39PM +, Andy Smith wrote:
> > I haven't yet felt the need to adjust sizing or permissions on /tmp
> > but if I did I'd just put an entry for it in /etc/fstab.
>
> Me too, but I'm still
On Wed, Oct 05, 2022 at 06:23:39PM +, Andy Smith wrote:
> I haven't yet felt the need to adjust sizing or permissions on /tmp
> but if I did I'd just put an entry for it in /etc/fstab.
Me too, but I'm still curious where the OP's /etc/systemd/system/* file
came from. If the OP didn't write
Hello,
On Wed, Oct 05, 2022 at 12:04:31PM +0200, DdB wrote:
> How are the more experienced people among you handle /tmp ?
> Could i just benefit from your experience?
I don't tend to mess with the Debian default for /tmp, which is to
not to have it be a mount point at all, so it is on the root
Am 05.10.2022 um 19:07 schrieb Greg Wooledge:
> And you have NO memory of creating this file? Did someone else maybe
> set this system up for you, who might have done this?
That is certain: I did NOT create this file, my understanding of systemd
is way too basic. (It did not even cross my mind
On Wed, Oct 05, 2022 at 05:45:41PM +0200, DdB wrote:
> > datakanja@NewSimul:/etc$ cat systemd/system/tmp.mount
> > # Automatically generated by systemd-fstab-generator
> >
> > [Unit]
> > SourcePath=/etc/fstab
> > Documentation=man:fstab(5) man:systemd-fstab-generator(8)
> > Before=local-fs.target
Am 05.10.2022 um 13:24 schrieb Greg Wooledge:
> You're going to have to figure out what's mounting your /tmp file system
> in the first place. If it's not /etc/fstab then it could be a dedicated
> systemd unit, or a command in /etc/rc.local, or a crontab @reboot entry,
> or an /etc/init.d/
On Wed, Oct 05, 2022 at 02:07:17PM +0100, Tixy wrote:
I seem to remember many releases ago playing with this, and there was a
config file to set /tmp to tmpfs. A quick google leads me to to look at
'man tmpfs' which says:
/tmp Previously configured using RAMTMP in /etc/default/rcS. Note that
On Wed, 2022-10-05 at 15:52 +0300, Anssi Saari wrote:
> DdB writes:
>
> > How are the more experienced people among you handle /tmp ?
> > Could i just benefit from your experience?
>
> I leave /tmp as is or if I see a benefit for the system, then I put
> something like this in /etc/fstab:
>
>
DdB writes:
> How are the more experienced people among you handle /tmp ?
> Could i just benefit from your experience?
I leave /tmp as is or if I see a benefit for the system, then I put
something like this in /etc/fstab:
none /tmp tmpfs defaults,size=55% 0 0
The 55% is
On Wed, Oct 05, 2022 at 12:04:31PM +0200, DdB wrote:
> fstab has no entry concerning /tmp.
> After booting, mount gives this:
>
> >> tmpfs on /tmp type tmpfs (rw,nosuid,relatime,size=51200k)
Huh. Weird.
> Additional information:
> while i am still using oldstable (buster),
You're going to
Hello,
i may be misunderstanding something, but to me, it looks like manually
increasing the size of /tmp is a working workaround for several problems
i am running into.
By now, there are some things, i will not even initiate before issuing:
>> sudo mount -o remount,size=50G /tmp
After this
13 matches
Mail list logo
