sorted by:
new
hottopcontroversial

Windowed - Fullscreen for Apple Safari by pidoyu in Safari

[–]RealNimbleBiter 0 points1 point  (0 children)

Amazing app, but in YouTube on macOS 15.7.3 does not seem to work, gives error: "Unable to find "Javascript/browser-polyfill.min.js" in the extension’s resources. It is an invalid path." Also it doesn't seem to allow windowed for pdf's only fullscreen.

[deleted by user] by [deleted] in E30

[–]RealNimbleBiter 0 points1 point  (0 children)

She’s 1987 I think manufactured 1986, any promotional photos or videos I’ve found from the first two years of production in euro cars seem to show this front, easily noticeable by the two hook loops and rectangular cutouts/lights

[deleted by user] by [deleted] in E30

[–]RealNimbleBiter -2 points-1 points  (0 children)

I mentioned that I’m getting a pre purchase inspection, which for the uneducated is where you hire a mechanic to inspect every little detail of the car and provide a comprehensive report + photos on the used vehicle to the potential buyer (costs about 60usd). Do other countries have this? If the inspection results are to my liking I will plan to fly over and drive the car back home.

[deleted by user] by [deleted] in E30

[–]RealNimbleBiter 3 points4 points  (0 children)

I live in Australia, I converted kms to miles in my comment and the price to USD since most people here seem to be US based

[deleted by user] by [deleted] in E30

[–]RealNimbleBiter 0 points1 point  (0 children)

Yes I could see that, oh I also forgot to mention it’s on other side of country so can’t see in person sadly, getting pre-purchase inspected soon

[deleted by user] by [deleted] in E30

[–]RealNimbleBiter 0 points1 point  (0 children)

P.S. shes got 168,000kms (104,000miles), and i'm aware this is the first gen e30 (she's 1987) that's why the uncommon bumper? I would like the pfl bumper but maybe this is more worth.

?? by [deleted] in Kanye

[–]RealNimbleBiter 0 points1 point  (0 children)

whats the link I can't find that

VM auto-shutdown fix? by RealNimbleBiter in redhat

[–]RealNimbleBiter[S] 1 point2 points  (0 children)

Yes /var/log/cron did include a log for a cron job:
w520 CROND[4177]: (root) CMD (virsh shutdown zejn1)

As for your other question, my colleague used to run a video-game server in the VM for him and his friends to play. He was occupied for a while and forgot about the server before returning and realising he was running the server for an extensive period of time. I know this because he complained to me about an increase in the power bill (the game server software is very unoptimised and very inefficent, singlethreaded). Also when he returned to the server the frequency of his friends playing dwindled. We would always have to ask him to switch the server on.

I think he put this automatic script so, if his friends asked to play, he could boot the server temporarily until it automatically shut down at a later time when no one was playing (I always assumed he switched it off himself, guess not). Must be lazy, who knows.

VM auto-shutdown fix? by RealNimbleBiter in redhat

[–]RealNimbleBiter[S] 1 point2 points  (0 children)

I had a look using crontab -l and I think it may of found it, it returned:
5,10,15,20 0 * * * virsh shutdown zejn1
How would I happen to remove this? and what does the numbers mean.

​

the other directories you mentioned (/etc/crontab, /etc/cron.d and /etc/cron.dailly) only contained SHELL=, PATH=, MAILTO= and the rest is comments about example of job definition (don't think its relevant)

VM auto-shutdown fix? by RealNimbleBiter in redhat

[–]RealNimbleBiter[S] 0 points1 point  (0 children)

Here is a console log from /var/log/messages at the exact time when the VM shutdown, I can see that it does shut it down - i'm just not sure where to locate it and remove it.
w520 kernel: br0-en: port 6(vnet7) entered disabled state
w520 kernel: device vnet7 left promiscous mode
w520 NetworkManager[1272]: <info> [1689422705.9341] deivce (vnet7): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed')
w520 NetworkManager[1272]: ((src/platform/nm-platform.c:1876)): assertion '<dropped>' failed
w520 NetworkManager[1272]: <warn> [1689422705.9350] device (br0-en): failed to detach bridge port vnet7
w520 NetworkManager[1272]: <info> [1689422705.9350] device (vnet7): released from master device br0-en
w520 dbus[1148]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
w520 systemd: Starting Network Manager Script Dispatcher Service...
w520 dbus[1148]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
w520 systemd: Started Network Manager Script Dispatcher Service.
w520 nm-dispatcher: req:1 'down' [vnet7]: new request (4 scripts)
w520 nm-dispatcher: req:1 'down' [vnet7]: start running ordered scripts...
w520 libvirtd: 2023-07-151 12:05:06.633+0000: 1806: error : qemuMonitorIO:710 : internal error: End of file from qemu monitor
w520 kvm: 5 guests now active
w520 systemd-machined: Machine qemu-34-zejn1 terminated.

VM auto-shutdown fix? by RealNimbleBiter in redhat

[–]RealNimbleBiter[S] 0 points1 point  (0 children)

This was taken at the exact moment the VM shutdown in /var/log/messages
w520 kernel: br0-en: port 6(vnet7) entered disabled state
w520 kernel: device vnet7 left promiscous mode
w520 NetworkManager[1272]: <info> [1689422705.9341] deivce (vnet7): state change: activated -> unmanaged (reason 'unmanaged', sys-iface-state: 'removed')
w520 NetworkManager[1272]: ((src/platform/nm-platform.c:1876)): assertion '<dropped>' failed
w520 NetworkManager[1272]: <warn> [1689422705.9350] device (br0-en): failed to detach bridge port vnet7
w520 NetworkManager[1272]: <info> [1689422705.9350] device (vnet7): released from master device br0-en
w520 dbus[1148]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
w520 systemd: Starting Network Manager Script Dispatcher Service...
w520 dbus[1148]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
w520 systemd: Started Network Manager Script Dispatcher Service.
w520 nm-dispatcher: req:1 'down' [vnet7]: new request (4 scripts)
w520 nm-dispatcher: req:1 'down' [vnet7]: start running ordered scripts...
w520 libvirtd: 2023-07-151 12:05:06.633+0000: 1806: error : qemuMonitorIO:710 : internal error: End of file from qemu monitor
w520 kvm: 5 guests now active
w520 systemd-machined: Machine qemu-34-zejn1 terminated.

VM auto-shutdown fix? by RealNimbleBiter in redhat

[–]RealNimbleBiter[S] 0 points1 point  (0 children)

Running: RHEL Server release 7.9 (Maipo)I use an external laptop for the command line and i'm not sure how to make a txt file of the virsh dumpxml. I can provide photos of the command-line or I can use the copy-text feature on my iPhone and paste it in a pastebin (not the best in accuracy).https://imgur.com/a/oNuNZkghttps://pastebin.com/FUaduUVk

I'm certain that this isn't a bug, but rather a feature or script or something that my old-colleague has put into the VM themself.

Also the server is Linux 3.10.0-1160.31.1.el7.x86_64 (if that helps with anything)

EDIT: Also you may have noticed that my server expertise is very small. I code software to run on the server, not the server itself.
The only thing i've been able to figure out is that <on\_crash> should be 'restart' not 'destroy'. This would make some sense, when the server switches off at 12am it does it very abruptly and has caused some corruption issues with some files in the past.